: Nginx 502 Bad gateway on shared hosting I have a website on a shared hosting provider. Since the very beginning my visitors have randomly got several types of errors, including 502 Bad Gateway

@Annie201

Based on the error message alone, I would suggest to ensure all files in your app are within the folder you're allowed to place data in. then if possible, use absolute paths when referencing files.

For example, Assume your site layout is as follows:

In your document root folder you have
Folder named Scripts, and a script named index.php

In the Scripts folder you have
File named 123.php that represents the script you want to load


In this setup, if someone accesses just your domain name, then its likely index.php will load its contents. That file can contain the following contents:

<?php
include "Scripts/123.php";
// rest of startup code goes here
?>


If you can, get the full path info to your document root (I assume here that path is /path/to/document/root), then make your index php file like this:

<?php
include "/path/to/document/root/Scripts/123.php";
// rest of startup code goes here
?>


That way you know you're at least pointing to the correct file. Just going into ssh to your document root and typing pwd and hitting enter should give you the absolute path to your document root.

If you just specify only a file name with no folder information, then php will scan all the predefined include folders (from the php configuration file) (aka "allowed paths") for your script, and some of these folders are likely outside of your user space.

Its possible that the bad gateway can be returned if the file you're requesting begins with an unusual or undefined protocol (like xx://).

My recommendation is to use files and absolute pathnames when referencing other files from within scripts.

Vote Up Vote Down