500mb are taken by the database, the table that holds almost all of that is the sessions table. By the looks the script you are using does not properly remove sessions since I'd say that it is not normal for it to grow this big, at least I never ran into it before (there's close to 2 million...
To me it looks like you at some point upgraded to premium hosting, which has a separate system.
You should be logging in at: https://clients.x10premium.com/login
No, they do indeed not propagate "upstream" from DA to the SSO page.
They do however sync from SSO page to DA in order for the logins to work, so changing in DA would not work at all as the first time you login to the SSO page after the change it would be reset.
Currently, the only way to...
There was a DNS issue with your domains. I have now corrected this and they should work properly again, though you may need to clear DNS cache or await its natural refresh first.
The SSL issue could be related and should in that case also be sorted with this, however it could also be due to the...
I have unblocked your IP again.
To change email password: Go to "E-mail manager" -> "Email Accounts". At the end of the row for the email address hover over the plus and you'll see two options: "Change Password" and "Download Outlook Configuration"
That is indeed your username. I have sorted out the permissions for you so you should be able to use SSL now.
On a sidenote, there is a forum account that is tied with that hosting account, it goes by the username: semx10h2 (likely derived from a previous domain). Password *should* be the same...
There is no hosting account associated with the forum account you are posting from.
Please provide your url or username so we can look it up and sort this out.
@spacresx the fact you can't reach it is related to a spelling error on the domain in the post, there's on dot too much.
@sunset your domain is currently not configured to use ssl at all. The first step would be going to "Account Manager"->"Domain Setup" and enable SSL for the domain, with or...
It was a DNS issue, where for some reason the domain pointed at the wrong IP (the old server I believe).
I have corrected this and it should now work properly, you may need to flush your dns cache or await its natural refresh though.
It was a DNS issue, where for some reason the domain pointed at the wrong IP (the old server I believe).
I have corrected this and it should now work properly, you may need to flush your dns cache or await its natural refresh though.
Logging in with email at: https://x10hosting.com/sso/login is always the recommended method as that is the only place that will mark your account as still being in use and prevent an inactivity suspension.
Going directly to server is a fallback that should only be used temporary.
For the...
Spoke a bit with Corey on this last night, he was looking into it but by the time I had to leave the computer the problem was not resolved.
Far as we can tell it only affects x11 (that's where reports come in from at least). It should work by going to http://x11.x10hosting.com:2222 as a...
Spoke a bit with Corey on this last night, he was looking into it but by the time I had to leave the computer the problem was not resolved.
Far as we can tell it only affects x11 (that's where reports come in from at least). It should work by going to http://x11.x10hosting.com:2222 as a...
Spoke a bit with Corey on this last night, he was looking into it but by the time I had to leave the computer the problem was not resolved.
Far as we can tell it only affects x11 (that's where reports come in from at least). It should work by going to http://x11.x10hosting.com:2222 as a...
There was an issue with DNS pointing to the wrong IP (likely the old Illuminated server), I have corrected this and your site appears to be working now.
I see that someone on your IP tried to login with an invalid username (DA does not take email address). To login directly to DA you should use the same username as you have here on the forums (also listed in SSO panel, it does not always match the forum one but often).
@abisacce and @cyberx16 ...