lucasjacob Posted April 4, 2013 Posted April 4, 2013 User: Lucas97Server: JohnnyDomain: undeadsoulspk.heliohost.org The account was created 24 hours ago. Thanks in advance.
lucasjacob Posted April 4, 2013 Author Posted April 4, 2013 User: Lucas97Server: JohnnyDomain: undeadsoulspk.heliohost.org The account was created 24 hours ago. Thanks in advance.
lucasjacob Posted April 5, 2013 Author Posted April 5, 2013 I created my account 2 days ago and still queued... Link : undeadsoulspk.heliohost.orgServer:johnnyUser:Lucas97 Someone can help me? Thank u so much
Krydos Posted April 5, 2013 Posted April 5, 2013 Your site is showing a 500 error for me not queued. If you're still seeing a queued page you should try clearing your cache. As far as the 500 error goes this might help:500 errors can be caused by a lot of things. The most common areExceeding Process Limit The solution is to not run as many processes. Opening cpanel, connecting to FTP, checking mail, connecting to webdisk, etc all increase your process count, and if you exceed your limit php will show 500 errors since it cannot start a new php process. This sometimes affects only the webmaster since opening cPanel and FTP etc is common when you're editing your site, but normal users won't have these errors since they will only be accessing your website not all the other services. The process limit is higher on Johnny so for some websites the solution to 500 errors might be to switch servers.Syntax Error in .htaccess If you have a syntax error in one of your .htaccess files it can cause a 500 error. The easiest way to check if this is the case is to delete or rename your .htaccess files and see if the 500 error goes away.Incorrect Permissions If the script or the directory that the script is in doesn't have the correct permissions it can cause 500 errors too. If you're running a php script the file permission should be 644. If you're running a cgi script it should have 755 permissions. Your directories should have 755 or 750 permissions.Exceeding Time Limit If your script exceeds the time limit it can be killed by the system which will also result in a 500 error. The solution to this problem is to break your long executing scripts into multiple faster scripts that can call each other. For instance longscript.php always results in a 500 error because it exceeds the time limit, but if script1.php runs for a short time, and then calls script2.php which calls script3.php they can together execute the same code as longscript.php without exceeding the time limit and being killed.High Server Load If the server is currently experiencing high server load scripts can return a 500 error when they would normally work. This is more common on Johnny than Stevie since Johnny is more unstable, and accounts that cause high load on Stevie are suspended. There isn't really anything that can be done about high load 500 errors other than trying again later when the load is lower.
Recommended Posts