Hello everyone and thanks in advance for the response if possible.
I have a fixed IP at home. Behind it I have set up an Ubuntu server with Virtualmin (VMWare) with ports http=89 and https=2053 and, on the same server, docker with nginx proxy manager to manage virtualmin certificates and docker containers. Everything working perfectly.
Cloudflare indicates that it also manages with port 2053 for https. But as soon as I activate Proxied, the web page stops showing.
If you web server is listening on port 2053 for HTTPS, then with the proxy shut off, you should be able to enter the URL like https://example.com:2053 and have it work. If that doesn’t work with the proxy shut off, then the problem is elsewhere.
You said with the proxy off, it works. What URL do you enter to make it work in that case?
Thanks again. No, the Nginx Proxy Manager in docker resolve the port. It resolve the port you want but the port 80 and 443 must to be put to it and not to the virtualmin software. As soon you say to the nginz manager the port that is using the web, in this case 2053 it redirects automatically.
In that case, it sounds like it’s being served publicly on the default ports (80 and 443). So you don’t need to do anything with the alternate ports because that’s already being forwarded. No rules, no ports needed in the URL, just a normal server setup.
But is it possible that your ISP is blocking those ports? If it’s a residential connection they may not want you running a web server and may be blocking 80 and 443.
Virtualmin uses 89 and 2053 for https as an optional https as indicate clouflare. Nginx docker uses 80 and 443. Salirdelasciudades com is the domain. Now i habe it disconnected. I acces to virtualmin whit its own port 10000. I type the name of the web whithout using the 2053 as must be
I do not know what is the best solution and how to do it. I want enable proxied in cloudflare with my configuration. Nginx must listen to 80 and 443 to get the letsencrypt certificates and then redirect to the 2053 https pprt of my sites. But it does not
OK, so forget about port 2053 as far as Cloudflare is concerned. You need the nginx proxy to provide the certificate to Cloudflare for HTTPS between Cloudflare and nginx. That connection will take place to port 443 at your end as if you were connecting directly.
Just set the A record for salirdelasciudades.com in your Cloudflare DNS to point at your static IP address. Ensure your Cloudflare SSL/TLS settings are set to Full or Full (strict) (check your nginx Letsencrypt certificate is valid for salirdelasciudades.com) and that should be it assuming all the internal stuff works as you say.
Are you sure any of this is actually working from outside your home? Not just within your local network?
The address your domain name resolves to is not accepting connections on any common ports, though it is reachable. Is it possible either your ISP is blocking connections, or that you have a firewall between you and the world?