this post was submitted on 30 Jul 2023
10 points (77.8% liked)

Selfhosted

40329 readers
397 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
10
Force SSL in Nginx Proxy Manager (self.selfhosted)
submitted 1 year ago by beppi to c/[email protected]
8 comments fedilink hide all child comments
 

What does it actually do? When it's on, I get a redirecting error when trying to connect to my nextcloud at cloud.example.com, but with it off, it seems like I can't connect to NC using http anyway? Am I misunderstanding what it does?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 year ago (7 children)

If my understanding of how "force SSL" works for most proxies, it just simply issues a HTTP 300 redirect message for all http traffic coming in on port 80. It then sends everything to port 443 https.

Do you get a 502 when you try to connect with the force SSL turned off? It might me less of an issue with SSL and more that your proxy is not pointing to the right host / port of your nextcloud server.

[–] beppi 1 points 1 year ago (1 children)

When I connect with it off, I am able to connect. If I use https://cloud... It connects, when I use http://cloud... The address bar changes to https and connects like normal.

It just feels weird using it with force SSL off, as if even though I'm always connecting with https I'm still leaking passwords

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

“Force SSL” forces your browser to redirect http://example.com to https://example.com, it doesn’t “force” SSL into the connection. As long as you’re connecting through HTTPS, the traffic is encrypted.

If your browser redirects you from http to https after you turn off Force SSL, there could be two things going on, both related to caching:

  1. You turned on HSTS previously and that’s still cached in your browser.
  2. The http->https redirect is still cached.

You can check both of these by clearing your browser cache for example.com (or in general).

[–] beppi 1 points 1 year ago (1 children)

Thanks for the reply, yeah that's what I thought it was meant to do, sorry for the confusion

Do you have any idea why setting it on would lead to "this page isn't redirecting properly" in firefox?

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

Usually it's due to the webapp not knowing that the request is actually already served under https by the reverse proxy, it think the request is still served over http so it issues a redirect to https, which leads to a redirect loop.

[–] beppi 1 points 1 year ago (2 children)

Alright that makes sense, do you know how to solve that if that webapp is nextcloud aio?

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

I'm not sure what happened in your setup, but here is how https handling should works:

  • users request https://example.com to your reverse proxy
  • reverse proxy pass the requests to upstream server, but using http instead. It also add HTTP_X_FORWARDED_PROTO header to let the upstream server know that even though the request is over http, the end user actually served over https so it should assume the connection as https
  • the upstream server return a response, it take into accounts that the request is already done via https (e.g. generating links with https:// prefix, etc).

I think this chain is broken somewhere in your setup and cause nextcloud to not receive the HTTP_X_FORWARDED_PROTO header from nginx proxy.

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

I just remember nextcloud has trusted_proxies option located in config/config.php file. Not configuring it (or configured it wrong) can cause nextcloud to not trust the HTTP_X_FORWARDED_PROTO header it received (it assumed to be spoofed).

https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html

load more comments (5 replies)