Ip/domain got blocked accidently, help needed

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.

There was some problem on server and ran this command many times. Turns out it was sending requests: sudo gitlab-ctl reconfigure

Not knowing about rate limit i accidently got banned, just wanted to make gitlab work on https instead of http. Can anyone help to unban so i finally configure it.

#2

Without the requested information, it’s awfully hard to give help. If you had 5 failed attempts, that limit passes in 1 hour. But if you did created 5 valid certificates, then that limit takes a week to pass. Check to see if you have any valid certificates. If so, you should be able to use one of these. But without providing any information, it’s like asking someone to fix what’s in a box without opening the box. :wink:

2 Likes
#3

Thanks for answering.

It did not generate any certificate. I checked it here https://crt.sh/?Identity=

It gives this error.
An unexpected error occurred:
There were too many requests of a given type :: Error creating new account :: too many registrations for this IP: see https://letsencrypt.org/docs/rate-limits/

1 Like
#4

Can you run:

certbot certificates

Post output here

If none were created, the rate limit should be gone by now and you should be free to proceed. I recommend using the --dry-run command as this tests your commands without actually running them against the main server, avoiding rate limits.

See explanation here:

–dry-run Perform a test run of the client, obtaining test
(invalid) certificates but not saving them to disk.
This can currently only be used with the ‘certonly’
and ‘renew’ subcommands. Note: Although --dry-run
tries to avoid making any persistent changes on a
system, it is not completely side-effect free: if used
with webserver authenticator plugins like apache and
nginx, it makes and then reverts temporary config
changes in order to obtain test certificates, and
reloads webservers to deploy and then roll back those
changes. It also calls --pre-hook and --post-hook
commands if they are defined because they may be
necessary to accurately simulate renewal. --deploy-
hook commands are not called. (default: False)

Commands

Let us know mate…

2 Likes
#5

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