Originally created by @PeterDaveHello on GitHub (Oct 1, 2016).
Sorry that I'm not sure if this is a problem of dehydrated, it only appear on one of my servers with Ubuntu 16.04 LTS, and the error message is very not help.
Tried v2.0~3.1, same version and same parameters can work on one another server.
Here is the error message:
# INFO: Using main config file /etc/letsencrypt.sh/config.sh
+ ERROR: An error occurred while sending get-request to https://acme-v01.api.letsencrypt.org/directory (Status 403)
Details:
<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://acme-v01.api.letsencrypt.org/directory" on this server.<P>
Reference #18.75481160.1475353435.800eb1b
</BODY>
</HTML>
I tried to use a browser to see the message, I got this
Access Denied
You don't have permission to access "http://acme-staging.api.letsencrypt.org/" on this server.
Reference #18.75481160.1475352241.7fbb713
Googled (also duckduckgo) 18.75481160.1475352241.7fbb713 but got nothing, have no idea about how to do to debug this problem, any suggest will be appriaciated, thanks!
Originally created by @PeterDaveHello on GitHub (Oct 1, 2016).
Sorry that I'm not sure if this is a problem of dehydrated, it only appear on one of my servers with Ubuntu 16.04 LTS, and the error message is very not help.
Tried v2.0~3.1, same version and same parameters can work on one another server.
Here is the error message:
```
# INFO: Using main config file /etc/letsencrypt.sh/config.sh
+ ERROR: An error occurred while sending get-request to https://acme-v01.api.letsencrypt.org/directory (Status 403)
Details:
<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD><BODY>
<H1>Access Denied</H1>
You don't have permission to access "http://acme-v01.api.letsencrypt.org/directory" on this server.<P>
Reference #18.75481160.1475353435.800eb1b
</BODY>
</HTML>
```
I tried to use a browser to see the message, I got this
```
Access Denied
You don't have permission to access "http://acme-staging.api.letsencrypt.org/" on this server.
Reference #18.75481160.1475352241.7fbb713
```
Googled (also duckduckgo) 18.75481160.1475352241.7fbb713 but got nothing, have no idea about how to do to debug this problem, any suggest will be appriaciated, thanks!
@PeterDaveHello commented on GitHub (Oct 1, 2016):
@adduxa I thought the part you mentioned is just a mistake from the error message returned from ACME server, the CA variable in the script is 100% https no problem, and as I say, the same same script, different 3 versions, run on my two different server, got two different result.
@PeterDaveHello commented on GitHub (Oct 1, 2016):
@adduxa I thought the part you mentioned is just a mistake from the error message returned from ACME server, the CA variable in the script is 100% https no problem, and as I say, the same same script, different 3 versions, run on my two different server, got two different result.
It's been a few weeks since did this on Ubuntu 16.04 LTS but it worked. But I recall having similar issues until I got the correct CA files, and particularly the Intermed. CA. I was using Let’s Encrypt Authority X1 which is retired: X3 is current.
@ccjon commented on GitHub (Jan 15, 2017):
It's been a few weeks since did this on Ubuntu 16.04 LTS but it worked. But I recall having similar issues until I got the correct CA files, and particularly the Intermed. CA. I was using Let’s Encrypt Authority X1 which is retired: X3 is current.
Not sure what was going on here, but it seems to me that Let's Encrypt just locked you out for some reason, this doesn't seem to have anything to do with dehydrated.
@lukas2511 commented on GitHub (Jan 30, 2017):
Not sure what was going on here, but it seems to me that Let's Encrypt just locked you out for some reason, this doesn't seem to have anything to do with dehydrated.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @PeterDaveHello on GitHub (Oct 1, 2016).
Sorry that I'm not sure if this is a problem of dehydrated, it only appear on one of my servers with Ubuntu 16.04 LTS, and the error message is very not help.
Tried v2.0~3.1, same version and same parameters can work on one another server.
Here is the error message:
I tried to use a browser to see the message, I got this
Googled (also duckduckgo) 18.75481160.1475352241.7fbb713 but got nothing, have no idea about how to do to debug this problem, any suggest will be appriaciated, thanks!
@adduxa commented on GitHub (Oct 1, 2016):
It seems like you tried to get access to ACME server via http instead of https (CA variable in config file)
@PeterDaveHello commented on GitHub (Oct 1, 2016):
@adduxa I thought the part you mentioned is just a mistake from the error message returned from ACME server, the CA variable in the script is 100% https no problem, and as I say, the same same script, different 3 versions, run on my two different server, got two different result.
@adduxa commented on GitHub (Oct 2, 2016):
Oh.. Ok, this is strange
@ccjon commented on GitHub (Jan 15, 2017):
It's been a few weeks since did this on Ubuntu 16.04 LTS but it worked. But I recall having similar issues until I got the correct CA files, and particularly the Intermed. CA. I was using Let’s Encrypt Authority X1 which is retired: X3 is current.
@lukas2511 commented on GitHub (Jan 30, 2017):
Not sure what was going on here, but it seems to me that Let's Encrypt just locked you out for some reason, this doesn't seem to have anything to do with dehydrated.