'Site does not open when Nginx Proxy Manager "Force SSL" option is active

I have cloudflare + docker + nginx proxy manager + portainer setup for normaly ssl connection. I am just starting to use these technologies together. What I want to do is actually very simple. I want to publish a website running on Docker as ssl. I know that when we set up SSL, browsers are affected by the cache state and we need to check with incognito tabs. However, I couldn't solve the problem.

I'm creating an A record on Cloudflare. and pointing to my server's ip address. I turn it off by clicking the proxy icon before getting the ssl certificate.

enter image description here

I would like to ask the places that make me think in order. What exactly does the Scheme field do? They don't mention it at all in the training videos I've watched. everyone is doing https or http according to their head. I've also seen people choosing the force ssl option and setting it to http. Isn't something like this wrong? I know how to set forward hostname/ip and port numbers.

When my settings are like this I can connect to docker via http and use it flawlessly. but no certificate. The problem starts after that. I will explain this in the SSL tab.

enter image description here

I am able to get a certificate for the domain appearing successfully. but if I choose the force ssl option, I cannot connect to this domain in any way.

what i want to do is connect to docker with just a simple ssl connection. maybe I need to follow a different path with cloudflare. I would like to talk about that too.

enter image description here

I have never tried the full strict option. I don't think it has anything to do with it, but when cloudflare is passive, ssl connection is not possible.

If I activate cloudflare's ssl connection directly, this time I start getting err_too_many_redirects error. By the way, when I try the full option in cloudflare, I have the same problem.

It doesn't make me angry to spend a day on such a simple thing, but I couldn't decide whether it was an issue or not.



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source