Service unreachable or access blocked: unblocking
Updated on
Access to your site or LRob services blocked: what to do?
Sometimes you may no longer be able to reach your site, your Plesk interface, your e-mail, or your database. Since LRob monitors services 24/7 and intervenes proactively, in most cases the unavailability you notice is rather a block linked to a security mechanism that protects all of our servers and our customers.
Here is how to recognize a block and, above all, how to get unblocked quickly.
Check the status of LRob services
First, if you are unsure about the availability of one of your services, you can check whether the problem is global or not using the public monitoring here: https://status.lrob.net
Try through another connection
If your services are unreachable over 5G, try over Wi-Fi, and vice versa. If you regain access to your services, then it really is a block on your IP rather than a technical problem.
Check that your domain name is active and publicly reachable
You can check your domain’s status and DNS pointing through the LRob service on this page: https://www.lrob.fr/domain-info/
If your domain has, for example, a “ClientHold” status, it means it is no longer reachable. In that case, contact your registrar for more information. If your domain is registered through LRob, contact your support.
How to submit an unblock request
From the device that cannot reach your service:
- Go to the page: https://www.lrob.fr/support/deblocage-ip/
- Enter:
- The domain name or site you are trying to reach
- Your e-mail address to identify you and allow us to get back to you if needed
- The anti-bot captcha
Your IP address will be unblocked as soon as possible.
In an emergency, do not hesitate to call us on the usual support number for immediate intervention.
Why can your access be blocked?
🔐 An active security system: Fail2ban
Our servers use Fail2ban, a security tool that monitors incoming connections and automatically blocks IP addresses that behave suspiciously or have too many failures.
This can affect you even if you are the site owner or a legitimate user. This block is temporary, but it can prevent you from accessing your services.
What are the most frequent causes of blocking?
❌ Login errors
- Repeated incorrect entry of your password in:
- an e-mail client (Thunderbird, Outlook…),
- WordPress
- a webmail,
- Plesk,
- or an FTP tool.
🔥 Web application firewall
Some WordPress plugins or CMSs can trigger security alerts by mistake by sending abnormal requests. The web application firewall generates 403 Forbidden errors, visible in the logs, which you can access through your Plesk control panel. Too many 403 errors in a row can lead to a block.
🧩 Problematic plugins or scripts
Some plugins or extensions automatically perform actions that can be interpreted as attacks (looping requests, scans, injections…).
📝 File containing special characters
A simple file containing a particular character (such as an apostrophe in an uploaded file name) can be perceived as an injection attempt.
Which services can be affected?
When an IP is blocked, all associated services are unreachable from that IP:
- Plesk interface
- E-mail (IMAP / SMTP / Webmail)
- Hosted websites
- FTP
- Databases (MySQL, MariaDB…)
The visible error is often a time-out: the page does not load or eventually shows a timeout error.
Why is this block important?
Even though it can be a nuisance in some cases, this security system is crucial for protecting your site:
- 🛡️ It effectively stops brute-force attacks and automated scans.
- ⚡ It greatly reduces server load (up to 90% of useless requests blocked).
- 🌱 It improves performance for real users and reduces energy consumption (eco-responsible hosting).