wefwef

4227 readers

1 users here now

wefwef is now Voyager! Subscribe to !voyagerapp@lemmy.world.

founded 1 year ago

MODERATORS

aeharding@lemmy.world

Self-Hosted Wefwef returns black page (discuss.tchncs.de)

submitted 1 year ago* (last edited 1 year ago) by norgur@discuss.tchncs.de to c/wefwef@lemmy.world

7 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] rylin@lemmy.world 2 points 1 year ago (5 children)

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 points 1 year ago (4 children)

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 points 1 year ago* (last edited 1 year ago) (1 children)

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 points 1 year ago (1 children)

    #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 2 points 1 year ago (1 children)

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

[–] norgur@discuss.tchncs.de 1 points 1 year ago

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

load more comments (2 replies)