CDN Connectivity & Accessibility
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 ...
Resolving iOS Inaccessibility Issues with VergeCloud CDN
Ignore "upgrade" Header If your website becomes inaccessible to iOS users (e.g., on iPhones or iPads) after integrating VergeCloud CDN, you can resolve the issue by adjusting the Page Rules in your VergeCloud User Panel. Follow the steps below: ...
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 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 ...
Troubleshoot 500 Errors.
Main Server Inaccessibility Error A common issue users of VergeCloud's accelerated and secured websites may encounter is the "Main Server Inaccessible" error. This error indicates that the primary server is temporarily unavailable. VergeCloud ...
NS Records Updated but Traffic Not Routing Through VergeCloud
Common Issues After Changing Nameservers to VergeCloud First Reason: Delay in Change Implementation You may have updated your NS records, but the changes have not yet taken effect. .com Domains For domains ending in .com, changes are typically ...