this post was submitted on 09 Jun 2023
28 points (100.0% liked)

Lemmy.World Announcements

28383 readers
11 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 [email protected] e-mail.

Report contact

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

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 1 year ago
MODERATORS
 

When you visit http://lemmy.world it should redirect to https://lemmy.world - at least the login page should be secure.

top 17 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 1 year ago

Yes that’s on my to do list. I’ll do that today.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (1 children)

Don't all modern browsers try https by default?

(Not that I disagree.)

[–] [email protected] 2 points 1 year ago

Every time I set up FF on a new install I have to choose always on https

[–] [email protected] 4 points 1 year ago (3 children)

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...)

[–] [email protected] 3 points 1 year ago (1 children)

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

[–] [email protected] 2 points 1 year ago

Cool, thanks! I'll try that.

[–] [email protected] 2 points 1 year ago

Can we get an error log? If no, are you seeing any timeouts in there?

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

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.

  • 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
[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

Ok. Now that I think about it, you shouldn’t have to specify the port.

[–] [email protected] 3 points 1 year ago (1 children)

I've been on the secure version by default so far myself.

[–] [email protected] 2 points 1 year ago (1 children)

Yes most browsers automatically do, but some don't..

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Oooh I thought it was a backend thing, cause my NGINX has a force SSL option. I guess it can be done from either end.

[–] [email protected] 3 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago (1 children)

@[email protected] Let me see if I can reply from Mastodon

[–] [email protected] 1 points 1 year ago

Ooh it worked!

load more comments
view more: next ›