Site Not Showing on Move to New Server
Permalink
Just moved a website from development environment to final host environment and took all the necessary steps. However, the website is pretty messed up. URL is http://www.crt-usa.com The site home page will only load (and broken at that, no image rotator showing), and then it just throws Internal Server 500 errors all over the place when you click on anything. When I try to log into the backend as admin, get the following errors:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@crt-usa.com to inform them of the time this error occurred, and the actions you performed just before this 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.
Any advice help would be much appreciated.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@crt-usa.com to inform them of the time this error occurred, and the actions you performed just before this 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.
Any advice help would be much appreciated.
I'd be wondering about .htaccess, or equivalent.
Following is the contents of .htaccess
# -- concrete5 urls start --
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /CRT/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME}/index.html !-f
RewriteCond %{REQUEST_FILENAME}/index.php !-f
RewriteRule . index.php [L]
</IfModule>
# -- concrete5 urls end --
# -- concrete5 urls start --
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /CRT/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME}/index.html !-f
RewriteCond %{REQUEST_FILENAME}/index.php !-f
RewriteRule . index.php [L]
</IfModule>
# -- concrete5 urls end --
Is your site still in the /CRT/ subdirectory? If not remove this line
RewriteBase /CRT/
BINGO!
I commented out that line and no more 500 errors. (Thank you!). Still have some issues on the site, but I can at least get to the backend and hopefully make some progress/clean up.
So - a process question for you. Is it better to leave the rewrite (Pretty URLs) off until after go live and then switch over to them? Concrete5 wrote that code in the .htaccess file when I did this in development. Just curious on best approach on going from development environment to production environment.
Thanks again!
I commented out that line and no more 500 errors. (Thank you!). Still have some issues on the site, but I can at least get to the backend and hopefully make some progress/clean up.
So - a process question for you. Is it better to leave the rewrite (Pretty URLs) off until after go live and then switch over to them? Concrete5 wrote that code in the .htaccess file when I did this in development. Just curious on best approach on going from development environment to production environment.
Thanks again!
Usually the best approach is to turn Pretty URLs and Caching Off, then Clear the Cache before you move a site (also delete everything in /application/files/cache/) then turn them back on once the site is in it's new place.
Good to know. I got some of it right. I did clear the cache, but didn't turn off the pretty URLs or site caching. Will definitely do this next time (have one more going live next week). This was my test case for Concrete5, to see if I was going to stick with it as a go-to CMS system. I think I will. There were some issue, but mainly a learning curve on my part. And I do appreciate the quick response of the community when there is a problem.
Again, thank you for your input - much appreciated!
Again, thank you for your input - much appreciated!
