Crumb
c/wefwef · by norgur@discuss.tchncs.de · 3y

Self-Hosted Wefwef returns black page

Hey there, I set up a Wefwef-Instance behind a ngninx reverse proxy. The server responds fine, yet when I call it through a forwarded domain, Wefwef will only return the page-header ("wefwef for lemmy") and a black page. Does anyone know why that would be?

URL: https://norgur.com/wef

22 points · 6 comments · view on lemmy.world

6 Comments

rylin@lemmy.world · 2 pts · 3y (5 replies)

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?

norgur@discuss.tchncs.de · 1 pts · 3y (4 replies)

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.

rylin@lemmy.world · 2 pts · 3y (3 replies)

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?

norgur@discuss.tchncs.de · 1 pts · 3y (2 replies)
    #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)

rylin@lemmy.ml · 3 pts · 3y (1 reply)

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

norgur@discuss.tchncs.de · 1 pts · 3y

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