Bad Gateway
I'm seeing a 502 Bad Gateway in the logs and
502.5 - Process Failure in my browser.
It's working locally just fine.
Any thoughts on how to proceed?
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
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
Support Staff 1 Posted by rune on 13 Feb, 2017 11:35 PM
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
rune closed this discussion on 13 Feb, 2017 11:35 PM.
zyrain re-opened this discussion on 14 Feb, 2017 01:23 AM
2 Posted by zyrain on 14 Feb, 2017 01:23 AM
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?
Support Staff 3 Posted by rune on 14 Feb, 2017 11:58 PM
Hi,
Yep that should work -- was this the comment you'd already read? You can find the CLI right here.
Best,
Rune