Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes
Are you sure you're not using someone else's docker image?
Yes
Have you searched for similar issues (both open and closed)?
Yes
Describe the bug
CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Encountered error adding TXT record: {'charset': 'utf-8', 'error_code': 'ACCESS_DENIED_FROM_IP', 'error_params': {'command_name': 'zone/add_txt'}, 'error_text': 'Access to API from this IP denied', 'input_params': {'domains': [{'dname': 'example.ru'}], 'input_format': 'json', 'io_encoding': 'utf8', 'output_format': 'json', 'password': 'PASSWORD', 'show_input_params': '1', 'subdomain': '_acme-challenge', 'text': '_UP-mx8LMJmvUPr02ashKoKZ24ZQsXTQ9GNfAz-SvtE', 'username': 'USEREMAIL'}, 'messagestore': None, 'result': 'error'}
Encountered error deleting TXT record: {'charset': 'utf-8', 'error_code': 'ACCESS_DENIED_FROM_IP', 'error_params': {'command_name': 'zone/remove_record'}, 'error_text': 'Access to API from this IP denied', 'input_params': {'content': '_UP-mx8LMJmvUPr02ashKoKZ24ZQsXTQ9GNfAz-SvtE', 'domains': [{'dname': 'example.ru'}], 'input_format': 'json', 'io_encoding': 'utf8', 'output_format': 'json', 'password': 'PASSWORD', 'record_type': 'TXT', 'show_input_params': '1', 'subdomain': '_acme-challenge', 'username': 'USEREMAIL'}, 'messagestore': None, 'result': 'error'}
Error communicating with the Reg.ru API: {'charset': 'utf-8', 'error_code': 'ACCESS_DENIED_FROM_IP', 'error_params': {'command_name': 'zone/add_txt'}, 'error_text': 'Access to API from this IP denied', 'input_params': {'domains': [{'dname': 'example.ru'}], 'input_format': 'json', 'io_encoding': 'utf8', 'output_format': 'json', 'password': 'PASSWORD', 'show_input_params': '1', 'subdomain': '_acme-challenge', 'text': '_UP-mx8LMJmvUPr02ashKoKZ24ZQsXTQ9GNfAz-SvtE', 'username': 'USEREMAIL'}, 'messagestore': None, 'result': 'error'}
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.
at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1105:16)
at ChildProcess._handle.onexit (node:internal/child_process:305:5)
Nginx Proxy Manager Version
2.11.3
To Reproduce
Steps to reproduce the behavior:
Go to SSL Certificates tab.
Add SSL Certificate.
Let's Encrypt.
Pick domain name, enter all other valid data.
Click Save.
Get error.
Expected behavior
No error
Operating System
Debian 12.7 x86_64
Additional context
Up-to-date docker
IP is not blocked for sure/not in spam lists/etc. I can issue a cert for reg.ru with certbot/use reg.ru in browser/use API. Don't know why NPM keeps telling me that access is denied. I suspect some internal issue or invalid exception description.
REG.RU demands about whitelisting IP for API usage are also met.
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
Nginx Proxy Manager Version 2.11.3
To Reproduce Steps to reproduce the behavior:
Expected behavior No error
Operating System Debian 12.7 x86_64
Additional context Up-to-date docker
IP is not blocked for sure/not in spam lists/etc. I can issue a cert for reg.ru with certbot/use reg.ru in browser/use API. Don't know why NPM keeps telling me that access is denied. I suspect some internal issue or invalid exception description.
REG.RU demands about whitelisting IP for API usage are also met.