That is odd. When I navigate there I get a 502 error. I’m self hosting as well with no issues but mine is on a subdomain and not a sub folder. Maybe that is it?
this post was submitted on 02 Jul 2023
21 points (92.0% liked)
wefwef
4227 readers
1 users here now
wefwef is now Voyager! Subscribe to !voyagerapp@lemmy.world.
founded 1 year ago
MODERATORS
Sorry, I had accidentally killed the docker-container. Should be running again now. The server is not in a sub-folder, it's a docking container with a proxy redirect to the external port of the container. So the server is not in norgur.com/wefwef, but it's listening to the redirect norgur.com/wefwef.
Right, what I meant is you are hosting it on nginx as norgur.com/wefwef instead of wefwef.norgur.com. I have mine hosted as a subdomain.
What does your nginx code block look like?
#extension docker begin
location ~ ^/wef.* {
proxy_pass http://0.0.0.0:7914;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
#extension docker end
(7914 is the external port of the container, so that's correct)
When you go to the local IP internally does it load properly?
it does load properly when I call the website directly by the server's hostname (which doesn't have HTTPS enabled).
view more: next ›