Getting 502 Bad Gateway after proxyAuth when trying to access custom app
-
I was trying to package up SABnzbd as a custom app for my use. This is behind the proxyAuth addon, and that certainly works. However, upon clearing the challenge, I get a 502 Bad Gateway error. I am able to access the server's index.html at port 8080 from inside the app container, however, not from outside it. The app's health check does not pass either. Would love some help to figure out what I might be doing incorrectly in the packaging process that is resulting in this error and how I might go about debugging this? I have specified httpPort in the Cloudron Manifest file correctly as 8080. Am I missing any other configuration?
The source code for my "package" is available here.
-
I was trying to package up SABnzbd as a custom app for my use. This is behind the proxyAuth addon, and that certainly works. However, upon clearing the challenge, I get a 502 Bad Gateway error. I am able to access the server's index.html at port 8080 from inside the app container, however, not from outside it. The app's health check does not pass either. Would love some help to figure out what I might be doing incorrectly in the packaging process that is resulting in this error and how I might go about debugging this? I have specified httpPort in the Cloudron Manifest file correctly as 8080. Am I missing any other configuration?
The source code for my "package" is available here.
-
I was able to resolve this issue. It was a case of my HTTP server refusing access to itself outside localhost.
-
@esawtooth Ah, I guess you had to listen to 0.0.0.0 ?
