Ashoat

Closing due to inactivity.

No problem

I'm not seeing your screenshots.

So... I'm thinking it's pretty unlikely that they broke into the server. I figure they'd be hacking heliohost.org or helionet.org if they had access. My guess is that you guys were all running the same software that had a bug in it. What CMS/forum/blog software were you guys all running?

Yeah, this is a Ponzi scheme and those are illegal.

Geoff: in general, you pretty much do. saml: if you're self-signing (using our services), you should be aware that every modern browser will highlight your site in red and warn your users from visiting your site. Are you sure you still want to do this? To use an SSL certificate correctly, you'll need to purchase one from a "trusted root" provider.

I don't think it's necessary. What hostname would you point the CNAME to?

They record the reason in the database... You need to view from the "SUSPENDED" filter, though.

I can give you a dedicated IP. But first: what provider are you using for your certificate? Is it self-signed?

Sorry, but there's no way we can do that All errors are written to a global error_log on our system. The cPanel "Error Log" just searches this log for messages it knows are directed at you. However, 500 errors are usually split up across a couple lines, and the important lines don't have the identifying information. It's the fault of cPanel's search for not being able to pick those up, but the only way you can get access to them is to ask me to take a look.

I have no idea what you're saying. Your site looks fine to me.

The A record should already be set, and I don't know what an RNAME record is... but I guess you can add it if you want? You'll need an MX record pointing to the same domain/IP that your account in on.

Geoff's suggestion is very good.

Yeah, the reason your mail isn't working is because your nameservers aren't pointed to us. As such, we have no control over the MX records that allow us to host your domain. You have two options: 1) Find a point to point your nameservers to us so that we can set your MX record for you. 2) Find a way to set your MX record from your domain registrar.

You mentioned an MX record. Who did you point your MX record to?

The fix is to basically go through /var and try to delete unnecessary things. Probably leave this one to me.

It was a temporary thing, but if it happens again just post a support thread. Glad it's working now

Okay, it should be working now.

The problem is that our /var partition is filled up. I'm working on cleaning it up right now.

No problem

Looks like the issue was a broken named.conf. I regenerated it and your guys' sites seem to be working fine.

This issue is kind of weird... but I'm working on it.

otakuz: 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.

No problem, and sorry that there's a bug

No problem