NitroPack’s Cloud API must communicate with your website to deliver fast page speeds, caching, and optimizations. If your firewall, security plugin, or hosting provider blocks NitroPack’s IPs, you may experience issues like 403 Forbidden errors or failed optimizations.
Here’s everything you need to know to guarantee nothing’s preventing NitroPack from optimizing your websites.
NitroPack’s IP Addresses to Allowlist
Make sure the following IPs are always allowed in your security settings:
178.62.81.205
46.101.77.196
178.62.71.222
159.65.180.53
34.89.113.53
34.147.235.168
35.246.2.61
104.154.182.50
When Do You Need to Allowlist NitroPack’s IPs?
The telltale signs that you need to allowlist NitroPack’s IPs are:
Optimizations fail in your NitroPack dashboard.
You see 403 Forbidden errors in server logs.
Your hosting provider has strict bot protection (e.g., Cloudways, Kinsta).
Your .htaccess file has strict IP restrictions.
Also, if you’re seeing error messages or pending/failing optimizations and you’re using WordPress security plugins (e.g., Wordfence, Sucuri), then you might need to finetune that integration as well.
How to Allowlist NitroPack’s IPs with Hosting Providers
Many hosts have built-in firewalls that may block NitroPack. Below are instructions for popular providers:
1. WP Engine
✅ No setup needed – NitroPack works out of the box.
2. Hostinger
Go to hPanel > Advanced > IP Manager
Add NitroPack’s IPs as Allowed
3. Cloudways
Warning: These instructions apply to Cloudways users on the "New Interface" and utilizing the "Cloudways Flexible Product." If your Cloudways setup differs, these steps will not apply. Please contact Cloudways support for tailored assistance.
Sign in to your Cloudways Platform.
From the top menu, click Servers.
Choose the specific server hosting your website.
On the left-hand side menu, click Security.
Ensure the Firewall tab is selected.
Click on Add custom rules.
Select the IP Address tab.
Enter each NitroPack IP address individually.
178.62.81.205
46.101.77.196
178.62.71.222
159.65.180.53
34.89.113.53
34.147.235.168
35.246.2.61
104.154.182.50
Leave "Time To Live (TTL)" and "Comment" empty.
Click Add Rule for each IP.
For a more detailed walkthrough, please refer to this article or reach out to Cloudways' Support team.
4. Kinsta
If using Kinsta’s native Cloudflare, no action is needed
For custom Cloudflare, follow NitroPack’s Cloudflare guide
5. SiteGround
No need to allowlist IPs
Make sure to disable the SG Optimizer plugin (conflicts with NitroPack)
For all other hosts, such as GoDaddy, Bluehost, Pantheon, A2 Hosting, HostGator, HostPapa, etc., NitroPack should work out of the box. If you still face issues, please check their firewall settings for IP allow listing options. You can also contact your hosting provider for further assistance.
How to Allowlist NitroPack's IPs in WordPress Security Plugins
1. Wordfence
Step 1: Go to Wordfence > Firewall > All Firewall Options > Allowlisted IP addresses that bypass all rules.
Step 2: Add NitroPack’s IPs in CIDR* format:
178.62.81.205/32
46.101.77.196/32
178.62.71.222/32
159.65.180.53/32
34.89.113.53
34.147.235.168
35.246.2.61
104.154.182.50
Note: CIDR format (like 178.62.81.205/32) is just a way to specify exactly which IP addresses to allow where "/32" means only that exact address.
2. Jetpack
Step 1: Go to Jetpack > Protect.
Step 2: Add NitroPack’s IPs to the Allowlist.
For other security plugins like All-in-One Security (AIOS), Really Simple Security, SG Security, Solid Security, Limit Login Attempts Reloaded, Sucuri, etc. no extra configuration should be necessary.
Important: The following security plugins do not require any extra configuration—All-in-One Security (AIOS), Really Simple Security, SG Security, Solid Security, Limit Login Attempts Reloaded, and Sucuri.
How to Allowlist NitroPack's IPs in Firewalls
1. Sucuri Firewall
Step 1: Log in to the Sucuri dashboard.
Step 2: Go to Security > Access Control > Allowlist IPs.
Step 3: Add NitroPack’s IPs.
If you are using Sucuri, read the following article to ensure the NitroPack and Sucuri caches are synced.
2. Cloudflare
Step 1: Go to Account Home > Choose your domain > Security > WAF > Firewall Rules.
Step 2: Create a new rule:
Field: IP Address
Operator: "is in"
Value:
178.62.81.205/32
46.101.77.196/32
178.62.71.222/32
159.65.180.53/32
34.89.113.53
34.147.235.168
35.246.2.61
104.154.182.50
Action: Allow
Priority: Set higher than any blocking rules (lower number = higher priority)
Important: If you're using Cloudflare's Free plan, after entering the new IPs, from the "Choose action" drop-down menu, select "Skip."
Allowlisting in `.htaccess`
If your .htaccess has ‘Deny from all’, place this above it:
For Apache 2.2
Order deny,allow
Deny from all
Allow from 178.62.81.205
Allow from 46.101.77.196
# Add other NitroPack IPs
Apache 2.4+
<RequireAny>
Require ip 178.62.81.205 46.101.77.196 178.62.71.222 159.65.180.53 34.89.113.53 34.147.235.168 35.246.2.61 104.154.182.50
</RequireAny>
Important: If your .htaccess has `Require all denied`, replace it with the above rule. Test changes to avoid breaking site access.
Troubleshooting
If after allowlisting all NitroPack IPs you are still blocked, please check:
Server logs for 403 errors.
Hosting restrictions (e.g., Cloudflare’s "Under Attack" mode).
Multiple security layers (e.g., both Wordfence & Cloudflare blocking NitroPack).
📌 If you need any assistance or have questions, reach out to our support team at [email protected]