Spyke
rylin
lemmy.world

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?

2
Norgurreply
discuss.tchncs.de

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.

1
rylinreply
lemmy.world

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?

2
Norgurreply
discuss.tchncs.de
    #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)

1
rylinreply
lemmy.ml

When you go to the local IP internally does it load properly?

3
Norgurreply
discuss.tchncs.de

it does load properly when I call the website directly by the server's hostname (which doesn't have HTTPS enabled).

1

You reached the end

Self-Hosted Wefwef returns black page | Spyke