While using VergeCloud services, users may encounter specific error codes unique to the platform. These codes signify issues or violations of rules configured on VergeCloud. This guide explains common VergeCloud error codes, their causes, and solutions.
Error code 403 occurs when a request violates the firewall rules configured in the VergeCloud User Panel. This error commonly arises when access restrictions are based on geolocation or other parameters.
For instance, if you configure your website to allow access only from a specific country, such as Iran, requests from other locations will be blocked and display error 403. However, even users from the allowed country might encounter this error if:
Until the geo IP data is updated, legitimate users may experience access issues despite being located in an allowed region.
Error code 429 appears when users exceed the limits set by VergeCloud’s rate-limiting feature. This feature restricts the number of requests or connections allowed for specific users within a defined time frame.
Overly restrictive rate limits can unintentionally block legitimate users. For example, if you underestimate the traffic patterns of your users and set strict limits, they may encounter error 429, affecting their ability to access your website.
VergeCloud’s secure link feature enables businesses to share protected resources like videos, educational materials, or sensitive files. Secure links restrict access based on parameters such as IP address, time window, and token, ensuring that only authorized users can access the content.
When a secure link is generated, it includes a server-side hash calculated based on the specified parameters. If an unauthorized user tries to access the resource with incorrect parameters, the request fails because the provided hash does not match the expected server-side hash.
Users may encounter the following errors when accessing secure links:
VergeCloud allows you to replace default error pages with custom ones for a personalized user experience. Follow these steps to set up custom error pages: