-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal error when requesting new certificate #1365
Comments
Hi, anyone to give me some advice ? In your opinion, is this a known issue, or more likely a misconfiguration (maybe in the database) ? |
The last console outputs states that your certs are still valid so they are skipped for renewal. On the database topic: you don't need it really. npm 3 will switch to an internal sqlite (as far as i unterstand). i used the official mariadb initially but i tossed it and i use the sqlite database. runs fine. EDIT: I think the jc21 database is only there because he added the aria storage engine. but that is standard in mariadb since 10.4. So i guess that maybe that database might vanish :) |
I experience a similar issue. An advise from another user was to delete the certificate and request a new one, but it's not working. For some subdomains renewing worked fine, for some it failed and requesting a new one worked fine. And for some both options didn't work. Below a part of the logfile for requesting a new certificate after deleting the expired one through the webinterface.
|
Hi, thanks both of you for your replies.
(I've of course replaced it by stars ;-) And after a few minutes, here is the error message NPM gives me :
Do you find any clues in this error message ? Thanks per advance. Eric |
@EricGuic Seems like your DNS isn't working well as you can see in the
Edit: On second reading I noticed that it is the command to install |
@thebiblelover7 , thanks to take time to read the log, I will check your link. |
@thebiblelover7 As I said, this raspberry run Adguard Home in a docker container on bridge network, and the pi has the 192.168.1.10 ip adress. The router is set up with this .10 ip adress as a dns provider. |
@EricGuic Let me try to simplfy this: Just watch the video below and afterwards reboot docker-dns.mp4I hope this makes sense |
Hi @thebiblelover7 , thank you very much for taking the time to do this little video. I've also run this command to change the default settings of the pi : I've update+upgrade the pi, reboot it, but I still have the same error in the log of the container :
Any idea ? Should I try to completely erase and re-deploy my NPM container ? (with the mariaDB one) ? (If that can help, I've also tried to request a wildcard certificate using the DNS Challenge method, by providing the token from my provider OVH). No way to make it work neither.) |
@EricGuic Check this video, hope it helps! github-docker-portainer-dns.mp4 |
Hi @thebiblelover7 , thanks again for your tip, it force me to go back to the basics (which I did'nt master apparently). You can set the default DNS settings options for the docker daemon by creating a daemon configuration file at /etc/docker/daemon.json.
I've choosed to completely "overpassed" my AdGuardHome DNS (running on another container on the same raspberry pi) to see if it could be the problem (so Cloudflare as primary, and Google as secondary DNS) I've successfully setup a wildcard certificate for my domain (with the DNS challenge). So thank you again for your help :-) (may I try a last thing : what is your advice about the network config : with only AdGuard Home, watchtower (mode notify only) and NPM on the Pi, should I run NPM under the bridge network or under the specific network created by Portainer when I deployed the stack ? (see capture attached of my current config). |
@S1M8N This is not a nginx-proxy-manager issue, please pass this on to portainer/docker |
Hi,
I get an "internal error" when I try to request a ssl certificate after setting up a proxy host.
It was working fine in july (I've created multiple host with working certificate the 16th july 2021), but now it seems to be broken.
I'm running NPM on a raspberry pi, inside Docker (alongside Watchtower, AdGuard Home and Portainer other containers). Being not very good at docker things and ssh command, I manage my container with Portainer GUI.
I've try to find a similar issue here, but without succes. Here are the first clues I can provide to you (sorry for my english from France).
My router is ok, 80 and 443 redirected to my Pi.
I can reach some services from outside my network.
So my images :
jc21/nginx-proxy-manager:latest
yobasystems/alpine-mariadb:10.4.17-arm32v7 (I try with :latest, but never get it working. I finally found some advice online saying that on the raspberry pi, you have to use this version. It works for me, but if you have advice, I will take it.
NPM container settings :
When I try to get the certificate, here are the logs inside Portainer :
Inside the console, if I run certbot renew, I get :
Those certificate correspond (I guess) to the working certificate I've already set up the 16th july 2021 and which are valid until october.
After that, I'm a bit lost. I don't know how to reach the Lets'Encrypt log, or other specific log which could be useful.
Thanks for your help.
(edit : clarify syntax, anonymised personnal email and domain)
The text was updated successfully, but these errors were encountered: