Krydos

Why repeat information that was already summed up in the first word of jje's post while contributing exactly zero additional information?

About a billion .'s later it finally said Done. Dig now shows the same info for tirocangas.com on both ns1 and ns2. Give it 24 hours from this time and we'll see if it's all working tomorrow.

I've noticed that when I use filezilla to upload or download a full sync of my site (thousands of files transferring for more than 5-10 mins depending on my connection speed) the entire site goes down and starts throwing 500 internal server errors. As soon as I close down filezilla (just closing the program not killing any processes on the server) all the errors go away and everything loads properly like it's supposed to. If you're actively downoading, uploading, testing, using mail, etc etc you will probably hit your process limit, but if you give it a few minutes to settle down your site will run fine again. Or you could just make a post here every time you start to overload your site. That works too I suppose.

I just suspended both my accounts on stevie and johnny and they both displayed the correct new suspend message. http://cody.heliohost.org/suspended.page/ still shows the old message, but it's not like anyone is ever going to see that unless they are clicking my link to find it.

Dig shows ns1 and ns2 have different records for TIROCANGAS.COM still. Currently running the DNS sync again to see if it helps.

Good to know. I'll file that script away for future reference if I run into this again.

What is your cPanel username? It sounds like it might be a process limit cap. Also moving this to Customer Service forum.

Did you try changing your password yet using the tool that I linked? The reason I suggested it is because maybe you're using a character in your password that is escaped properly and works for cPanel login, but the domain name change script doesn't escape it properly or handles it slightly differently causing it to think your password is wrong. Worst case scenario your account becomes slightly more secure (because you should change your passwords regularly anyways) and you help us troubleshoot why this script has worked for hundreds if not thousands of other users and it only fails for your particular case. If you're in a hurry to get the new domain up and running faster you could also add it as a addon domain or a parked domain through cPanel.

Can you log in to cPanel using your username and password? If you can't (you're using the wrong password) you can use this page http://stevie.heliohost.org:2082/login/ to reset your password.

Depending on how customized the joomla install is that you're trying to move it might be easier to use softaculous or at least do a fresh joomla install and then transfer all the data and templates over.

Your site masteracoservices.heliohost.org is actually located on stevie. That server doesn't support .NET so that's why your .aspx file isn't processed. You could move your account to johnny by following these instructions http://wiki.helionet.org/Moving_your_account

That was 12 days ago. That's like 2,318 years in internet time.

Welcome to heliohost. We think so too.

The server stats were enabled for all accounts and it caused a lot of unnecessary server load because only a small fraction of websites actually used them or needed them. There are plenty of alternatives, the most popular or which are probably google analytics and piwik. More information can be found on the wiki http://wiki.helionet.org/Site_statistics

I've never used net2ftp but glancing at their website it doesn't look like it would cause a lot of server load.

What causes the script to take so long? Is it because it causes massive server load, is it because it is waiting on some other slow server somewhere to respond, or is it some other reason? If it's massive server load then maybe you shouldn't be running that process on our servers anyways because it will likely get you suspended eventually.

You'd have to ask jje, but I'm guessing that based on this he hadn't thought to dropping a redirect index file in there so he escalated it? I didn't actually look at any of those files so I have no idea if the directory listing should be visible or not or if it presented any vulnerability or not. If you're certain there is no threat feel free to de-escalate this thread, or jje can do it. If nothing else this thread can be a note to djbob that basically just says, "Hey, we messed with the files in your stevie account a little. Hope it's all good."

As a regular user you definitely don't have access to enable modules in apache and recompile, however if you are interested in seeing what our root administrator has to say about this potential installation I can escalate this thread to bring it to his attention. There is a chance that he will add it, especially if this upgrade could benefit many users.

I think he was just concerned that something might be broken, or it was a security vulnerability.

Except that softaculous sets the database up for you.

Closing...

Generally we advise waiting 48 hours for the account to be deleted, but depending on how many accounts are in the queue, server load, etc it might take longer or it might even delete in less than 48 hours. It's fairly variable.

It looks like your old account hasn't deleted yet. When did you run the deletion script to add your account to the deletion queue? There are currently 187 accounts on Johnny that need to be deleted.

By the way, bandwidth is unlimited on heliohost. That said, server load, process count, and storage space are not unlimited. Some services can use a lot of bandwidth but use very little server load. Some services can use barely any bandwidth but bog the servers down with massive amounts of server load. In my experience ftp uses very little server load, but it can use up a lot of your process limit. Sometimes while actively downloading or uploading through ftp your site can experience 500 internal server errors because you hit your process limit.

Why not just drop an index file there that redirects to heliohost.org or something? Then djbob can fix or unfix it as he sees fit when he has a chance? I don't really see how that could hurt anything.