wolstech

The domain imediaearth.com is stuck in limbo...it's half-added. It shows in the admin tools as being on your account, but not in WHM. It also didn't appear under addons or aliases in the user cPanel, yet had DNS records that Krydos found. Reparking yielded: Park::park failed: (XID shmkf9) A DNS entry for “imediaearth.com” already exists. You must remove this DNS entry from this server or all servers in the DNS cluster to proceed. The domain imediaearth.com has been cleaned up, and re-parked on your Tommy account. Give it an hour or so, and the queued page should go away and mail should start working.

You won't be able to delete it since it is suspended. It will delete itself in due time. The account's username is bhandra and it's domain was bhandra.tk. I cannot post the entire email address for privacy and spam reasons, but it's an email address that looks like sum****3@****l.com

Unsuspended.

@Kassu: Your post has been split: https://www.helionet.org/index/topic/41562-graphics-design-in-finland/

It's because you have two accounts. You're only allowed one. Which one do you want to keep?

It's not bandwidth that gets you suspended for this (in fact, we don't even monitor bandwidth, it's unlimited). It's CPU and RAM use on the server that gets you a load suspension. In your case, it was RAM use. You can see here: https://tommy.heliohost.org:2083/frontend/paper_lantern/load/index.live.php The closer you are to 100 on that chart, the more likely you are to be suspended in the event the server starts to bog down. Your account's RAM use was at 100 for 3 of the past 7 days, and near it for 2 of them, so I'm not surprised you got suspended. Krydos can check and give you a process name, but that usually just says it's PHP...we don't really have a way of knowing which file caused the excess load, but looking at your account, the forum is my guess since most of the other folders appear to contain simple HTML files.

Your account was suspended because Wordpress is causing too much load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. This is really common for Wordpress. It can cause massive amounts of load even if you're hardly getting any traffic to your site. Wordpress is also incredibly insecure and very easy to hack. We see Wordpress accounts get hacked all the time and usually the hacker sets up a phishing site on your domain. We strongly recommend using any software other than Wordpress. Something that might help is this simply static Wordpress plugin. It will speed up your site, reduce the load you cause, and reduce your chance of getting hacked. If you try it let us know how it worked out for you. If you insist on using Wordpress you might want to consider purchasing a VPS instead. VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access. Wordpress sites load relatively slowly on our shared hosting, but they will be much faster on a VPS.

There was an internal problem with the database server on Ricky that made it impossible to reuse the username victord, so we had to change the username to restore the account.

Krydos will need to unarchive this since it failed:

Not surprised by the lack of a response...

It's banned for phishing. I think the contents speak for themselves here: root@ricky [/home/online1/www]# ls -R .: cgi-bin chasebankaction.heliohost.org chaseonline.verify.com online.chase.com www.online.chase.com ./cgi-bin: ./chasebankaction.heliohost.org: cgi-bin ./chasebankaction.heliohost.org/cgi-bin: ./chaseonline.verify.com: cgi-bin ./chaseonline.verify.com/cgi-bin: ./online.chase.com: cgi-bin ./online.chase.com/cgi-bin: ./www.online.chase.com: CHASE_SCAMPAGE_2020.zip httpswww.chase.com ./www.online.chase.com/httpswww.chase.com: 8714f763f70c08a8edd5088028738c18 blocker.php index.php page ./www.online.chase.com/httpswww.chase.com/8714f763f70c08a8edd5088028738c18: confirm.php Email.php HARD.php images img.php index.php mailer.php ./www.online.chase.com/httpswww.chase.com/8714f763f70c08a8edd5088028738c18/images: back1.png d2.png d6.png fff.png hard.png headerss.png loginscreen.png slide2.png sss.png c1.png d3.png d7.png fobefore.png HARD_upload.js jquery.fileupload.js log on.png slide3.png update2.png confirmacc.png d4.png demo.png footer.png head2.png line2.png logo.png slide4.png update.png d1.png d5.png favicon.ico footersss.png head3.png liness.png slide1.png slide5.png ./www.online.chase.com/httpswww.chase.com/page: confirm.php Email.php HARD.php images img.php index.php mailer.php ./www.online.chase.com/httpswww.chase.com/page/images: back1.png d2.png d6.png fff.png hard.png headerss.png loginscreen.png slide2.png sss.png c1.png d3.png d7.png fobefore.png HARD_upload.js jquery.fileupload.js log on.png slide3.png update2.png confirmacc.png d4.png demo.png footer.png head2.png line2.png logo.png slide4.png update.png d1.png d5.png favicon.ico footersss.png head3.png liness.png slide1.png slide5.png root@ricky [/home/online1/www]#

It was indeed high load. Unsuspended. Krydos might have an idea what caused the load, however the servers these days usually only point to a process name, which will probably be PHP.

It's banned because we have reason to believe it was intended for phishing...care to explain why you picked that domain and appear to be hiding behind what I'm guessing is a VPN running on AWS?

Because of Cloudflare. Our systems don't support CF properly. Remove it and set the NS to ns1.heliohost.org and ns2.heliohost.org, and it should work. If it does, once the site is working, try deleting the zone from Cloudflare and letting CF set it up again.

Unsuspended. If you're building a support website of some kind, do not use the logos or likeness of any legitimate company such as paypal or a bank. Doing so will result in a permanent ban for phishing.

Krydos might know why this is...

Unarchived.

What do you plan to use that account for?

Do you mean how to change it?

No idea what causes it to happen, but it seems to happen to most users after a while, and this exact scenario is the reason we don't support FTP over TLS.

Unarchived.

What settings are you using? The correct settings are below. Please keep in mind that we don't support FTP over TLS (though it's known to sometimes work randomly), so if you're using that, it's probably why you're experiencing issues. If you're unable to use SFTP, please use "plain" (unencrypted) FTP on port 21 instead. SFTP host: tommy.heliohost.org SFTP port: 1342 SFTP protocol: SFTP SFTP logon type: Normal SFTP Username: trenten SFTP password: <same as cpanel>

You've done all the steps right. Depending on the host though, there are a few that block external databases on their end, so it might actually be that your other host doesn't allow it. What happens if you try to remotely access your database from something like your home computer?

What account is suspended?

FTP issues are usually load related. You said it happened right around the time registrations opened so the server is probably busy setting up new accounts...