I did not create this blog, but I'm trying to fix it for my client. I'm now getting a 500 internal server error
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, jayne@thebaysedge.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.
Everything was working fine and now this error. I have made any changes to the blog other than my client posting to it. Any suggestions and please give as much detail as you can as I am not familiar with serendipity for blogs.
Thanks
500 error
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Re: 500 error
Hi!
Check the Apache/CGI/PHP error_log. A 500 intenral server error can mean many things. The real error message can be found inside the error log.
Usually, something is wrong with the .htaccess file
Regards,
Garvin
Check the Apache/CGI/PHP error_log. A 500 intenral server error can mean many things. The real error message can be found inside the error log.
Usually, something is wrong with the .htaccess file
Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
I think this is what you are talking about.
# BEGIN s9y
ErrorDocument 404 {PREFIX}{indexFile}
DirectoryIndex {PREFIX}{indexFile}
<Files *.tpl>
deny from all
</Files>
<Files *.sql>
deny from all
</Files>
<Files *.inc.php>
deny from all
</Files>
<Files *.db>
deny from all
</Files>
# END s9y
If it is, what does this tell you? Do I need to do something to the .htaccess?
Thanks for your quick reply.
# BEGIN s9y
ErrorDocument 404 {PREFIX}{indexFile}
DirectoryIndex {PREFIX}{indexFile}
<Files *.tpl>
deny from all
</Files>
<Files *.sql>
deny from all
</Files>
<Files *.inc.php>
deny from all
</Files>
<Files *.db>
deny from all
</Files>
# END s9y
If it is, what does this tell you? Do I need to do something to the .htaccess?
Thanks for your quick reply.
-
garvinhicking
- Core Developer
- Posts: 30022
- Joined: Tue Sep 16, 2003 9:45 pm
- Location: Cologne, Germany
- Contact:
Hi!
This is an invalid .htaccess file, how did it come to this?
This file is usually in include/tpl/htaccess_normal.tpl - it should NEVER look like this as a .htaccess file. How did you modify it?
Remove the file, then you should be able to log into s9y and then you can try to save your configuration and the .htaccess should be recreated. If not, turn on/off the "URL Rewriting" option, save, then turn it back to what it was before to trigget .htaccess regeneration.
regards,
Garvin
This is an invalid .htaccess file, how did it come to this?
This file is usually in include/tpl/htaccess_normal.tpl - it should NEVER look like this as a .htaccess file. How did you modify it?
Remove the file, then you should be able to log into s9y and then you can try to save your configuration and the .htaccess should be recreated. If not, turn on/off the "URL Rewriting" option, save, then turn it back to what it was before to trigget .htaccess regeneration.
regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
Ok, I think I'm in over my head. I did not set this up and reallly have no idea what you mean by the last post. I think my client will need to contact the previous developer to fix it. I don't understand why it's not working now when nothing was done other than posting. If they are not available to help is there anyone who could help my client with this? Thanks.
-
Don Chambers
- Regular
- Posts: 3657
- Joined: Mon Feb 13, 2006 2:40 am
- Location: Chicago, IL, USA
- Contact:
Garvin is saying:
1) The .htaccess code you posted is not what should be in the real .htaccess file located in the root folder of where serendipity is installed. It appears to be the same code that serendipity uses to CREATE an htaccess file as the code you are showing contains variables {PREFIX} and {indexFile} that will be populated by serendipity when it actually creates the real file.
2) delete the existing .htaccess file located in your serendipity root folder- or rename it to something else. Do NOT delete the file Garvin mentioned (/include/tpl/htaccess_normal.tpl).
3) Log into serendipity's adminstration/back-end at yourdomain/serendipity_admin.php.
4) Go to Administration -> Configuration. Click the button at the bottom marked "Check & save". That SHOULD re-create a correct .htaccess file.
5) if step 4 does not work, go back to Configuration -> Appearance and Options -> URL rewriting. If currently set to "disable URL rewriting", then enable it (you may have more than one option) and save your configuration, then disable it and save a second time. If already enabled, then disable & save followed by re-enabling and saving a second time.
1) The .htaccess code you posted is not what should be in the real .htaccess file located in the root folder of where serendipity is installed. It appears to be the same code that serendipity uses to CREATE an htaccess file as the code you are showing contains variables {PREFIX} and {indexFile} that will be populated by serendipity when it actually creates the real file.
2) delete the existing .htaccess file located in your serendipity root folder- or rename it to something else. Do NOT delete the file Garvin mentioned (/include/tpl/htaccess_normal.tpl).
3) Log into serendipity's adminstration/back-end at yourdomain/serendipity_admin.php.
4) Go to Administration -> Configuration. Click the button at the bottom marked "Check & save". That SHOULD re-create a correct .htaccess file.
5) if step 4 does not work, go back to Configuration -> Appearance and Options -> URL rewriting. If currently set to "disable URL rewriting", then enable it (you may have more than one option) and save your configuration, then disable it and save a second time. If already enabled, then disable & save followed by re-enabling and saving a second time.
=Don=