Need unblock IP

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., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:unused

I ran this command:letsencrypt-auto certonly

It produced this output:
An unexpected error occurred:
There were too many requests of a given type ::
Your IP,, has been blocked due to ridiculously excessive traffic.
Once this is corrected you may request this be reviewed on our forum

My web server is (include version):caddy

The operating system my web server runs on is (include version):centos 7

My hosting provider, if applicable, is:vultr

I can login to a root shell on my machine (yes or no, or I don’t know):yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):noVNC

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):none

1 Like

Hi @znssky


same problem.

I haven’t heard of Certbot getting blocked like that.

Have you used other ACME clients before? In particular, older versions of cert-manager, or the software mentioned in the other thread?

How long have you had that IP address? Has it always been blocked?

One year.
I`d like to try caddy this month,but the ip has been blocked.

This is probably related to the issue at IP has been blocked. we recently blocked a bunch of IPs from misconfigured Caddy instances, possibly related to a bundle called V2Ray (more details in the other thread).


Yes,i used V2Ray with mKCP as transport protocols by one year.
I’d like to try Caddy in this month.


Thank you for the information. Please post this extra information:

  • When did you first install Caddy?
  • What commands did you use to configure Caddy?
  • What is your Caddy config?
  • What is in your Caddy logs?
  • What is in your system logs?
  • What is your domain name?



When did you first install Caddy?
The other day

What commands did you use to configure Caddy?

What is your Caddy config? {
timeouts none
proxy / {

What is in your Caddy logs?
Activating Privacy features… done.
Serving HTTP on port 2015

What is in your system logs?
failed to server http for WebSocket >
accept tcp [::]:35716: use of closed network connection

What is your domain name?

1 Like

(One of your posts was caught by the forum’s automatic spam filter for a few minutes. Sorry.)

1 Like

@znssky Thanks, we’re making progress. Can you please attach the full systemd Caddy process logs? I’d like to know what ACME errors your instance received from the beginning… that would be very helpful.

You can attach or link to the full log file.

That’s all


Thanks, but I am looking for the logs from when the error started occurring, or from when you first started running Caddy. If running with systemd, you should be able to see some history with journalctl.

Thanks for the update! According to no certificate was ever issued for However, your IP address was sending new-acct requests for a long time. It sounds like maybe what happened was this:

  1. V2Ray set up a default Caddy config (with no hostname) that made Caddy try to create an account over and over again.
  2. We (Let’s Encrypt) blocked traffic.
  3. You tried to configure Caddy and then run it interactively, and got an error message.

Does that sound accurate?

@mholt, with the default config built by, would Caddy go ahead and create an account? Or would it wait to have a domain configured? What would happen if $domain in that script were empty?

1 Like

Yes, I think it would create an account, but I don’t think $domain in that script is empty.

I’m willing to bet that the process was being restarted over and over without regard for exit code, though: CertMagic’s retry loop has a hard limit at 3 attempts before returning an error:

If $domain was empty in this case, Caddy should also exit with an error before even getting to this point since server blocks without any keys are not allowed, so it’d be a parse error, basically, before the server even starts up.

So that’s why I think $domain is probably set, but I don’t know for sure without full log history.

Remember that before /new-acct is called, lego needs to set up a client which requires invoking the directory URL – only once that is successful can lego proceed to call /new-acct. So, it wasn’t IP-blocked from the beginning. Something else caused it to return an error at startup originally.

I am willing to bet it can’t write to storage. If it could, it would have re-used that account and not called /new-acct.

UNLESS, of course, the random email address is changing with every process restart. A new email address means a new account, even if it is saving to disk correctly.

I recently pushed a commit to CertMagic which tests the storage before attempting any ACME calls:, but this will not solve the underlying problem…


From what I seen in our logs, each IP address consistently uses the same random email address consistently, so I don’t think that’s what’s happening.

BTW one quirk that I hadn’t mentioned before: For a given IP address, when it first starts sending traffic with this problem, it sends clusters of five requests: /directory, /acme/new-nonce, /acme/new-acct, /acmt/new-acct, /acme/new-acct. The first new-acct request succeeds and returns 201. However, the next two new-acct requests generate an error: 400 :: malformed :: No embedded JWK in JWS header. Then the process repeats 4 seconds later, with the same pattern, until the requests start returning 429 (rate limited).

Unfortunately we don’t have the raw JWS header, but if you can think of any situation that could cause Caddy to send a new-acct request that’s missing a JWK, that might be an interesting avenue.


One more question, @znssky: Where did you install V2Ray from? What commands did you use to install V2Ray?


Thanks for the details. I’m almost certain it has an error writing to storage. I’ll explain what I think is happening to show why:

  1. When Caddy tries to obtain a cert, it first must create an ACME client, which is a struct initialized in memory with some state resulting from a negotiation from the ACME CA. newACMEClient gets called, and the very first thing it does is try to get a user:

  2. getUser will load the user with the given email address from storage, or specifically if it doesn’t exist, it will create a new user in memory (basically just generates a private key): – it does NOT store the user at this point (no point in doing so, since the user does not have an account).

  3. On the first run, a user gets created as expected. After some input validation, we see that no ACME client for the given CA & email exists in memory yet, so we have to create a new one. To do so, we first need to make a lego config, which takes the user as input:

  4. After preparing the lego config, we finally ask lego to create an ACME client: - this is where the initial call to /directory happens. (Probably /new-nonce too, actually. I’m not super familiar here.) Before attempting to register a new user, we cache the client in memory for future use, to avoid hitting /directory more than once:

  5. In any case, the very next thing to do is ensure that the user has an account. If not, one is created: - you can see that immediately after creating the registration/account, the user (account info) is saved to storage. I believe writing this resource to storage is what fails.

  6. If an error is returned at this point, it goes up to the caller in this loop: – it retries (newer versions of the code wait before retrying, and only if the HTTP status is not 429).

  7. We repeat from step 1 again, except this time, when we get to step 3, an ACME client for the user email already exists in our in-memory cache, because we already queried /directory and we don’t need to do that again. So we skip to step 5. The cached client’s user does not have an account because there was an error storing it. This fails again, and the loop repeats one more time until the process exits.

  8. The process is apparently restarted in a tight loop.

That should explain the “quirk” you described with the pattern of requests.

1 Like

Aha, sorry, upon a closer reading, I see that you’ve verified that the initial new-acct succeeds, and the subsequent requests have:

This is interesting, probably some mismatch between how lego expects to be used and how it’s actually being used. I’ll look into that.

However, I do think that’s a red herring to what’s actually going on at the crux of the excessive requests.
bash <(curl -s -L

Perhaps relevant -

[ERROR] Making new certificate manager: could not save user: mkdir /etc/ssl/caddy/acme: read-only file system