You don’t need to change code when your blog is moved. Especially if the domain name stays the same. Just like you didn’t have to change code when you initially installed your blog.
One issue may be that the DNS change to point to the new server hasn’t propogated. Or perhaps they didn’t copy all the WP code.
But, what might be more interesting, is for you to give us a bit of a description about what “ruined my blog” really means. What’s working? What’s not working? Got a link?
My site is accessible, the DNS is still the same as they only moved my site to a different internal server with a different IP.
My site is NuMixes.com and if you go there now it will display my temp index.htm. I think the database is out of sync with the site (but I’m a newbie so I can’t say with certainty)
This is the error I get if I remove my index.htm and leave index.php from wordpress :
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@numixes.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.
But I have my temp index.htm file on now so that is displayed.
My host told me it was up to me to make the appropriate changes to code, but I really don’t know what needs to be done.
Your host isn’t being very helpful ;-p I’ll state again: No code changes are necessary.
Moving_WordPress really shouldn’t be all this difficult!
So, if you rename that index.html, are you able to get to http://numixes.com/wp-admin/ ?
Does the error still happen?
After getting a 500 error, have you checked your (new) web server’s error logs? There might be something helpful in there.
Yes my web host is hopeless… if I rename or remove the temp index.html I still can’t get to wp-admin, same error.
I checked my error logs, they look rather strange but these are the only errors that showed up repeatedly:
[Sun Mar 2 16:12:32 2008] [error] [client 24.9.187.128] FastCGI: comm with (dynamic) server “/var/www/fcgi/php-cgi” aborted: (first read) idle timeout (30 sec)
[Sun Mar 2 16:12:32 2008] [error] [client 24.9.187.128] FastCGI: incomplete headers (0 bytes) received from server “/var/www/fcgi/php-cgi”
[Sun Mar 2 16:13:44 2008] [error] [client 87.119.120.6] Directory index forbidden by rule: /home/fhlinux150/n/numixes.com/user/htdocs/mixes/
I have no idea what that means 🙁
I assume this means that the error is something my host needs to fix? I’ve just emailed them but this means I will have to wait for atleast 3 hours for a response :/
FastCGI? Hmm, I’m not bright enough to do more than suggest that it might be your problem.
Do a search, here in the forums, for FastCGI and see if anything pops up?
you’ve helped me out anyway, thanks 🙂
I googled FastCGI and apperently it’s some sort of PHP parser or compiler on the server-side.. so be I can hope for is for my host to respond quicker !
Your not alone lordgryn I’ve been having the same problem with FastCGI and streamline.net for over two months now and I just don’t seem to be getting anywhere, all I get is the engineers are working on your problem, I would of thought they could have something sorted by now!
Dear lordgryn * rembeatz,
Did you manage to get your FastCGI error fixed?
I’m with streamline.net and everything was working fine until last thursday or friday and no i’m in the same boat as you. I’ve submitted a support ticket but not heard anything back yet.
Thanks,
James.
Unfortunately I’m having exactly the same issue with Streamlinenet:
http://wordpress.org/support/topic/167138?replies=4
