overby@lemmy.world to Lemmy.World Announcements@lemmy.world · 1 year agolemmy.world should redirect to https (secure) sitemessage-squaremessage-square21fedilinkarrow-up128arrow-down10file-text
arrow-up128arrow-down1message-squarelemmy.world should redirect to https (secure) siteoverby@lemmy.world to Lemmy.World Announcements@lemmy.world · 1 year agomessage-square21fedilinkfile-text
When you visit http://lemmy.world it should redirect to https://lemmy.world - at least the login page should be secure.
minus-squareRuud@lemmy.worldMlinkfedilinkarrow-up4·1 year agoHmm , when I replace this: http { server { listen 80; server_name lemmy.world; location / { proxy_pass http://lemmy-ui:1234; proxy_set_header Host $host; } } with this: http { server { listen 80; server_name lemmy.world; location / { return 301 https://$host$request_uri; } } it breaks, gives 502 when visiting the site… ideas? (I’m not that much into nginx…)
minus-square𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.onelinkfedilinkEnglisharrow-up3·1 year agoYou could try this this config snippet is assuming thet you’ve already got the TLS cert/pem file for lemmy.world elsewhere in your nginx.config http { server { listen 80; listen 443 ssl; server_name lemmy.world; if ($scheme = "http") { return 307 https://$host$request_uri; } location / { proxy_pass http://lemmy-ui:1234; proxy_set_header Host $host; } } If you get redirected to lemmy.world:1234, then add absolute_redirect off; in the ‘server’ block Last thing - 307 is a temporary redirect, you might to change it to a permanent one once you’ve confirmed it’s working as intended
minus-squareTom@lemmy.worldlinkfedilinkarrow-up3arrow-down1·1 year agoCan we get an error log? If no, are you seeing any timeouts in there?
minus-squareSlashzero@lemmy.worldlinkfedilinkarrow-up1·edit-21 year agoYou might want to add the secure port (:443) in your redirect. Otherwise it might be trying to load https on port 80 still, which can’t work. http: port 80 https: port 443 Notes: just a guess. I haven’t looked at an nginx config in a while make sure to try on multiple browsers as they all don’t behave the same way
minus-squareRuud@lemmy.worldMlinkfedilinkarrow-up1·1 year agoThis piece I’ve pasted above isn’t the whole nginx.conf, there’s also a large block for the 443 traffic. It’s just the http traffic that I need to redirect to 443.
minus-squareSlashzero@lemmy.worldlinkfedilinkarrow-up1·1 year agoOk. Now that I think about it, you shouldn’t have to specify the port.
Hmm , when I replace this:
http { server { listen 80; server_name lemmy.world; location / { proxy_pass http://lemmy-ui:1234; proxy_set_header Host $host; } }
with this:
http { server { listen 80; server_name lemmy.world; location / { return 301 https://$host$request_uri; } }
it breaks, gives 502 when visiting the site…
ideas? (I’m not that much into nginx…)
You could try this
this config snippet is assuming thet you’ve already got the TLS cert/pem file for lemmy.world elsewhere in your nginx.config
http { server { listen 80; listen 443 ssl; server_name lemmy.world; if ($scheme = "http") { return 307 https://$host$request_uri; } location / { proxy_pass http://lemmy-ui:1234; proxy_set_header Host $host; } }
If you get redirected to lemmy.world:1234, then add
absolute_redirect off;
in the ‘server’ blockLast thing - 307 is a temporary redirect, you might to change it to a permanent one once you’ve confirmed it’s working as intended
Cool, thanks! I’ll try that.
Can we get an error log? If no, are you seeing any timeouts in there?
You might want to add the secure port (:443) in your redirect. Otherwise it might be trying to load https on port 80 still, which can’t work.
Notes:
This piece I’ve pasted above isn’t the whole nginx.conf, there’s also a large block for the 443 traffic. It’s just the http traffic that I need to redirect to 443.
Ok. Now that I think about it, you shouldn’t have to specify the port.