How to prevent IP blocking?
Summary
Whitelisting allows Clonable to access and translate your website correctly when your server blocks unknown traffic. If your website uses a firewall, security plugin, or IP restriction, you may need to whitelist Clonable’s IP addresses. This ensures your clone works properly and prevents loading errors, incomplete translations, or blocked requests.
FAQ
When do I need to whitelist Clonable?
When your website is protected by a firewall, IP restriction, or security tool that blocks unknown visitors.
What happens if I don’t whitelist?
Your clone may show errors, missing content, or fail to load.
Is whitelisting always required?
No. Only if your hosting or security setup blocks Clonable’s requests.
⏱️ Reading time: 4–6 minutes
What is whitelisting?
Whitelisting means allowing specific IP addresses to access your website.
Some servers, firewalls, or security plugins block unknown traffic automatically. Since Clonable accesses your website to create and update your clone, those requests can be blocked.
If that happens, Clonable cannot retrieve your content properly.
Typical symptoms include:
- 403 Forbidden errors
- 500 Server errors
- Empty or partially translated pages
- Images or scripts not loading
If your clone is not working as expected and your website uses security protection, whitelisting is often the fix.
When is whitelisting required?
You may need to whitelist Clonable if you use:
- A server-level firewall
- A hosting provider with strict security settings
- A WordPress security plugin
- IP-based access restrictions
- Bot protection or rate limiting
- Cloud-based firewalls
If your website is publicly accessible without restrictions, you usually do not need to whitelist anything.
Clonable IP addresses to whitelist
To allow Clonable to access your website, add the official Clonable IP addresses to your firewall or security whitelist.
Add the following IP addresses:
Server | IPv4 Address | IPv6 Address |
|---|---|---|
clonable-ams-1 | 80.69.93.77 | 2a01:7c8:bb06:71::/64 |
clonable-rtm-1 | 87.253.157.237 | 2a01:7c8:bb07:b4::/64 |
Make sure they are added as allowed or trusted IP addresses.
Where to add the whitelist
The exact location depends on your setup.
Common places include:
Hosting control panel
Look for:
- Firewall settings
- IP access management
- Security settings
- Server protection
WordPress security plugins
Check your plugin settings for:
- IP allowlist
- Trusted IP addresses
- Firewall rules
Cloud firewalls
If you use a cloud firewall service, add the IP addresses to the allowlist in your dashboard.
How to check if whitelisting worked
After adding the IP addresses:
- Clear any caching layers
- Reload your clone
- Check for error messages
- Verify that pages load fully
If issues persist:
- Double-check that all IP addresses are added
- Make sure there are no additional security layers blocking access
- Contact your hosting provider for confirmation
Common issues
Here are the most common mistakes:
- Only adding one of the required IP addresses
- Adding the IP addresses in the wrong firewall section
- Forgetting to save or apply firewall changes
- Blocking by country or ASN instead of by IP
- Additional bot protection still blocking traffic
If your clone worked before and suddenly stopped, check whether your hosting provider recently enabled new security rules.
504 error
If a 504 error occurs when visiting a clone, it is always due to one of the two problems below
The IP address of the original site has changed
If the IP address of the original site has changed, the old IP address will no longer work. You can change this IP address under origin server in the site settings under advanced.
Clonable is blocked
Is the origin server set up correctly? If so, Clonable is probably blocked. To resolve this, the Clonable servers must be unblocked and added to a whitelist. How to do this depends on the hosting provider. The most up-to-date server information can be found higher up on this page.

502, bad gateway
If a 502 Bad gateway error appears when visiting a clone, this means that the IP address of the original server is set incorrectly. To resolve this, first find the correct IP address and then set it as the origin server in the site settings under advanced:
Tags
server access, firewall configuration, IP allowlist, hosting security, 403 error, blocked requests, infrastructure setup
Updated on: 22/02/2026
Thank you!
