Troubleshooting ISP Accessibility Issues with VergeCloud CDN.

Troubleshooting ISP Accessibility Issues with VergeCloud CDN.

Resolving ISP Access Issues with VergeCloud

If your website is inaccessible to users from specific Internet Service Providers (ISPs) while using VergeCloud's CDN, this guide provides solutions to common causes, such as firewall and rate-limiting configurations.

Introduction

Users may face access issues due to improper configurations on the hosting server, such as firewall rules blocking VergeCloud’s IPs or restrictive rate-limiting settings. Addressing these problems ensures seamless access to your website across all ISPs.

Steps to Resolve ISP Access Issues

Add VergeCloud’s IPs to the iptables Whitelist

To allow VergeCloud’s IP addresses through the server firewall using iptables, follow these steps:

  1. Access Your Server:

    Log in to your web hosting server using SSH. For example:

    ssh user@yourserver.com
  2. Identify VergeCloud’s IP Addresses:

    Obtain the list of VergeCloud IPs by visiting https://vergecloud.com/ips.txt.

  3. Add the IPs to the Whitelist:

    Run the following command to allow a specific IP address:

    sudo iptables -A INPUT -s [VergeCloud_IP] -j ACCEPT

    Replace [VergeCloud_IP] with the actual IP address (e.g., 192.0.2.1).

  4. Save the iptables Rules:

    Save the configuration to ensure the changes persist after a server reboot:

    sudo iptables-save > /etc/iptables/rules.v4
  5. Verify the Changes:

    List all rules to confirm that the IP has been added successfully:

    sudo iptables -L

Add VergeCloud’s IPs to the htaccess Whitelist

To whitelist VergeCloud’s IP addresses using an .htaccess file, follow these steps:

  1. Access Your Server:

    Log in to your web hosting server using an FTP client, cPanel, or SSH.

  2. Locate the .htaccess File:

    Navigate to the root directory of your website where the .htaccess file is located (usually the public_html folder).

  3. Edit the .htaccess File:

    Open the .htaccess file in a text editor. If the file doesn’t exist, create one in the root directory.

  4. Add Whitelist Rules:

    Insert the following code to whitelist VergeCloud’s IP addresses:

    
    # Whitelist VergeCloud IPs
    
        order deny,allow
        deny from all
        allow from [VergeCloud_IP_1]
        allow from [VergeCloud_IP_2]
        ...
    
            

    Replace [VergeCloud_IP_1], [VergeCloud_IP_2], etc., with the actual IP addresses from https://vergecloud.com/ips.txt.

  5. Save and Upload:

    Save the file and upload it back to the server if you’re using an FTP client or cPanel.

  6. Test the Changes:

    Visit your website and check its accessibility to ensure the whitelist rules are working as expected.

Add VergeCloud’s IPs to Nginx

To whitelist VergeCloud’s IP addresses in your Nginx configuration, follow these steps:

  1. Access Your Server:

    Log in to your server using SSH.

  2. Open the Nginx Configuration File:

    Locate your Nginx configuration file, usually found at /etc/nginx/nginx.conf or in a site-specific file under /etc/nginx/sites-available/.

  3. Edit the Configuration File:

    Add the following code inside the server block:

    
    allow [VergeCloud_IP_1];
    allow [VergeCloud_IP_2];
    deny all;
            

    Replace [VergeCloud_IP_1] and [VergeCloud_IP_2] with the actual IPs from https://vergecloud.com/ips.txt.

  4. Save the Changes:

    Save the configuration file and exit the editor.

  5. Test the Configuration:

    Run the following command to ensure your Nginx configuration is valid:

    sudo nginx -t
  6. Restart Nginx:

    Apply the changes by restarting Nginx:

    sudo systemctl restart nginx

Add VergeCloud’s IPs to IIS

To whitelist VergeCloud’s IP addresses in Microsoft IIS, follow these steps:

  1. Access IIS Manager:

    Log in to your Windows Server and open IIS Manager.

  2. Select Your Website:

    In the left-hand Connections pane, expand the Sites node and select your website.

  3. Open IP Address and Domain Restrictions:

    Double-click on IP Address and Domain Restrictions in the IIS Manager Features View.

  4. Add Allow Entries:

    Click Add Allow Entry in the right-hand Actions pane. Enter each VergeCloud IP address from https://vergecloud.com/ips.txt and click OK.

  5. Configure Default Deny:

    Set the default behavior to deny all traffic except those explicitly allowed:

    • Click Edit Feature Settings in the Actions pane.
    • Set Default Action to Deny and click OK.
  6. Restart IIS:

    Restart IIS to apply the changes:

    iisreset

Check Rate Limiting Settings

Rate-limiting configurations on your hosting server may restrict the number of requests allowed per user, potentially blocking legitimate traffic. Follow these steps to resolve rate-limiting issues:

  1. Access Rate Limiting Settings:

    Log in to your hosting server control panel and locate the rate-limiting settings.

  2. Review Current Settings:

    Ensure the request quota is set to a reasonable value to prevent legitimate users from being blocked.

  3. Adjust Rate Limits:

    Increase the request quota or whitelist VergeCloud’s IP addresses to ensure uninterrupted traffic flow.

  4. Test Changes:

    Verify that users can access the website without encountering rate-limiting issues.

Considerations

  • Always verify VergeCloud’s IP addresses periodically at https://vergecloud.com/ips.txt, as they may change over time.
  • Ensure that firewall and rate-limiting configurations align with the traffic needs of your website.
  • Test your website after applying changes to confirm that users from all ISPs can access it without issues.

    • Related Articles

    • Troubleshooting With Active CDN and Enabled Cloud Icon.

      Testing Main Server Connection With Active CDN When VergeCloud's CDN is enabled, the cloud icon in your user panel indicates that your website's main server address is masked behind VergeCloud's servers. Tools like ping and traceroute will return ...
    • Troubleshooting SSL Errors on VergeCloud CDN.

      Troubleshooting SSL Errors on VergeCloud If users encounter SSL errors while visiting your website and you are utilizing VergeCloud’s content delivery network (CDN), the issue may stem from several potential causes. This guide outlines common factors ...
    • Troubleshooting with cURL.

      cURL: An Essential Tool for Diagnostics What is cURL? cURL, short for Client for URLs, is a command-line tool used for transferring data over various protocols. It supports a broad array of devices and can be employed to test several scenarios, such ...
    • Troubleshooting Traffic Routing Through VergeCloud CDN

      After updating your NS records to utilize VergeCloud CDN, you might notice that the traffic isn’t yet routed through VergeCloud. This issue can arise due to two main reasons: Reason 1: Delay in Propagation of Changes Although you have updated your NS ...
    • Troubleshooting DNS_PROBE_FINISHED_NXDOMAIN Error on VergeCloud

      Understanding DNS_PROBE_FINISHED_NXDOMAIN Error The DNS_PROBE_FINISHED_NXDOMAIN error occurs when a DNS lookup is performed for a domain name, but no corresponding IP address is found. NXDOMAIN stands for "Non-Existent Domain," indicating that the ...