Search results

Your account has been terminated due to inactivity. Unfortunately this is an irreversible process, and your data is unrecoverable. Though it is usually twenty-one days before an inactive account is terminated, the termination can happen any time after a two week period (14 days).

What country are you from?

Huh?

I'm not talking down to you, I'm just giving you information, as I would give anyone, including our premium customers that I work with on a daily basis. I'm sorry that you feel like we're belittling you, but we're not.

Unmetered doesn't mean unlimited, just fyi

Did I suspend you? Did I terminate your account? No. You're taking all of this way out of proportion. I simply mentioned to you that you should probably clear it up. If you don't like it, then please, leave. I appreciate your ability to use big words, it really makes me thing you're very smart.

You're probably going to have to reset the user's password (mysql user).

This has been resolved.

Just because there's an option for it doesn't give you the right to breach the terms of service. We have no problem with you making backups, but your web space isn't for hosting backups...

I've ensured that the server time is synced with a time server. If your issue is not resolved, then the issue is most likely not with the server, but rather with your script.

This is resolved. I set your account to the unmetered disk space plan.

Turn on error reporting. You're not getting output from your script.

Almost completely impossible to verify anything is working when you took down your forums. I reimported your database from a backup. This *should* be fixed now. Please, please, PLEASE change your mysql password. It's incredibly unsafe.

You should be able to park the domain yourself, now.

You need to edit ~/www/application/config/db.php and change the configuration settings.

Resolved.

You were blocked for too many login attempts. I've removed you from the firewall.

We do not support perl on free hosting.

Hey guys (and girls), We think that our datacenter might be filtering outgoing traffic on XO3, causing this issue.. we're working on it.

Huh?