A 403 Forbidden error typically occurs when file system permissions prevent the web server from accessing the page or running a script. Please see Setting File Permissions for more information on changing file permissions.
A 502 Bad Gateway error occurs when the front-end web server cannot communicate with the application responsible for responding to the request. To resolve this error: Confirm that the application is running. If the application crashed, was terminated, or has not yet started following a system reboot, the application must be restarted to respond to requests. If the application was terminated, you will receive a notification email with additional information. To restart the application manually, please see your application type’s documentation or control panel entry for instructions. Most stopped applications are automatically restarted during periodic cron jobs. Please see the application’s entry in the control panel for details. Confirm that the application is listening to the correct port. Check your application’s configuration to make sure that it is listening to the port assigned to the application in the control panel.
A 504 Gateway Timeout error occurs when an application takes too long to respond to an incoming request. This error is often caused by an application receiving heavy traffic. This error can also be caused by an application running to slowly; optimizations may be required to avoid the error. For more information, please see the documentation for your application type.