Search results

The reason was we actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow a grace period where the accounts can be restored if asked within a week from when...

Great, I'll close this one of as resolved then. Please start a new thread if you need any further assistance.

Your account should now be back to fully operational.

Your account should now be fully operational again.

Your account should now be good to go, admin told me he was running the restore a little earlier.

The reason was we actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow a grace period where the accounts can be restored if asked within a week from when...

This should now be sorted. With the new setup the paths has changed a bit, I updated your config.php so that the correct paths are in use Path to public_html now looks like /home/USERNAME/domains/DOMAINNAME/public_html in case someone else runs into a similar propblem.

The prime option has not been active for a long time, think it was taken away as an upgrade a couple years ago even, so I'd assume that the plan expired on you since it was paid for 3 months at a time if I recall right, with the migrations any remnants of old, no longer in use, plans are...

I have once again asked the head admin to transfer the proper package to me, currently there is no account/site on the new server. I expect him to be online in the next couple hours (he's in a different timezone from me) so I'll have a word with him again if he doesn't sort it. It is possible...

The account should be back to working order, the site not working for the moment can be related to the above, some infected files may have been removed causing wordpress to not work properly. Seeing as it is giving an http 500 error it could also be due to php version not being compatible with...

The reason was we actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow a grace period where the accounts can be restored if asked within a week from when...

@sentrix1 your account should now be restored, let me know if there are any issues.

The reason was we actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow a grace period where the accounts can be restored if asked within a week from when...

Never rely on emails as a sole reminder, the requirement is there even if we don't warn you about it. We actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow...

The reason was we actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow a grace period where the accounts can be restored if asked within a week from when...

The reason was we actually purged accounts where there was no login made in the past 60 days (the requirement as per ToS is to login once every 30 days), but since we purged without suspending first, we allow a grace period where the accounts can be restored if asked within a week from when...

While inactivity suspensions would not be automatically imposed, the requirement to login to the account still remain the same even during maintenance periods. You should always assume you need to follow ToS. I have restored the account. Let me know if something is not working right.

@spinthew your account should now be good to go. Remember to always login every 30 days, I recommend much more frequently to ensure you get information as well as stay on the safe side. Never rely on emails for a reminder to login, make it a habit instead.

Often times hackers target specific versions of a script, usually somewhat older with known vulnerabilities, which is why it is always recommended to keep the script up to date. Though in your case I kind of doubt that is the case, it seem a bit to persistent for that. If it is indeed a bot...

If you want to be able to use https (though you'd be using the server cert and users would get an error) it needs to be turned on. DirectAdmin allows for different content on http and https, and unless you configure it as as symbolik link (which I believe is default with ssl turned on) you...