Blocked access to your LRob site or services: what can you do?
It may happen that you can no longer access your site, your Plesk interface, your emails or your database. As LRob monitors services 24/7 and intervenes proactively, in most cases, the unavailability you're experiencing is more likely to be a blockage related to a security mechanism that protects all our servers and customers.
Here's how to recognize a blockage, and more importantly, how to get unstuck fast.
Check the status of LRob services
First of all, if you have any doubts about the accessibility of one of your services, you can check whether the concern is global or not, by using the public monitoring here : https://uptime.lrob.net/status/lrob
Try another connection
If your services are inaccessible on 5G, try wifi, and vice versa. If you regain access to your services, then it's a blocking of your IP rather than a technical problem.
Check that your domain name is active and publicly accessible
You can check your domain's status and DNS status using the LRob service on this page: https://www.lrob.fr/domain-info/
If, for example, your domain is on "ClientHold" status, this means that it is no longer accessible. In this case, contact your registrar for more information. If your domain is registered via LRob, contact your support team.
How to make an unlock request
From the device not accessing your service :
- Go to the : https://www.lrob.fr/support/deblocage-ip/
- Inform :
- Visit domain name or site you are trying to access
- Your email address to identify you and enable us to contact you if necessary
- Visit captcha anti-robot
Your IP address will be unblocked as soon as possible.
In case of emergency, don't hesitate to call us on our usual support number for immediate intervention.
Why can your access be blocked?
🔐 An active security system: Fail2ban
Our servers use Fail2bana security tool that monitors incoming connections and automatically blocks IP addresses that behave suspiciously or fail too many times.
This may concern you even if you are the site owner or a legitimate user. This blocking is temporarybut it can prevent you from accessing your services.
What are the most common causes of blockages?
❌ Connection errors
- Repeated incorrect entry of your password in :
- an email client (Thunderbird, Outlook...),
- WordPress
- webmail,
- Plesk,
- or an FTP tool.
🔥 Application firewall
Some WordPress plugins or CMS may mistakenly trigger security alerts by sending abnormal requests. The application firewall generates 403 Forbidden errors, visible in the logs you can access via your Plesk control panel. Too many 403 errors in succession can lead to blocking.
🧩 Plugins or problematic scripts
Some plugins or extensions automatically execute actions that can be interpreted as attacks (loop requests, scans, injections, etc.).
📝 File containing special characters
A single file containing a particular character (such as a apostrophe in an uploaded file name) can be perceived as an injection attempt.
Which services may be affected?
When an IP is blocked, all associated services are inaccessible from this IP :
- Plesk interface
- Emails (IMAP / SMTP / Webmail)
- Hosted websites
- FTP
- Databases (MySQL, MariaDB...)
The visible error is often a time-out The page does not load or ends up displaying a timeout error.
Why is this block important?
Even if this can be restrictive in certain cases, this safety system is the ideal solution. crucial for protecting your site :
- 🛡️ It effectively stops brute force attacks and automatic scans.
- ⚡ It significantly reduces server load (up to 90 % of useless requests blocked).
- 🌱 It improves performance for real users and reduces energy consumption (eco-responsible hosting).
