Website redirects to somewhere else...

[jgamerx1]

Hello everyone. I am Jstar269, the owner of gaming/technology news and reviews website, J-Gaming. I have used x10hosting since March 16th. For the past few days, my website has been on and off from the server migrations. However, since last night my website has been un-viewable to anyone, including me. Just recently my website HAS FINALLY been brought back up, bit not in a way I wanted it to be. Instead of bringing me to J-Gaming, it brought me to Atlantic Coast Fantasy Football League. I presume some websites are being mixed to each other, and unsurprisingly putting /wp-admin at the end of the link brought me to a 403 Forbidden error. The website is http://jgamer.x10.mx

 

[Anna]

Don't panic, things will get back to normal, appears that httpd.conf is messed up causing all domains to point to the same place, we're looking into it.

 

[caftpx10]

I wouldn't say all, mine has recently went through a 403 error stage and then got to the main site without redirection, though it did have an expected issue, but that's a different thing and irrelevant to this thread.

Again, not all, maybe some.


I do find it strange that the http daemon configuration file has been set for some/most domains to that football site, slightly unexpecting from such migration.


Could of this issue affected a few older accounts (not so recent)?

 

[mobsta]

I get the same crap, can't loggin to cpanel or ftp. Not trying to panic but I've got important stuff I haven't backed up for a few days.
At least it's a known issue and will be dealt with.

 

[Anna]

I wouldn't say all, mine has recently went through a 403 error stage and then got to the main site without redirection, though it did have an expected issue, but that's a different thing and irrelevant to this thread.

Again, not all, maybe some.


I do find it strange that the http daemon configuration file has been set for some/most domains to that football site, slightly unexpecting from such migration.


Could of this issue affected a few older accounts (not so recent)?

The issue affects only accounts that have NOT yet been transferred to the new server. Currently for some reason httpd.conf decided that the footy page (which is actually the first entry in said httpd.conf) should be default for unknown domains, rather then the normal default webpage that cPanel usually throws in these cases. Unfortunately the migrations could break if we try to rebuild the httpd.conf at this point, or we'd need to halt migrations and lengthening that process a bit.

 

[mepax10m]

My vote would be to halt migrations to enable a new page with a suitable explaination to be displayed, even if it meant lengthening the process

 

[caftpx10]

My vote would be to halt migrations to enable a new page with a suitable explaination to be displayed, even if it meant lengthening the process

TBH, if my site was still being migrating then I would really go with migration just in case a few things break and plus, many of us want this migration to end ASAP. XD
Even if mine now is fully working (reached the other side), I'm still concerned about the migration since anything could happen and mess up, this is a large and long process to do.

I'm not an expert when it comes to migrations (not that experienced) but remember, breaking is nasty.

 

[caftpx10]

The issue affects only accounts that have NOT yet been transferred to the new server. Currently for some reason httpd.conf decided that the footy page (which is actually the first entry in said httpd.conf) should be default for unknown domains, rather then the normal default webpage that cPanel usually throws in these cases. Unfortunately the migrations could break if we try to rebuild the httpd.conf at this point, or we'd need to halt migrations and lengthening that process a bit.

Oh right, sorry, late night.
Could something managing the file be setting the first entry as default?, I don't even know why it would even change unknown domains to the strange default which would be the top entry.

Looks like stuff will need looking at when it comes to the end.