Selfhosted

61512 readers

1261 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Force SSL in Nginx Proxy Manager (sh.itjust.works)

submitted 3 years ago by beppi@sh.itjust.works to c/selfhosted@lemmy.world

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

[–] redcalcium@lemmy.institute 1 points 3 years 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.