Krydos

You can see your mining results at https://www.heliohost.org/heliomine/scoreboard/

It's working now https://www.sslshopper.com/ssl-checker.html#hostname=industryus.ca

New email address provided via Facebook, and an invitation to create a new account has been sent.

There you go https://secege.heliohost.org/secege_hs/

See https://www.helionet.org/index/topic/33698-can-i-use-my-maildomainca-domain-for-email-when-i-havent-resolved-the-blacklist/?p=151229

Looks like you need to get removed from the google blacklist before AutoSSL will work. You can try https://wiki.helionet.org/Installing_a_Let%27s_Encrypt_SSL_Certificate but it might give the same error.

There you go https://krydos1.heliohost.org/56/phpinfo.php

Neither of those will work. If your website was up you could access your cgi script by going to lustboy.heliohost.org/cgi-bin/gettingUsers.py in browser or with a cron command such as /usr/bin/python3.6 /home/lustboy/public_html/cgi-bin/gettingUsers.py

Sometimes cloudflare causes more problems than it solves. Cloudflare only operates on port 80 and 443, so it makes sense that 2078 would have appeared closed.

The problem is the ddos attack. We're trying various methods of mitigation to see what is the most effective. The best solution to the problem is switching to Ricky or Tommy which aren't affected by the ddos attack.

It looks like autossl was getting stuck on certain domains and working on others. I deleted the autossl pending queue, and resubmitted your domain for a new certificate. It seems to have gotten past the sticking point this time and is just waiting on comodo to issue the certificate. I'll update again once it's installed, but it looks like it's going to work this time.

Also your ssl certificate is fine https://www.sslshopper.com/ssl-checker.html#hostname=ancientslab.com

Yes, it is # telnet ancientslab.com 2078 Trying 65.19.143.6... Connected to ancientslab.com. Escape character is '^]'. ^] telnet> quit Connection closed. This is what a closed port looks like # telnet ancientslab.com 2076 Trying 65.19.143.6... telnet: connect to address 65.19.143.6: Connection refused WebDAV on Tommy is working for me.

Sort of. I'm moving some accounts around on Johnny and cpanel very helpfully edited the dns zone for heliohost.org to be on the ip 64.62.211.131 instead of 65.19.143.5. I changed it back, but it can take a while to start working everywhere again. Running the command ipconfig /flushdns on windows might help.

Just wanted to mention that you can hasten this process at https://www.google.com/webmasters/tools/home?hl=en Once you have your account set up and your domain registered in your control from google click the Security Issues tab, and request a review. Generally they get the review done within 72 hours and if the phishing content is gone the dangerous site error goes away in everyone's chrome browser. Your new account has been moved to your dedicated IP.

Done. You should now be able to log in and your website should be working again.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Let us know if you have any problems adding them to your new account.

You'll have to use your latest backup.

These should all be available now. What domain(s)?

Only one other account was affected.

My apologies. In my haste to combat the AnonymousFox wordpress hacks I missed a single character in my script. Thanks for letting us know so quickly. I'll be checking the other suspended accounts to make sure they weren't suspended in error as well. Unsuspended. @wolstech The admin tool is fixed.

I wouldn't risk it personally. Having wordpress installed on your account is just a time bomb. Eventually it will be hacked, and it will be a mess.

Try changing the password of ducquang_main. I deleted that user and recreated it and reassigned it to the database, but obviously I don't know what the password was.

Which postgresql user are your trying with?