Replies: 1 comment
-
I have added the following in the "Advanced"
which since there is nothing on port 80 of that ip i get a 404 although i would rather prefer to use the proper way e.g. serve directly a 404.html |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have two problems which i hope they are related to the same thing
- The destination is set as "http://192.168.1.52:80" which is where nginx is actually hosted
- I don't have any custom location set on the path "/".
- I have some subpath configured e.g. /syncthing or /bitwarden which can be correctly access when i do https://my-domain.com/syncthing or https://my-domain.com/bitwarden.
Is the 502 Bad Gateway suggesting a proper configuration?
It is as if that 502 is making some external services try different time the :80/ in the hope of having a proper response
Beta Was this translation helpful? Give feedback.
All reactions