this post was submitted on 27 Oct 2023
1 points (100.0% liked)

Self-Hosted Main

502 readers
1 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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
[email protected]
1
Cloudflare with Nginx Proxy Manager Issues (alien.top)
submitted 10 months ago by [email protected] to c/[email protected]
2 comments fedilink hide all child comments
 

I’m trying to setup a Cloudflare tunnel to Nginx proxy manager to access all my self hosted services externally.

If I have my tunnel forward to http://nginx:80 and have force TLS turned off in Nginx proxy host everything works fine.

If I turn on force TLS I get a too many redirects error. I did some googling and found that you need to turn on full encryption rather than flexible in Cloudflare to fix this and I tried that and I still get the same issue.

If I change the tunnel to forward to https://nginx:443 I get a 502 bad gateway error, even if I turn off TLS verify.

Can anyone please help me fix these issues?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 10 months ago

What error messages are you getting in your tunnel's error logs? You can view the live logs by going to Zero Trust -> Access -> Tunnels on your Cloudflare dashboard. Click on your tunnel's name, then the connector ID, then "begin log stream".

Or, from the command line, you can add the flag --logging DEBUG to your cloudflared application at start.

After enabling logging using either of these methods, try to load your site in your browser and see what error you're getting.

Are you wanting to enable this setting in NPM so https addresses will work on your local network? I ask because the tunnel already encrypts the traffic outside your network. Changing your tunnel's forwarding address from http://nginx:80 to https:nginx:443 only encrypts the traffic between the cloudflared and NPM daemons running on your computer. It really isn't necessary since it's internal to your server.

If that's the reason why, did you install a certificate in NPM that's specific for your domain?