c/lemmyworld · by overby@lemmy.world · 3y

lemmy.world should redirect to https (secure) site

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

28 points · 16 comments · view on lemmy.world

16 Comments

ruud@lemmy.world · 7 pts · 3y

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

WhoRoger@lemmy.world · 6 pts · 3y (1 reply)

Don't all modern browsers try https by default?

(Not that I disagree.)

animist@lemmy.one · 2 pts · 3y

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

ruud@lemmy.world · 4 pts · 3y (6 replies)

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

lemann@lemmy.one · 3 pts · 3y (1 reply)

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

ruud@lemmy.world · 2 pts · 3y

Cool, thanks! I'll try that.

Tom@lemmy.world · 2 pts · 3y

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

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

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

ruud@lemmy.world · 1 pts · 3y (1 reply)

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.

slashzero@lemmy.world · 1 pts · 3y

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

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

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

ruud@lemmy.world · 2 pts · 3y (1 reply)

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

CannaVet@lemmy.world · 1 pts · 3y

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.

Tom@lemmy.world · 3 pts · 3y

[ removed ]

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

I think I now fixed it

ruud@mastodon.world · 1 pts · 3y (1 reply)

@ruud@lemmy.world Let me see if I can reply from Mastodon

ruud@lemmy.world · 1 pts · 3y

Ooh it worked!