Total Disaster - Image errors, PHP config problem, and now, internal server error...
Permalink
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@gusposey.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 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
This is what I get now when I try to load my site. I wanted to install Concrete5 to rebuild my site, but it never quite worked. At first, it was just a problem of the images not displaying. I tried everything listed in the forums. Then, I tried reinstalling Concrete5. Now, I can't install anything, can't access the site, and my provider is telling me that they can't help me with the internal 500 error. Can anyone help me with this?
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@gusposey.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 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
This is what I get now when I try to load my site. I wanted to install Concrete5 to rebuild my site, but it never quite worked. At first, it was just a problem of the images not displaying. I tried everything listed in the forums. Then, I tried reinstalling Concrete5. Now, I can't install anything, can't access the site, and my provider is telling me that they can't help me with the internal 500 error. Can anyone help me with this?
The Galleria image gallery works as expected on your site, just not in Chrome (after testing in Chrome 22, IE9 and FF 15), but the same problem occurs on the developers own site.
Seems like you have this solved.