The telecom operator has closed port 443 and port 80. I use port 444 to access the server. The domain name is abcx Com, Nginx Proxy Manager has been used to reverse proxy, point to port 11000, and enter the domain name in the browser https://abcx.com:444 , automatically jump to https://abcx.com , resulting in no access to the server. How can I use port 444 instead of nextcloud ALL IN ONE? Thank you for your advice.
The ACME DNS challenge still uses port 443. I don’t need port 443.
It is not possible to use a different port.
However a Cloudflare Tunnel will allow you to use port 443.
Cloudflare Tunnel access is too slow, affecting the use. Is there a solution for the Nginx Proxy Manager not to use port 443?
A bit off-topic but why would an ISP block ports 80 and 443? That makes no sense. I have never heard of an ISP blocking ports 80 and 443. If the ISP is really doing this it might be time to move on to another ISP…
Can it be that you have just misconfigured the port forwardings for those ports on your gateway/modem? 
1 Like
No, our operators have indeed closed ports 80 and 443
In general, it is not possible to use a diffent port but you might be able to do so with all-in-one/manual-install at main · nextcloud/all-in-one · GitHub…
I recently had a similar problem but in my case I use nextcloud snap so what I had to do and forward a random external port to port 443 and then it worked correctly
Hello,
One can change Snap Nextcloud ports with single commnad
sudo snap set nextcloud ports.http=81 ports.https=444
Otherwise, if one has access to a domain, any TLD or ccTLD, he / she can use CloudFlare Tunnel. Service is free and works flawlessly behind NAT / CG-NAT or any blocked port issues.
Thanks.
First stop the docker service, and then modify the environment variables nc_domain and overwritehost of the nextcloud-aio-nextcloud container. It is always in /var/lib/docker/containers/ID/config.v2.json, restart docker after modification. It works for me.