Search results

There is something funky with DNS making propagation slow and/or flaky in some cases, higherups knows and was last I heard looking into it, I haven't had confirmation that he solved it yet though.

There is something funky with DNS, that IP is that of the old server and should NOT be the result you get for your domain, I have alerted higherups (there are some other things related to DNS he is already looking into so might be related). Though, if x13.x10hosting.com also pings to the same...

Both hostnames should work, with the one noted in Quick FTP there is a SSL certificate though. If you had checked that before the migration, it would also have listed the server (xo#.x10hosting.com)

localhost should always connect you to the correct mysql server, you should not even be able to connect to the old one from the new server. Can you check if the domain actually responds with the correct IP using the ping command (windows powershell can be used for that for newer windows...

Your issue was not the same as original poster, it is always adviced to start your own thread so the request doesn't go overlooked. I can't see any problems with mysql management or phpmyadmin for your server right now.

Your account as been redone. Let me know if there still are any issues

Do you get any errors? DirectAdmin works perfectly fine for my account on x11

What does it say in your error log? You will find it under "System Info & Files->Site Summary / Statistics / Logs". That is a wordpress thrown error and would indicate that there is something wrong with wordpress itself rather then a serverside error.

Do you have an index file (ie index.html, index.php)? If you have a designated landing page with a different name you'll have to tell the server you want that to load by default, or change its name (and any links going to that file). To tell the server that your landing page should be the one...

I have alerted the admin in charge of the migrations about that, he's usually fairly quick on it

You can stick with that if you want, just remember that if you want subdomains, email etc you will need to update at your registrar as well. I put admin on the case so hopefully they solve any issues with dns as well, I did see a couple odd things when I dug around

Would you mind if I set a temp password for DA and attempt to login to your account, to verify if the issue is account or connection?

The direct login link for DA as noted by spacresx would only accept a username (dtfx10m2) Good to know you can login through ftp, that means the issue is not an IP block in place at least.

I agree that something is in the works, your IP is not blocked, I have been looking at a possible chance that the failed two-steps have blocked it somewhere other then our firewall, and it is not in the other known place.

foxstats forum account is associated with that domain... For SSO page and server nothing is changed, it is ONLY when you login here at the forums that you should be using foxstats as your username.

The foxstats account was created in 2016, likely together with an hosting account you created at that point. I can only see the email that is tied for the SSO login (which is the same as you posted earlier), I can not see any email addresses associated with forum accounts here at the forums so I...

I have turned it off. For future support requests, please try and use the proper forum account.

Your IP is not currently blocked. For security reasons I can not make any changes to an account when the request does not come from the verified accountholder. That said, I have tested with my account and even with two-step auth on I could login through SSO without being prompted to use the...

Actually, you could probably try logging in through the sso page, we have implemented some changes that should make it possible to always login through that page, regardless of mismatched passwords. I can unfortunately not tell you what email address that forum account is under, but since it is...

That would be something you do at your domain registrars end, login to the controlpanel there. You'll need to switch the domain back to using their nameservers (they can help you with what those are if they are not readily available). Set the A record for the domain to point to: 198.91.81.15