Need unblock my IP---thanks for your help

Help
1

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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: www.da-fa.tk

I ran this command: caddy

It produced this output: Activating privacy features… 2019/10/09 11:31:53 get directory at ‘https://acme-v02.api.letsencrypt.org/directory’: acme: error: 0 :: GET :: https://acme-v02.api.letsencrypt.org/directory :: urn:ietf:params:acme:error:rateLimited :: Your IP, 140.238.48.104, has been blocked due to ridiculously excessive traffic. Once this is corrected you may request this be reviewed on our forum https://community.letsencrypt.org , url:

My web server is (include version): Caddy
The operating system my web server runs on is (include version): redhat7 4.14.35-1902.5.2.2.el7uek.x86_64

My hosting provider, if applicable, is: VPS

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):

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

2

Hi @ChenDaMin

there are some other topics, may be the same problem. Caddy plus that `ridiculously excessive traffic'.

Check

Do you use V2Ray?

3

yes， I use V2ray + Caddy

4

This is a new setup server, i don’t understand “ridiculously excessive traffic” .

5

Looks like a general problem with that V2ray, so that tool produces an endless loop.

6

wait,… I try close v2ray. and try again.

7

I closed v2ray but the issue still exists. :joy:

8

@ChenDaMin,

We’re aware of issues with V2Ray. Until we explicitly remove the ratelimit for your IP, you will continue receiving the ratelimit.

Can you please post the following information:

  • Your full Caddyfile (without changes)
  • Your full logs (from your Caddy process log and/or systemd/journalctl)
  • Full and complete error messages
2 Likes
9

It’s not a V2Ray issue. The systemd config file for Caddy (caddy.service) is the problem (see here: https://github.com/233boy/v2ray/issues/347) and should have been fixed. If you use the script by 233boy, upgrading to the latest version might help. Of course, your ip ban needs to be removed first, I think.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.