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?
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.
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.
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).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
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.
Alright that makes sense, do you know how to solve that if that webapp is nextcloud aio?
I’m not sure what happened in your setup, but here is how https handling should works:
HTTP_X_FORWARDED_PROTOheader 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 httpsI think this chain is broken somewhere in your setup and cause nextcloud to not receive the
HTTP_X_FORWARDED_PROTOheader from nginx proxy.I just remember nextcloud has
trusted_proxiesoption located inconfig/config.phpfile. Not configuring it (or configured it wrong) can cause nextcloud to not trust theHTTP_X_FORWARDED_PROTOheader it received (it assumed to be spoofed).https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html