-
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 with netcup and DNS Challenge #1706
Comments
What do the certbot logs say? (see #1271 (comment)) |
Do you mean the log from /var/log/letsencrypt/letsencrypt.log ? |
Yes. |
Here is the log
Is the destination in Netcup correct pw-local.MYDOMAIN? Do I need a token there? |
Hm, it's weird that it is an incorrect TXT record and not just no record at all. Have you tried increasing the propagation seconds? By default they seem to be just 10 seconds which might not be enough. |
I set propagation to 300 seconds but it runs into a timeout. What should be the TXT record look like? |
Hi everybody, I have a similar issue, trying to get a new certificate for a subdomainn here is the content of letsencrypt.log :
Here is my docker compose : version: '2'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
DNS_CLOUDFLARE_CREDENTIALS: "/cloudflare.ini"
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
- ./log:/var/log/letsencrypt
- ./letsencrypt.ini:/etc/letsencrypt.ini:rw
- ./cloudflare.ini:/cloudflare.ini:ro
db:
ports:
- '3307:3306'
image: 'mariadb'
restart: unless-stopped
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
volumes:
- ./data/mysql:/var/lib/mysql If someone has an idea about this issue, I would be very glad to read it. Thanks ! |
@sumadark Your problem has nothing to do with the problem discussed in this issue, you are not even using netcup as the domain provider. And I'm pretty sure your issue is due to your own custom |
Thanks for your reply... |
This might be a bit late, but for the sake of maybe closing the issue here is what I found when fixing a similar problem with the DNS challenge for the provider netcup:
I believe the reason the DNS challenge failed with the "Incorrect TXT record" error is that @TWART016 manually created the So to fix the issue with the DNS challenge:
After 8-10 minutes you should have your certificate. |
I have an simular issue, and i tried to set the propagation 480 but that runs in a timeout then ... Is there a way to increase the timeout? |
The Content of the log-file
|
Same here. I opened coldfix/certbot-dns-netcup#28 to let https://github.com/coldfix/certbot-dns-netcup pick a default time which should work. I needs to be above 600 as the zone reload time of Netcup is 10 Minutes, confirmed by many in Netcup's customer forum. @LukasOchmann https://pypi.org/project/certbot-dns-netcup/ says at least 600 seconds is needed for Netcup (and likely even then may need some tries), and 900 seconds should really work. On the Nginx-proxy-manager side, the Nginx-proxy-manager Web UI should be fixed to not time out after just a minute to allow for longer DNS Challenge propagation times: Currently, it shows a red error bar long before that, but While waiting, to check the status, you can open a shell in the container and run After you see the successfully https://github.com/coldfix/certbot-dns-netcup See coldfix/certbot-dns-netcup#28 Update: As confirmed in German forum discussions in forum.netcup.de, the observation of customers is that Netcup runs the actual DNS zone updates every 15 minutes, apparently on a cron-like schedule each hour, seemingly like starting at minute |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Describe the bug
I want to access my internal password management (vaultwarden) with NPM. Therefore I created in Netcup an A-Record with Destination my internal IP 192.168.178.15. Also I added a TXT entry with Destination: pw-local.MYDOMAIN.
In NPM I created a proxy host and Forward to my password management. In SSL I want to create a certificate with Use a
DNS Challenge
. I selected netcup as the provider and set dns_netcup_customer_id , dns_netcup_api_key and dns_netcup_api_password. After save I get aInternal Error
Message.In Docker Logs I see
Inside letsencrypt.log:
"Incorrect TXT record \"pw-local.mydomain.de\" found at _acme-challenge.pw-local.mydomain.de",
Nginx Proxy Manager Version
2.9.13
Operating System
Ubuntu 18.04.4 LTS (Bionic Beaver) with Docker
Edit: If I add the domain to an other proxy host in NGINX the website can be opend but of couse with an certificate error.
Without a certificate it is not possible to access the website.
The text was updated successfully, but these errors were encountered: