500 Internal Server Error

Status
Not open for further replies.

-GH0ST-

New Member
Messages
24
Reaction score
1
Points
0
After the downtime my account was finalized and everything appeared to be just dandy. Joomla installed 5 by 5 and everything seemed to be fine. Unfortunately, when I try to install any template, I get the following:

Code:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, no-reply@x10hosting.com 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 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

I haven't bothered with attempting to install anything due to the fact that if I get this through the installer at any point, I'll get it with anything. Knowing that I started searching the forums and found that it's possibly the .htaccess file. So, here's the contents of that badboy which I nabbed using my ftp client:

Code:
##
# @version $Id: htaccess.txt 21064 2011-04-03 22:12:19Z dextercowley $
# @package Joomla
# @copyright Copyright (C) 2005 - 2010 Open Source Matters. All rights reserved.
# @license http://www.gnu.org/copyleft/gpl.html GNU/GPL
# Joomla! is Free Software
##


#####################################################
#  READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE
#
# The line just below this section: 'Options +FollowSymLinks' may cause problems
# with some server configurations.  It is required for use of mod_rewrite, but may already
# be set by your server administrator in a way that dissallows changing it in
# your .htaccess file.  If using it causes your server to error out, comment it out (add # to
# beginning of line), reload your site in your browser and test your sef url's.  If they work,
# it has been set by your server administrator and you do not need it set here.
#
#####################################################

##  Can be commented out if causes errors, see notes above.
Options +FollowSymLinks

#
#  mod_rewrite in use

RewriteEngine On

########## Begin - Rewrite rules to block out some common exploits
## If you experience problems on your site block out the operations listed below
## This attempts to block the most common type of exploit `attempts` to Joomla!
#
## Deny access to extension xml files (uncomment out to activate)
#<Files ~ "\.xml$">
#Order allow,deny
#Deny from all
#Satisfy all
#</Files>
## End of deny access to extension xml files
# Block out any script trying to set a mosConfig value through the URL
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|\%3D) [OR]
# Block out any script trying to base64_encode data within the URL
RewriteCond %{QUERY_STRING} base64_encode[^(]*\([^)]*\) [OR]
# Block out any script that includes a <script> tag in URL
RewriteCond %{QUERY_STRING} (<|%3C)([^s]*s)+cript.*(>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
# Return 403 Forbidden header and show the content of the root homepage
RewriteRule .* index.php [F]
#
########## End - Rewrite rules to block out some common exploits


########## Begin - Custom redirects
#
# If you need to redirect some pages, or set a canonical non-www to
# www redirect (or vice versa), place that code here. Ensure those
# redirects use the correct RewriteRule syntax and the [R=301,L] flags.
#
########## End - Custom redirects


#  Uncomment following line if your webserver's URL
#  is not directly related to physical file paths.
#  Update Your Joomla! Directory (just / for root)

# RewriteBase /


########## Begin - Joomla! core SEF Section
#
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
#
# If the requested path and file is not /index.php and the request
# has not already been internally rewritten to the index.php script
RewriteCond %{REQUEST_URI} !^/index\.php
# and the request is for root, or for an extensionless URL, or the
# requested URL ends with one of the listed extensions
RewriteCond %{REQUEST_URI} (/[^.]*|\.(php|html?|feed|pdf|raw))$ [NC]
# and the requested path and file doesn't directly match a physical file
RewriteCond %{REQUEST_FILENAME} !-f
# and the requested path and file doesn't directly match a physical folder
RewriteCond %{REQUEST_FILENAME} !-d
# internally rewrite the request to the index.php script
RewriteRule .* index.php [L]
#
########## End - Joomla! core SEF Section

Worst case scenario, I'll just scrag my install and start over. I'm assuming there's still some kinks that need to be worked out on Stoli? That's cool, just looking for some confirmation or at the best a fix.

Oh yea, in an effort to troubleshoot (which really wasn't much of an effort let me tell you ha), I changed perms on .htaccess to 777, just to ensure it wasn't a read/write issue. That did nothing, so I left it as is and posted this.
 

stpvoice

Community Support Rep
Community Support
Messages
5,987
Reaction score
212
Points
63
Hello,

Htaccess should be CHMOD 644.
Code:
##
# @version $Id: htaccess.txt 21064 2011-04-03 22:12:19Z dextercowley $
# @package Joomla
# @copyright Copyright (C) 2005 - 2010 Open Source Matters. All rights reserved.
# @license http://www.gnu.org/copyleft/gpl.html GNU/GPL
# Joomla! is Free Software
##


#####################################################
#  READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE
#
# The line just below this section: 'Options +FollowSymLinks' may cause problems
# with some server configurations.  It is required for use of mod_rewrite, but may already
# be set by your server administrator in a way that dissallows changing it in
# your .htaccess file.  If using it causes your server to error out, comment it out (add # to
# beginning of line), reload your site in your browser and test your sef url's.  If they work,
# it has been set by your server administrator and you do not need it set here.
#
#####################################################

##  Can be commented out if causes errors, see notes above.
Options +FollowSymLinks

#
#  mod_rewrite in use

RewriteEngine On
RewriteBase /

########## Begin - Rewrite rules to block out some common exploits
## If you experience problems on your site block out the operations listed below
## This attempts to block the most common type of exploit `attempts` to Joomla!
#
## Deny access to extension xml files (uncomment out to activate)
#<Files ~ "\.xml$">
#Order allow,deny
#Deny from all
#Satisfy all
#</Files>
## End of deny access to extension xml files
# Block out any script trying to set a mosConfig value through the URL
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|\%3D) [OR]
# Block out any script trying to base64_encode data within the URL
RewriteCond %{QUERY_STRING} base64_encode[^(]*\([^)]*\) [OR]
# Block out any script that includes a <script> tag in URL
RewriteCond %{QUERY_STRING} (<|%3C)([^s]*s)+cript.*(>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|\[|\%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|\[|\%[0-9A-Z]{0,2})
# Return 403 Forbidden header and show the content of the root homepage
RewriteRule .* index.php [F]
#
########## End - Rewrite rules to block out some common exploits


########## Begin - Custom redirects
#
# If you need to redirect some pages, or set a canonical non-www to
# www redirect (or vice versa), place that code here. Ensure those
# redirects use the correct RewriteRule syntax and the [R=301,L] flags.
#
########## End - Custom redirects


#  Uncomment following line if your webserver's URL
#  is not directly related to physical file paths.
#  Update Your Joomla! Directory (just / for root)


########## Begin - Joomla! core SEF Section
#
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
#
# If the requested path and file is not /index.php and the request
# has not already been internally rewritten to the index.php script
RewriteCond %{REQUEST_URI} !^/index\.php
# and the request is for root, or for an extensionless URL, or the
# requested URL ends with one of the listed extensions
RewriteCond %{REQUEST_URI} (/[^.]*|\.(php|html?|feed|pdf|raw))$ [NC]
# and the requested path and file doesn't directly match a physical file
RewriteCond %{REQUEST_FILENAME} !-f
# and the requested path and file doesn't directly match a physical folder
RewriteCond %{REQUEST_FILENAME} !-d
# internally rewrite the request to the index.php script
RewriteRule .* index.php [L]
#
########## End - Joomla! core SEF Section

I also made a small edit to the .htaccess file. Please try that.
Also, nothing should be CHMOD 777. Directories should generally be 755, and files 644.
 
Last edited:

-GH0ST-

New Member
Messages
24
Reaction score
1
Points
0
Update

- Made changes to the .htaccess (copypasta), saved, uploaded to root and chmod to 644
- Tested and we're now good to go there (I don't get 500 errors on every page anymore - just when I try to install now)

Every time I try to upload something via the Jinstaller, I get the 500 Internal Server Error. So since I've got nothing to lose, I'm going to scrag the install via the cPanel, cleanup with ftp client and reinstall using cPanel. I'll let you know if anything happens after that either way so we can close this.
 

stpvoice

Community Support Rep
Community Support
Messages
5,987
Reaction score
212
Points
63
Okay. Remember not to delete the public_html or www folders, or anything above unless you put it there.
 

-GH0ST-

New Member
Messages
24
Reaction score
1
Points
0
No prob on that. The excess files are deleting now.

Update

Everything was removed as it should, nothing was removed that shouldn't have been. Reinstalled via the cPanel (Fantastico), test installed and fail.

I'm removing everything again but I checked the configuration.php file on a hunch and I found that Fantastico didn't write to it, so it was blank. That would certainly throw an error like that. So now I'm going to manually upload everything, then install and create the sql database manually bypassing cPanel and seeing if it's really Fantastico or something totally different.
 
Last edited:

Skizzerz

Contributors
Staff member
Contributors
Messages
2,928
Reaction score
118
Points
63
Note the particular line that was causing issues that stpvoice fixed was adding RewriteBase / before all of the rewriterules. If you are using mod_rewrite for stuff, make sure you set RewriteBase or this will probably cause 500 Internal Server Errors.
 

-GH0ST-

New Member
Messages
24
Reaction score
1
Points
0
Note the particular line that was causing issues that stpvoice fixed was adding RewriteBase / before all of the rewriterules. If you are using mod_rewrite for stuff, make sure you set RewriteBase or this will probably cause 500 Internal Server Errors.

I'm still not convinced that my account was created without a glitch due to the timing of my signup and the outage.

Update

Okay, after scragging everything and starting over by uploading the .zip, decompressing and installing manually including creating the database by hand, I'm still getting the same 500 Internal Sever Error when I try to upload and install using the Jinstaller over say 500ish kb sized zip files. Anything under that seems to go up no problem while everything above blows up. I've tried using the ftp upload layer involved in the Joomla backend but instead of generating a 500 error, I get another but I know what's up with that and it's not related to this particular issue.

When I do get the 500 error, I've noticed that some of the files are uploaded and installed, but not correctly nor are there any updates to the tables in the database. I'm wondering if there's an upload cap on the sever, but if there is, why would I be able to upload some files that are far larger than that whereas I can't in Joomla? It doesn't make much sense, but the only other thing I can think of is a server timeout maybe?

I don't really know, I'm an IT guy, not a server host heh.

So my method of thinking goes back to wondering if my account wasn't setup correctly due to the outage. Might someone be able to check on that? If not, is there a way to totally reset everything? I know this should work here, so I'm out of ideas at this point.

Also

When I try to access my error logs, I get a blank page aside from this text even though the server has been throwing errors left and right -

Code:
Error Log
This function will display the last 300 errors for your site. This can be very useful for finding broken links or problems with missing files. Checking this log frequently can help keep your site running smoothly.

Last 300 Error Log messages in reverse order:


---------- Post added at 10:25 PM ---------- Previous post was at 07:40 PM ----------

bump for great justice
 
Last edited:

Skizzerz

Contributors
Staff member
Contributors
Messages
2,928
Reaction score
118
Points
63
It's unlikely that it's a server glitch, but should you want to reset your account, please fill out the following form. The only way for us to reset accounts is to delete them and have you recreate it. Required information is boldface and red for your convenience.

cPanel username:

( ) Inserting an X inside the parentheses signifies that I have made all necessary backups of my free hosting account and will not hold x10Hosting responsible for any data I am unable to recover after my free hosting account is deleted. The X also serves as my digital signature verifying that I have proper authorization to request account deletion of the account specified.

Other common causes for 500 Internal Server Errors:
1) Scripts that take more than 30 or 60 seconds to execute (can't remember)
2) Permissions. Files must be 644 and directories must be 755
3) RewriteBase missing
4) Trying to use php_flag/php_value in .htaccess
5) CGI Perl/Python scripts (CGI is not supported on Free Hosting)

EDIT: Also, please note that error logs and access logs do not function correctly on Free Hosting due to how we have the servers configured.
 
Last edited:

-GH0ST-

New Member
Messages
24
Reaction score
1
Points
0
Okay then. Will I be able to retain this forum account? Or, will I be able to reestablish a link with my new host account with the forum account? How long will this take? I've read it takes 14 days to typically delete a hosting account, would that time frame apply to my situation?

If the answer is no to any of the above (other than the time frame question), I'll keep working on it since you feel it's not related to the account. Otherwise, let's do this.

In the mean time, here's the requested info -

cPanel username: ghostnet

(X) Inserting an X inside the parentheses signifies that I have made all necessary backups of my free hosting account and will not hold x10Hosting responsible for any data I am unable to recover after my free hosting account is deleted. The X also serves as my digital signature verifying that I have proper authorization to request account deletion of the account specified.
 
Last edited:

Skizzerz

Contributors
Staff member
Contributors
Messages
2,928
Reaction score
118
Points
63
You'll retain your forum account, and can sign up for a new hosting account by first logging into http://x10hosting.com/control and following the links there to sign up. This will link your new hosting account with the current forum account. It should take no more than an hour (often less) to make a new account and get it in the system.

The 14 days is a time frame to give people a chance to change their minds. Since you're recreating right away, we can fire off the deletion immediately, which since the answers to all your questions (minus the time frame one) are "yes", I'm going to do right now.

EDIT: and it's gone
 
Last edited:

-GH0ST-

New Member
Messages
24
Reaction score
1
Points
0
Thanks man and thanks to everyone else who took part in this evolution.

out
 
Status
Not open for further replies.
Top