http returns 500 Internal Server Error but not https
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
1. The fact that you can't access it by HTTP (port 80) and you can by HTTPS (port 443) might be completely irrelevant.
2. "500: server error" is *extremely* generic - the underlying problem could be just about *anything*.
3. SUGGESTED STEPS:
a) Identify exactly what "application" is on the link you failed to reach.
Simple HTML files? PHP or ASPX scripts? A Tomcat servlet container? A JBoss application server? Something else entirely? A combination of some or all of the above?
b) Try to see if that "application" has any logs.
c) See if the "container" (for example, Tomcat and/or JBoss) has any logs.
d) Look at your web servers logs (e.g. /var/log/apache)
e) Look at your server logs (e.g. /var/log/messages)
[Tue Jun 22 14:37:57 2010] [error] [client xxx.xxx.xxx.xx] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
and from /var/log/messages
Jun 22 10:45:33 servername ntpd: synchronized to 220.127.116.11, stratum 1
Not sure what this means.
BTW. I am using apache on a redhat linux. No tomcat...
The "app" is drupal, and you haven't configured it correctly, or you have changed something. Check all the config files that deal with standard non-https pages and content. It's not an apache server error, it's an error that apache can do nothing about. You get the same thing with misconfigured perl or php scripts.