I think I now fixed it
this post was submitted on 09 Jun 2023
2 points (100.0% liked)
Lemmy.World Announcements
30111 readers
28 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
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...)
Can we get an error log? If no, are you seeing any timeouts in there?
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' 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
Cool, thanks! I'll try that.
I've been on the secure version by default so far myself.
Yes most browsers automatically do, but some don't..