cpanel internal server error ssl
Hostgator Php Error Log4, 2010 Messages: 7 Likes Received: 0 Trophy Points: 1 Hi Folks, Hopefully someone can help me with this one. I have an ssl cert installed and it works find in WHM, I also have a joomla site and WHMCS installed when i use https on those I get a 500 internal server error. output of log is: Code: SoftException in Application.cpp:422: Mismatch between target UID (99) and UID (503) of file "/home/adminroo/public_html/clients/cart.php", referer: http://lmas-networks.com/ and Code: SoftException in Application.cpp:422: Mismatch between target UID (99) and UID (503) of file "/home/adminroo/public_html/index.php" UID 99 is nobody I think? If i stat a directory that contains files that give the 500 error I get: Code: File: `public_html' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 37h/55d Inode: 53739932 Links: 17 Access: (0755/drwxr-xr-x) Uid: ( 503/adminroo) Gid: ( 99/ nobody) Access: 2010-08-08 04:10:10.000000000 +0100 Modify: 2010-08-06 17:44:33.000000000 +0100 Change: 2010-08-08 02:05:59.000000000 +0100 and a file: Code: File: `index.php' Size: 2049 Blocks: 8 IO Block: 4096 regular file Device: 37h/55d Inode: 54595371 Links: 1 Access: (0644/-rw-r--r--) Ui
annoying, finaly got it solved with the help of a very helpfull member of the cpanel forum by the name of Miraenda. Scenario: You get a 500 server error after installing an ssl cert and using https and
What Causes 500 Internal Server Error Phpyour error logs in apache contain somthing along the lines of: SoftException in Application.cpp:422: Mismatch hostgator 500 internal server error between target UID (99) and UID (503) of file “/home/someuser/public_html/anything.php”, This is because the /var/cpanel/userdata/someuser/domain-name.com_SSL does not contain the correct user info softexception in application.cpp:256: file is writeable by group i.e. is installed as the wrong user (usualy nobody “UID (99) is nobody”) FIX: To fix this you first need to find your domain-name.com_SSL file in /var/cpanel/userdata/ look in this directory you will have a bunch of https://forums.cpanel.net/threads/ssl-cert-500-internal-server-error.162653/ users in here one of which is likley to be “nobody” and is a good place to start. Once you find the file move it to the correct user location. e.g. if you are not sure which user it should be installed as go to the directory that is causing the issue and run “stat /home/someuser/publichtml/somefile.php” this will give you enough info to find out who it should be installed as. Now you have the https://vijaynayani.wordpress.com/2010/10/09/ssl-cpanel-500-internal-server-error/ file in the right place you need to make a few changes to the domain-name_SSL file to make it work correctly. You should see the following lines: documentroot: /home/user/public_html group: user homedir: /home/user user: user Replace user with the username for each one. note, these are not the only lines in the file, they are just the lines you need to change in that file. If the account is a reseller and not owned by root, you will also need to change owner: root to owner: user. Please also check the ip: field has the right IP listed. After making all the changes, then run these commands to rebuild Apache with the new entries and get it restarted: /scripts/rebuildhttpdconf /etc/init.d/httpd restart Now test it again hope this help someone. 12.971606 77.594376 Like this:Like Loading... Related This entry was posted on October 9, 2010, 5:25 AM and is filed under Linux. You can follow any responses to this entry through RSS 2.0. You can leave a response, or trackback from your own site. Comments (1) Trackbacks (3) #1 by Greg on August 26, 2011 - 7:20 PM Thank you! Rarely do I find a post that just seems to fix my problem outright! Reply paico | Usando SSL no seu VPS + Erro 500 ao usar SSL ralph lauren shirts Moshi Monsters Leave a Reply Cancel reply Enter your
be caused by many things, including but not limited to invalid permissions, invalid ownership, bad lines in your php.ini or .htaccess file, invalid requests in the script, and others not mentioned here. Typically this is not a problem with the server itself, and can be most often resolved by modifying something in your site's configuration. Please check the Error Logs in cPanel for specific information. Example of Server 500 Error Bad permissions, Writable by group Bad .htaccess, Invalid code, command, or syntax Improperly configured php.ini Example of Server 500 Error A Server 500 error will generally look something like this:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, firstname.lastname@example.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.Bad permissions, Writable by group A bad permissions error may look something like this: [Sun Jun 05 12:03:22 2012] [error] [client 220.127.116.11] SoftException in Application.cpp:601: Directory "/home/exampleuser/public_html" is writeable by group In this instance the folder had permissions for a folder set too high. To correct this, the permissions need to be changed from "777" to "755". Directories and folders should be 755. Executable scripts within the cgi-bin folder must be 755. Images, media, and text files like HTML should be 644. Files - 644 CGI Scripts - 755 Directories - 755 You can modify permissions with the File Manager, located in the "Files" category of the cPanel, an FTP client, or using the chmod command in SSH/Bash. Bad .htaccess, Invalid code, command, or syntax In the .htaccess file ("dot htaccess"), you may have added lines that are either worded badly or conflicting. The best way to troubleshoot this is comment out the lines in the .htaccess. You can comment out a line in the .htaccess by adding # to the beginning. You are wise to save an original copy of any file before you make changes. For