Bad Gateway

zyrain's Avatar

zyrain

13 Feb, 2017 09:25 PM

I'm seeing a 502 Bad Gateway in the logs and
502.5 - Process Failure in my browser.

It's working locally just fine.

http://ztesseract.apphb.com/

Any thoughts on how to proceed?

  1. Support Staff 1 Posted by rune on 13 Feb, 2017 11:35 PM

    rune's Avatar

    Hi,

    I took a look and it seems like this is a .NET Core application? Those are not officially supported yet, but we expect to be able to support it shortly after the RTM version of the SDK/tooling is released -- the Visual Studio team just announced the RTM release date of VS2017, which will be March 7th and will include the RTM .NET Core tooling!

    In the meantime you're of course free to see if you can find workarounds. You might want to try and enable file system write access in case log files are being written, but otherwise stay tuned and we should have a better integrated workflow ready next month.

    Best,
    Rune

  2. rune closed this discussion on 13 Feb, 2017 11:35 PM.

  3. zyrain re-opened this discussion on 14 Feb, 2017 01:23 AM

  4. 2 Posted by zyrain on 14 Feb, 2017 01:23 AM

    zyrain's Avatar

    Yes it is. I read you were supporting it, but I was supposed to use the CLI
     (where is the link for that?). I assume that means uploading the built
    files instead of having you build. Will that work?

  5. Support Staff 3 Posted by rune on 14 Feb, 2017 11:58 PM

    rune's Avatar

    Hi,

    Yep that should work -- was this the comment you'd already read? You can find the CLI right here.

    Best,
    Rune

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac