wolstech

This is limited to prevent the server from becoming overloaded. A well-written script shouldn't have any issues with the limits we have set. What are you trying to do, and is your script closing your SQL connections when you're done with them?

This is intentionally disabled due to a history of abuse (botnets and copyright infringement).

We're not familiar with that site. You'd need to ask its owner.

You got blocked again. Unblocked. This is likely going to keep happening while we have the firewall configured this way. I'd suggest just trying again later once the traffic from the DoS dies down a bit.

Looking at the firewall IP blocklist explains it...this was a DoS attack.

This one wasn't anything you did, you just happened to connect during an ongoing DoS attack and got stuck in the firewall. Unblocked.

That account cannot be restored because it was deleted for disk space. An invitation has been sent to the email address on file for that account so you can create a new one. We apologize for any inconvenience this may cause.

Deployed. Please note that it may take up to 12 hours for the 404 error to go away.

Looks like load causing apache to die based on the monitor. There's only 4 accounts suspended on Tommy. One account suspended on Tommy is for load (mrj's account, he posted earlier). The others are banned for malware, child porn, and phishing.

That would be this forum. It serves as our support system as well as a place for our users to communicate and knowledge with each other.

It got suspended for high load again. Let's see if Krydos can identify what's causing it for you.

That's typically how it gets taken out of read only. The thing is, in our experience, when we do that, MySQL either won't start anymore, or just corrupts everything. In the past, we had to discard the innodb data to get it working again.

You can't. Johnny only supports 5.6. Ricky and tommy offer multiple versions of php. Ricky offers free accounts at midnight UTC every day if you want to move servers. Tommy requires a donation. http://wiki.helionet.org/Moving_your_account

That's why. We have tomcat 7 on Johnny, so that app won't run. You'll need to rebuild it for tomcat 7 if you want to run it on Johnny.

Deployed. http://bfpsw.heliohost.org/JAW/

Deployment did not succeed (hung while starting). Moving so Krydos can take a look at it...

Your message is blank and the IP you posted from is not blocked.

It's worth noting that the donation is required for a Tommy account. We currently do not offer free Tommy accounts due to lack of disk space.

You can't log in by visiting the name server address. Those are only for attaching a domain to our system. You should log in at https://heliohost.org/login/

Unblocked. It was for failed cPanel logins. If you use https://heliohost.org/login/ this won't happen.

Its worth noting that at this time, a donation is required for a Tommy account due to low disk space. If you do not wish to donate, your only alternative is to wait in line for Java on Johnny.

The names themselves are just made up. There's no significance to them, the mods and admins just vote on the names. There is a naming convention though: Physical hardware has a name ending in 'ie', hence Stevie, Charlie, and Eddie. There's also one called Katie, but it's only for internal use (runs a personal project for the company founder).The VMs on the hardware end in 'y', hence, Ricky, Johnny, Tommy, Cody, (and soon Lily).

You can't, unless you want to try modifying the installer. Usually there's a folder of .sql files that the installer imports. You could edit these to change the engine flag to MyISAM and see if the program will work. Some applications require the functionality of InnoDB though and won't work if you convert their tables. If you don't want to wait until this is fixed, you can move to Ricky (http://wiki.helionet.org/Moving_your_account, free registrations open at midnight UTC every day) or Tommy (https://heliohost.org/tommy/, no free sign ups, donation required) where we have working InnoDB support.

The domain isn't the problem. The .htaccess for the django application in the folder above that document root is conflicting and breaking the domain. I renamed the .htaccess in ~/public_html/the925 to htaccess.old and your domain is now working, however your django application will not work now. To correct your issue, you need to either add an exception to exclude the oauth folder from the URL Rewrite in the .htaccess file, or just change the doc root of the addon domain so it is not inside a folder that contains a django application.

Back the database up, then make a copy of the backup. Alter the copied .sql file in a text editor to change the engine to MyISAM, and import the altered copy into a new database. In read only mode, you cannot drop your existing database, convert it, or edit it in any way.