go back to rebel.ca

Rebel Help Centre

Articles in this section

See more

Rebel Plesk Hosting: Why Can’t I Access My Website? (Local Network & IP Blocks)

Avatar
Israel
Updated
Follow

Overview

It can be frustrating when your website (WordPress, Joomla, Drupal, or custom site) loads perfectly on a smartphone's cellular network, but returns a connection error—such as ERR_CONNECTION_TIMED_OUT, HTTP 403 Forbidden, or a blank page—when accessed from a specific home or office Wi-Fi network.
 
When a website hosted on our Plesk Hosting platform is online for the rest of the world but unreachable from your specific location, the issue is typically isolated to one of three distinct layers:
  1. Local Network & Router Routing (Upstream ISP / Local Firewall): Traffic is dropped by your local office router, corporate firewall, or Internet Service Provider (e.g., Shaw, Rogers, Bell) before reaching our server gateway.
     
  2. Server Infrastructure Security (Fail2ban / Imunify360): Automated server firewall rules temporarily block a network address after multiple failed login attempts to email, FTP, or administrative portals (/wp-admin).
     
  3. Application & CMS Security Plugins (WordPress / .htaccess): Security plugins running directly inside your website (such as iThemes Security Pro, Wordfence, or custom .htaccess directives) cache security rules that reject HTTP requests from specific IP addresses.
     

How to Instantly Identify If It's Your Local Network/ISP Issue (Proactive Guide)

By combining Step 1 (Hotspot Test) and Step 3 (Traceroute), you can immediately prove whether the block is on your local network/ISP side versus our web server:
  • How You Know It's 100% Your Local Network or ISP's Issue:
    1. Step 1 (Hotspot Test) PASSES: The site opens immediately when you switch your phone/laptop to a mobile cellular hotspot. (This proves our hosting server, database, and domain are completely healthy).
       
    2. Step 3 (Traceroute) FAILS early or mid-way:
      • If the traceroute stops at Hops 1–2 (192.168.x.x or 10.x.x.x), your office router/firewall is dropping outbound traffic.
         
      • If the traceroute stops mid-way on an ISP hop (like shawcable.net or rogers.com) displaying * * * Request timed out before ever reaching canada14.rebel.com, your Internet Provider is dropping the connection on their network level.
         
  • What You Should Do Immediately If It's Your Issue:
    1. Power Cycle Your Office/Home Router: Unplug your modem and Wi-Fi router for 30 to 60 seconds, then plug them back in. This forces your Internet Service Provider to assign your router a fresh public WAN IP address, which instantly bypasses the bad network route or cached IP block.

       

    2. Check Internal Firewall / IT Settings: If you are in a corporate office, ask your network administrator/IT team to inspect your office firewall security logs for active outbound rules blocking traffic to the web server IP.
       
    3. Contact Your ISP (Shaw / Rogers / Bell): If restarting the router doesn't pull a new IP, contact your ISP's technical support, provide them with your traceroute output, and ask them to clear the cached/stale route to your hosting server IP.
       

Step-by-Step Self-Troubleshooting Guide

Follow this diagnostic checklist to pinpoint the exact layer causing the block and restore access immediately:
 

Step 1: Isolate the Issue with the "Mobile Hotspot" Test

  1. Disconnect your computer or mobile device from your local Wi-Fi network.
  2. Connect to a Mobile Cellular Hotspot from your smartphone.
  3. Open a fresh browser window and attempt to load your website.
  • If the site loads on the Hotspot: Your web hosting server, database, and domain are 100% healthy. The block is strictly isolated to your local network address or ISP routing path.
     
  • If the site fails on the Hotspot: The issue is widespread across all networks. Contact Support right away.

Step 2: Obtain Your Public WAN IP Address

  1. Reconnect to the affected home or office network.
  3. Note down the IP address displayed (e.g., 184.70.195.118). This is your network's public digital address on the internet.

Step 3: Run a Connection Path Check (Traceroute)

A traceroute maps the exact route your connection takes from your computer to our Plesk web server, identifying where traffic stops:
  • Windows: Open Command Prompt (cmd), type tracert yourdomain.com, and press Enter.
     
  • Mac: Open Terminal, type traceroute yourdomain.com, and press Return.
How to Analyze Your Traceroute Results:
  • Healthy Connection (Target Reached): Traffic passes through intermediate hops and finishes cleanly with a reply from the server IP (e.g., canada14.rebel.com [134.195.196.134]).
    If the traceroute completes successfully but you still receive an HTTP 403 Forbidden error in your browser, the connection is reaching our server, but an Application-Level Security Plugin or .htaccess rule inside your website is blocking the request (see Step 5).
  • Local Router Drop (Hops 1–2): The trace stops immediately at 192.168.x.x or 10.x.x.x. Action: Your internal office firewall or router policy is blocking outbound traffic. Contact your IT administrator.
    • ISP Drop (Middle Hops): The trace stops midway on an ISP hop (e.g., shawcable.net or rogers.com) displaying * * * Request timed out. Action: Your Internet Provider is dropping traffic before it reaches our network gateway. Power cycle your modem/router to pull a fresh IP or contact your ISP.

    Step 4: Clear Your Computer’s DNS Cache (Flush DNS)

    Local computers store temporary connection data. Flushing this cache forces your operating system to fetch a fresh, direct route to the web server:
     
  • Windows: Open Command Prompt as Administrator, type ipconfig /flushdns, and press Enter.
    • Mac: Open Terminal, execute sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, enter your Mac admin password, and press Return.

    Step 5: Resolve HTTP 403 Forbidden Errors (WordPress & .htaccess Fix)

    If your traceroute confirms traffic reaches our server but your browser displays an HTTP 403 Forbidden error, a WordPress security plugin (like iThemes Security Pro or Wordfence) or a corrupted .htaccess file is actively blocking your IP.
     
  • Follow these exact steps inside your Plesk Control Panel to clear the block:
     
  • Method A: Regenerate Your .htaccess File (Quickest Fix)
    1. Log into your account dashboard and open your Plesk Hosting Dashboard.
    2. Go to Files > httpdocs (your website's root folder).
    3. Locate the file named .htaccess. Right-click it and select Rename.
    4. Rename it to .htaccess.old and click OK. (This instantly disables any restrictive IP blocks written by security plugins).
    5. Click + Create File at the top, name the new file .htaccess, and paste the following standard WordPress default code:
    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
    1. Save the file and test your website again in an Incognito / Private browser window.
    Method B: Disable Security Plugins Temporarily
    If renaming .htaccess does not clear the 403 error, a security plugin may still be enforcing the rule in your database:
    1. Inside Plesk, navigate to Files > httpdocs > wp-content > plugins.
    2. Locate the folder for your security plugin (e.g., ithemes-security-pro or wordfence).
    3. Right-click the folder and rename it by adding _disabled to the end (e.g., ithemes-security-pro_disabled).
    4. Refresh your website. Once logged back into your WordPress dashboard (/wp-admin), add your office IP (184.70.195.118) to the plugin's Trusted / Whitelisted IP List before removing _disabled from the folder name.

    Summary of Causes & Actionable Solutions

    Issue Identified Root Cause Exact Action to Take
    Local Router Drop (Hops 1–2) Internal office router or corporate firewall security policy dropping outbound connections. Ask your IT administrator to check local network security logs for active outbound restrictions to your server IP.
    ISP Network Drop (Middle Hops) Your Internet Provider (Shaw, Bell, Rogers) is dropping traffic on an intermediate hop. Unplug your office modem/router for 30–60 seconds to pull a fresh public WAN IP address, or contact your ISP.
    Application Lock (HTTP 403) Security plugins (iThemes, Wordfence) or .htaccess rules blocking your IP address. Rename .htaccess to .htaccess.old in Plesk File Manager and recreate it using standard WordPress default code, or append _disabled to the plugin folder name inside /wp-content/plugins/.
    Server Firewall Lock Imunify360 or Fail2ban triggered by repeated wrong passwords (Webmail, FTP, /wp-admin). Contact Support with your IP from (http://myip.rebel.com/). Our team will clear your IP from the server firewall whitelist.

    Escalating to Our Support Team

    If you have completed these steps and your website remains unreachable from your network, please contact our Support Team with the following details so our Systems Engineering team can resolve it promptly:
    1. Your Domain Name.
    2. Your Public WAN IP Address (from (http://myip.rebel.com/)).
    3. A copy or screenshot of your Traceroute results.
    4. Confirmation of whether the site loaded successfully when tested on a Cellular Mobile Hotspot.
    5. The exact Error Message or HTTP Status Code (e.g., HTTP 403 Forbidden, ERR_CONNECTION_TIMED_OUT) displayed in your browser.

Comments

0 comments

Please sign in to leave a comment.