Krydos

+1

I'm guessing you were also having issues connecting to MySQL due to an abusive account trying to crash Stevie. That account is now suspended, and everything seems operational. Let us know if you're still having any issues.

I'm seeing two databases associated with your account. I'm guessing that they weren't showing up in that screenshot because around the same time that you posted this MySQL on stevie was having issues due to an abusive account which is now suspended. Let us know if you're still having any issues.

There was a malicious user abusing poor Stevie and causing MySQL to not work very well. He's been suspended now, and MySQL seems to be working fine now. Let us know if you're still having any issues.

Your account was suspended permanently due to large number of abuse suspensions so it doesn't matter what you set your nameservers to. For unsuspended accounts in good standing once the nameservers are changed it can take up to the TTL of the ns value for all computers to access the site from the current host instead of the old host. The reason for this is because the value gets cached and as the cache expires on various servers and computers they check the value again and get updated to the correct new value. During the change over time some computers will try to access the website on the old server and some will access the new server, so for the most seamless change over from old host to new host you can keep both sites active until all requests are going to the new server. Keeping your two sites synced with the same information during this transition depends on the type of site, but one solution is to set up both sites to use the same database on the new server before you change the nameservers. Obviously this might not work for all websites though. Also useful is the information that the correct nameservers for hosting a site on Heliohost is: ns1.heliohost.org ns2.heliohost.org

Your account was suspended permanently due to large number of abuse suspensions so that's why you will no longer be able to log in or reset your password.

Cgi can be really picky about permissions and syntax, and when it isn't exactly perfectly right it throws the very unhelpful 500 error. Step one on troubleshooting is to make sure your cgi-bin directory and cgi file both have 755 permissions. Step two is to make sure you're using the right shebang, which according to your code above looks right to me. Step three is to make sure you set the correct content type. print "Content-type:text/html\r\n\r\n"; Is what I use for perl cgi and it works on Heliohost. There may be other slight variations that work too. Let us know if that doesn't fix the problem.

Don't know why it keeps doing that. Very odd.

That's fine. That's not fine, and the abusive user has been suspended. That's fine. It isn't down when I checked, but low /tmp space can cause issues with mysql so I'm guessing that's what the problem was.

Not only is php mail function working, your exact file is working on your account. I copied your test.php to test2.php and changed your email address to my hotmail account and here is the result of visiting the page in a browser: Here is the email I received: x-store-info:fHNTDlzCF8Nxw6HwcfGQy+S7Ax/lqLSmNphQ3OF+T9E= Authentication-Results: hotmail.com; spf=none (sender IP is 65.19.143.2) smtp.mailfrom=fabiank@stevie.heliohost.org; dkim=none header.d=fabian.heliohost.org; x-hmca=none X-SID-PRA: fabian@fabian.heliohost.org X-AUTH-Result: NONE X-SID-Result: NONE X-Message-Status: n:n X-Message-Delivery: Vj0xLjE7dXM9MDtsPTE7YT0wO0Q9MjtHRD0yO1NDTD00 X-Message-Info: 2etWe3f/w1eCAIY8IUcwYEh3b9UZmmS6hXHLrcj3OU1dIjB0s5r3HPSe+dmpYJTK26PY9bEOFgSe0lwq83ErR20e8TDUKycyGaMJlrl88gIeJ5xIpQmQyHh8znrsom7EYz8E6KCEixWLiz/bT6riR2uja4jzgIvY Received: from stevie.heliohost.org ([65.19.143.2]) by COL0-MC1-F30.Col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4900); Sat, 1 Dec 2012 15:06:58 -0800 Received: from fabiank by stevie.heliohost.org with local (Exim 4.69) (envelope-from <fabiank@stevie.heliohost.org>) id 1Tew9a-00030x-1S for [redacted]@hotmail.com; Sat, 01 Dec 2012 15:06:57 -0800 To: [redacted]@hotmail.com Subject: Test Mail From:fabian@fabian.heliohost.org Message-Id: <E1Tew9a-00030x-1S@stevie.heliohost.org> Date: Sat, 01 Dec 2012 15:06:57 -0800 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - stevie.heliohost.org X-AntiAbuse: Original Domain - hotmail.com X-AntiAbuse: Originator/Caller UID/GID - [22306 32003] / [47 12] X-AntiAbuse: Sender Address Domain - stevie.heliohost.org X-Source: /usr/bin/php X-Source-Args: /usr/bin/php /home1/fabiank/public_html/test2.php X-Source-Dir: fabian.heliohost.org:/public_html Return-Path: fabiank@stevie.heliohost.org X-OriginalArrivalTime: 01 Dec 2012 23:06:58.0916 (UTC) FILETIME=[90B49A40:01CDD018] This is a test!

Done.

You might want to check out festival.php

Feel free to delete everything I set up and do it yourself. It won't hurt my feelings. I was just trying to help you out by getting a working example that you could copy from. You were asking questions like "So please inform if there is a working RoR app at heliohost?" so your answer to that is obviously yes. Did you change anything?

Those methods of logging in will work, but the recommended way to make sure your account doesn't get flagged as inactive is to log in at http://heliohost.org/ at least once every 30 days. That's actually not recommended because the login screen could change breaking your script and resulting in a suspended account. The best way is to log in manually to make sure that it is working.

I'm guessing your zipped file is corrupt. What happens when you extract it first before you import it? Actually partial database backups get created as .sql.gz files. The tar part isn't required because there isn't a directory structure, but it's still the same gzip type compression.

Your account was suspended for inactivity, because the last time you logged in was October 26th. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. If you are still seeing the Account Suspended page after renewing your account, please clear your cache. Creating a hosting account does not create a forum account. In fact you don't ever need to have a forum account to receive free hosting (unless you want to post on the forums.)

Details of how to download your backup have been PMed to you.

Fixed.

All of them. You've already had an unprecedented 6 chances to fix your site so it won't crash the server and take all the other accounts offline. Twice you crashed MySQL so no other accounts could access their databases, and today your account was causing almost 600% more load than the second highest load account on the server so you're done. No more unsuspensions. No more chances. I suggest you look into a VPS or even better think about purchasing and maintaining your own server because I'm fairly certain that any paid shared hosting service you found would suspend you for high load too. Your account will not be unsuspended, nor will your account be manually deleted for any reason. However I am willing to provide you with a backup of your files and databases if you wish. Just let us know if you want it.

Unfortunately we are unable to unsuspend your account because to do so would result in our entire hosting service being removed from the internet which would cause the other 40,000 or so domains hosted on our service to also be taken offline. The reason this would happen is because Heliohost received an official abuse report regarding your account. If the following information is erroneous you are strongly encouraged to contact your accuser(s) to correct them.

Perhaps you should have read the post I made 12 minutes prior to yours. Since you couldn't figure out RoR on your own I set it up for you, and I agree that the official instructions are a little confusing.

It's been over 13 hours already and this still hasn't been taken care of. Here is a hint: /home1/fabianof/public_html/fabianofernandes/blog/images/M_images/inc.php /home1/fabianof/public_html/fabianofernandes/blog/images/M_images/config.php /home1/fabianof/public_html/fabianofernandes/blog/images/M_images/contact.php /home1/fabianof/public_html/fabianofernandes/blog/images/M_images/red.php You only have 11 hours left to delete these files or replace them with clean versions or your account will be suspended again.

Your account is now showing up as clean. Thanks for taking care of this.

I created a fresh RoR setup for you, and started it running. The ruby files are located at /home/sehrguey/rails_apps/depot and you can see the working RoR default stuff at http://depot.maht.heliohost.org/ Your old ruby files are still where you created them at /home/sehrguey/depot and you can transfer them over to the working setup if you wish. Thanks for pointing out how confusing the wiki article is. I didn't write the original one, but I also found the instructions kind of hard to understand. I might have to rewrite it sometime to make it easier to get started with Ruby on Rails on Heliohost.

So, are you able to log in and you just can't change your password, or are you not able to log in either?