Ashoat

Okay, figured out what caused the last two and fixed it.

Closed due to inactivity.

First two were related. I'm not sure what caused the third.

... same problem as last night. Should be resolved.

There was another downtime. This one was because a user hogging resources. Woohoo.

If you don't have the nameservers setup, we can't help you. I don't see your nameservers. Server: 65.19.174.2 Address: 65.19.174.2#53 ** server can't find ugconsultoria.com.br: NXDOMAIN

You probably just have an error in your code. Please reduce your code to the smallest possible snippet that reproduces this issue, and then I'll take a look.

Try upgrading Joomla! to the latest version. I'm not having that problem in my version.

No problem

No problem

... okay.

Fudge U, deng yunlan: please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active.

Try again now.

Post in this thread: http://www.helionet.org/index/index.php?showtopic=5553 Deescalated.

Okay, do this: 1) Select "Choose Log Programs" in your cPanel. 2) Click the checkbox for awstats next to whatever domain you want it for. 3) Wait 24 hours. You should see stats appear for your domain.

This isn't your thread. Open your own, please.

Learn how to spell or I won't respond to you.

I'm sorry, but hackers often use our services to execute port scans and to try to take advantage of exploits on other servers. Allowing outgoing connections on arbitrary ports is a security risk

Fudge U: please wait until "Server Load" under "Service Status" in your cPanel is below 4, and then try adding the domain again once. You will have to wait 24 hours after adding your domain for it to become active.

Looks like since you had already setup this domain as a parked/addon domain, the main domain change errored out. However, the ACP script didn't pick this up. Your new domain should be active within 24 hours or so.

We've got a bit of a backlog in the account queue. Your account should be created soon.

You should be able to view AWStats, but be unable to update it. Is this not the case?

We allow socket connections, but only locally. I do see your point, though. It might make sense to just disable that feature at this point. Again: we aren't going to open any ports for you

Sorry, but I'm not performing any code reviews for you. Hope it works out!

No problem