Closed Raxiel1987 closed 1 month ago
Do you use ufw?
yes it's on portainer and the npm works well on firewall the ports are ok
So you have the ports open in ufw?
So you have the ports open in ufw?
yes sure
it is on proxmox lcx container, with npm "standard" lcx works, when i change to the new npm plus lcx not work
Please run docker on the host system and try again
Please run docker on the host system and try again
what do you mean run docker on host system? i duplicated the old npm standard lcx ( just for backup purpose) then in the new lcx container i swapped the npm to npm plus, all is working, the only things that don't work is the certbot
Don't use lxc. Why do you run a virtualisation Software (docker) in another one (lxc)? Either use docker OR lxc
i mean.. container.. i run docker in containers on proxmox.. npm "standard" is able to acquire new ssl cert on the same config :D, but i want to use npm plus for some extra updates and security
can you open your websites normally?
yes.. all websites working normally the only issue is for get a new certficate for another domain
i tried to restore the "old" backup with npm standard, tried to get a certificate for that domain, and it's works
What happens if you open the domain without a cert yourself?
error.. but...
i've just discovered a fact:
could npm plus have a less frequent dns refresh interval? because ( a domain registered 3 hrs ago) now seems to be reached if i test but the www part still not:
The check is done using an external service
What error?
nvm.. i think the problem is that the domain is too "new" i've registered about 3 hrs ago and maybe for some reason npm plus can't elaborate dns quick, so i wait a couple of hours and check again later
i tried to renew some other certs of others domains i have and they works..
if it works please close the issue then
after switching from npm "standard" to npmplus i got some troubles renewing the certs or obtain new. if i check network avaibility i get this error:
There is no server available at this domain. Please make sure your domain exists and points to the IP where your NPM instance is running and if necessary port 80 is forwarded in your router.
the port is open and working, if i try with the standard npm it works.. so this must be something i miss from npmplus this is my compose file:
i deleted the volumes lines # - "/portainer/Files/AppData/Config/Nginx-Proxy/letsencrypt:/etc/letsencrypt" # Only needed for first time migration from original nginx-proxy-manager to this fork, after the first starts
now i can't renew/add new certificates this supposed to open port 80 and 443, or enable in npmplus