Search results

There is no apparent reason for those to not work for you, your IP is not blocked. DirectAdmin works fine as far as I can tell, what address are you attempting to connect on? Are you getting any error messages from ftp or browser?

You are trying to connect to the old, decommissioned, server which is why that fails. The current server for your account is: x15.x10hosting.com

That domain have cloudflares name severs set already, though since the IP of the server has changed you need to login to the account there and update the A record for that domain. The IP for your server is: 198.91.81.12 With domains bought elsewhere you set the name severs at the place where...

Due to the automated suspension/terminations being halted we did run a manual purge in early March (it was started the 4th) and since your account did not have any logins the the 60 days prior to the purge it was terminated as inactive. Due to there being no warning emails as those are part of...

It was never possible to set the name servers for the domains provided by x10, though cPanel had an integration for cloudflare that allowed a cname setup. Unfortunately no such integration is currently available for DirectAdmin, but with DA getting a higher user base there may be one developed...

What is the account in question? Note that resetting the password on the main login page does currently NOT reset it on the forums as far as I know. Although the forum login page should have its own password reset option if you are unsure of what the password could be here (initially when you...

Have you made sure to look in spam folders as well?

Those extensions, at least some, would likely have been part of solving the problem (you didn't have mysql enabled so that alone would otherwise have caused a problem).

Glad to hear you got it working. I'll close this off as resolved then.

To some extent you can change php.ini settings under switch php version, at the top right you'll see "Switch to options" (or some like that), on that page you can change upload limits, if I recall right the default is set at 2 mb only.

I sorted that out for you. One reason was the permissions on the folder for the subdomain was wrong. I also enabled the more common php extensions for you since there was none enabled.

I have no problems with your x10.mx domain (although it has a 403 error but that is a different reason). As for the co.uk domain, did you update the A record at cloudflare to reflect the new server? Your sever has the IP: 198.91.81.13

I have now restored from the backup, and can confirm that the domains are properly listed. Let me know if you see something that doesn't work properly.

The suspension reason says "Explanation of webhosting use needed", that would indicate you need to explain the purpose of your site and how it works. According to notes site closes or redirects instantly for instance.

Due to the automated suspension/terminations being halted we did run a manual purge in early March (it was started the 4th) and since your account did not have any logins the the 60 days prior to the purge it was terminated as inactive. Due to there being no warning emails as those are part of...

JSON is enabled in native mode. However with changing php version, it is up to the user to pick out extensions needed.

The second issue is a result of the first, repeated attempts to login to an account no longer existing will get the IP blocked indeed. Between December 16th and May 3rd you did not login to the account once, this lead it to be marked as inactive and purged in early March. The automated...

Due to the automated suspension/terminations being halted we did run a manual purge in early March (it was started the 4th) and since your account did not have any logins the the 60 days prior to the purge it was terminated as inactive. Due to there being no warning emails as those are part of...

I'm running the restore now and the account should be good to go in a few minutes. To add to Garrets information, prime was paid for yearly and not a one time fee.

That would be an indication that something went wrong in the migrations. The best solution is to redo the migration of your account, with the most recent backup from the old sever (which was taken right before they were put offline). This action is recommended in case there's something more...