standalone, I 'm trying to issue a fresh certificate for my domain automation.minervatech.xyz but getting connection timeout. Kindly guide how to fix the issue and issue certificate ..Attached is the reference of the error
1 Like
that's the reason you shouldn't use standalone, it's hard to debug.
Start a simple webserver on your domain and use another authenticator.
1 Like
Are you on the right system?
Please show the output of:
curl -4 ifconfig.co
1 Like
If your DNS records turn out to be correct and you're on the right system, this is probably a sign of a firewall intentionally blocking inbound connections on port 80. (You might not otherwise notice this behavior because your HTTPS connections are normally sent over port 443.)
1 Like
I asked because I see a running web server there:
curl -Iki automation.minervatech.xyz/
HTTP/1.1 301 Moved Permanently
connection: keep-alive
content-length: 0
location: https://www.blynk.cc
access-control-allow-origin: *
But it seems to be particular about the /.well-known/acme-challenge/ requests...
which go unanswered and then time-out.
So --standalone may not be the right approach.
Or it might be... we simply don't know enough about their system setup.
1 Like
I have attached the screenshot, actually I am trying to issue certificate for Blynk IOT platform
1 Like
port 80 is kept open at AWS security group along with 443
That IP address looks different from the one that automation.minervatech.xyz points to. Do you know why that would be?
Are you not running Certbot on the same device where you intend to use the certificate?
2 Likes
http://automation.minervatech.xyz/ redirects to: https://www.blynk.cc
Name: blynk.io
Address: 185.203.72.17
Aliases: www.blynk.cc
[yet another IP]
1 Like
actually to access blynk port 9443 is used and that is where my server page will load else it directs to the brands page at port 80
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.