Thread

Suddenly I have begun recieving a 500 Internal Error. 

the site is at http://youngcubrecords.com/index.php

I updated a template, then returned to the site and now it is not working?

EE backend still works though.  Any ideas? How do I even revert back to it working with the index.php?

The site is on Godaddy, and I had been using an htaccess file to remove the index.php with no problems whatsoever until now.  Here is a copy of the htacess file:

# -FrontPage-

IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*

<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName <a href="http://www.youngcubrecords.com">http://www.youngcubrecords.com</a>
AuthUserFile /var/chroot/home/content/y/o/u/youngcub/html/_vti_pvt/service.pwd
AuthGroupFile /var/chroot/home/content/y/o/u/youngcub/html/_vti_pvt/service.grp
DirectoryIndex temp.html  

# rewrite rules
RewriteEngine On
RewriteCond %{QUERY_STRING} ^(css=.*)$ [NC]
RewriteRule ^(.*)$ /index.php?/%1 [L]
RewriteCond $1 !^(images|yoursystem|themes|favicon/.ico|robots\.txt|index.php) [NC]
# ditch index.php
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /index.php?/$1 [L]

To disable your htaccess, either rename it or delete it after making a backup.

To troubleshoot start with a blank htaccess and add it back in line by line until you find the culprit causing the 500 error.

Typically I would move this thread to the How to forum as we do not support the removal of index.php. But lets confirm it is your htaccess to begin with. A 500 error is a server side error by nature.

Thanks for the quick reply.  I really appreciate it.

I tried deleting the htaccess altogether, but to no avail.  I am having no problem logging into expression engine however.

lag47,

Can you add back in index.php as the value for Name of your site’s index page here
CP Home ›  Admin ›  System Preferences ›  General Configuration

thanks again.

SO the htaccess has been deleted.

Changed up the configurations.

Still no dice. 

Here is an image of the my setttings

Here is a better pic

lag47,

In your image you are still missing the Name of your site’s index page . The very first row in your image.

See the first and second values?

Name of your site’s index page should be index.php
URL to the root directory of your site should be: http://youngcubrecords.com

Still broken

You might want to talk to your host about it. 500 errors are always the server’s fault: it’s either running out of resources, mis-configured, or been instructed to throw that particular error. That said, your host should have access to the servers’ error logs, which will give us an idea what the issue is.

My server suggested I monitor the the error_logs. 

The error is:
Premature end of script headers: /var/chroot/home/content/y/o/u/youngcub/html/index.php

So the htaccess is gone.  The configuration looks like it does above.  A link like this, however, runs http://youngcubrecords.com/?css=site/site_css.v.1257251309

Hi lag47-

If my memory serves me correct, a number of Godaddy customers need to “Force Query Strings.”

You can find this setting by navigating to: Admin > System Preferences > Output and Debugging Preferences.

You may also need to open the main site index.php (not your Control Panel file) and find the $qtype variable at the top of the file.  Try changing the value of that variable; most likely “2” will work for you.

Didn’t work.  What next?

I turned on debugging though, and the new error is:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 922430 bytes) in /home/content/y/o/u/youngcub/html/ycr/core/core.template.php on line 712

its trying to allocate less than a megabyte? 

The wierd thing is that it was working fine.  I added a template and then it stopped working.  I don’t want to, but it is starting to sound like I need to reinstall everything.

You actually have 64 MB allocated to PHP, which should by sufficient for most purposes. That said, yes, EE is running out of memory. Try to reduce / optimize your templates, or increase that amount (if only temporarily) if that’s an option.