Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output:
this is the log of my error: error1.txt (17.5 KB)
My web server is (include version):
Nginx proxy manager on docker with the Nginx version: openresty/220.127.116.11
The operating system my web server runs on is (include version):
ubuntu:21.04 ARM version
My hosting provider, if applicable, is:
Self hosted- Raspberry pi 4
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no, I use terminal
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 1.19.0
I had my domains on Namecheap.
Then transferred them to cloudflare. (the transferation is not complete yet).
with Nginx proxy manager I am trying to make have a subdomain, which is manage.medidentkala.com
this works fine with port 80.
When I try to get SSL certificate, I can not and get the errors which you can see in logs.
After some errors also will get banned by "too many request limit",
Also when I had my domains hosted on Namecheap, had the same problem,
Also issued the cloudflare token. but still does not work.
Any help is appreciated.
Hello @griffin .
Thanks for quick reply.
As I said, I had tried multiple times and made multiple domains, and issued certificates for them. Maybe accidentally send wrong log file, because I got a bit tired
I issued a new certificate now and hereerror.txt (110.5 KB) is the log file of it.
Thanks for helping out
Hey @griffin , your answer was totally right.
The problem was, I have accidentally white listed my own public IP address.
so I could check the website from home and couldn't understand the problem.
bur after you showing me the ports are closed, then got that there is a problem with network firewalls.
allowed all IP addresses to reach the website, and could easily issue SSL certificate, everything works fine.