Ashoat

No, you do not need an A record. Ask them to remove all A records - HelioNet will handle that. If they really want one, tell them 65.19.143.3.

Really, how much red ink do you need? Moving, and your account will be auto-deleted after three months.

Please create a support topic in the support forums and I'll help you out

Looks like your account was deleted in the server move. Please create a new account with the same username/password.

No, you need to just use ftp://powys-dev.heliohost.org and login with that username and password.

Turns out there was an error in the account creation daemon. I have fixed it and put the daemon on full throttle. Hopefully, all accounts should be validated soon

Turns out there was an error in the account creation daemon. I have fixed it and put the daemon on full throttle. Hopefully, all accounts should be validated soon

Turns out there was an error in the account creation daemon. I have fixed it and put the daemon on full throttle. Hopefully, all accounts should be validated soon

Turns out there was an error in the account creation daemon. I have fixed it and put the daemon on full throttle. Hopefully, all accounts should be validated soon

You can run whatever you want as long as it complies with our ToS and it doesn't take too much server resources.

Did you make sure to set it to use .NET Framework 2.0? We don't support 3.0 or 3.5. There's a topic about how to do that in the Customer Feedback section or something.

Turns out there was an error in the account creation daemon. I have fixed it and put the daemon on full throttle. Hopefully, all accounts should be validated soon

Oops, sorry... I just realized there was a bug in the account validation daemon that was preventing account activation. Let me fix it and stick the daemon at full throttle so that accounts get activated quickly.

It should be gone now.

The problems should all be gone now, anyways.

I've temporarily ran out of dedicated IPs, so I requested some more from HelioHost's colocation provider. I'll let you know once the IPs come in (should be a week or so).

Create a web.config file in the same directory your .aspx file is.

And what is it?

Not unless you have a good reason.

Nevermind about that... the real solution is to CHMOD your public_html directory to 755. This is being caused by Apache not behaving as if it were being run by nobody. It's accessing all files as "other".

What error are you getting?

Why do you want changed CNAME records?

Please CHMOD the .htaccess file in your directories to 644. Nevermind, the real fix is to CHMOD 755 your public_html directory.

Nevermind, the real fix is to CHMOD 755 your public_html directory.

Please use proper spelling. Chat abbreviations are not acceptable.