Krydos

The HelioHost staff have been working tirelessly for the last 12 hours, and we're happy to announce that we've already completed the repairs on heliohost.org, and we have both nameservers running again. The next step is getting Tommy back online. We're going to let the backup run through the rest of the night and we should be able to get Tommy powered on sometime tomorrow as long as everything goes well.

You should be able to login at https://johnny.heliohost.org/ for now.

Generally mail servers retry for 4 or 5 days before giving up entirely, but there isn't a rule that says you have to try for a certain number of days, so each sending mail system may have a different limit. Yes, if the email can't be delivered at all the sender should receive a bounce back message saying their message wasn't delivered, but again it might depend on which mail service they're using to send the mail. So if Tommy comes back online tomorrow or the day after you will probably not lose any mail, but it won't all show up as soon as the server comes online because the longer the server is down the less frequent the sending mail server will try. For instance, one failure means they will retry in 30 minutes or so, but after 24 hours of failures they may only try once every 4 hours. Once again all of these numbers are determined by the settings on the sending mail server, and there are no rules saying they have to do it a certain way. Another thing you could consider is setting up a free Zoho account, or another free mail hosting service, and changing your MX records on your domain. When the sending mail server retries they will see the new MX record and send it to Zoho or whoever you use instead.

Have you read the most recent news?

Due to the recent news it may take a couple days before we can complete the wipe and reinstall because we're going to be extremely busy cleaning this whole mess up.

A few hours ago our server named Eddie was hacked. This has also affected and caused downtime on Tommy Plesk, Tommy cPanel, Cody, one VPS, one of our nameservers, and certain functions on heliohost.org. Our forums, Johnny, Ricky, and the rest of the VPS are unaffected. Johnny users won't be able to login through heliohost.org for now, but if you go directly to https://johnny.heliohost.org/ you can login that way. We have already taken steps to prevent our other servers from being hacked too. We will be fixing heliohost.org first, our nameserver second, Tommy Plesk third, and Tommy cPanel last. We're hopeful that we can get this work done in the next few days. In the meantime you won't be able to create new accounts on Johnny, Tommy, or VPS plans until heliohost.org is fixed. You won't be able to transfer existing Tommy cPanel accounts to Plesk either. We have no reason to believe that password hashes or any other data has been accessed, but it's a good idea to change your password occasionally anyways just to be safe. We'll keep you updated on the recovery status.

Would you like to use your free wipe and rebuild then or?

Your invite to move to Plesk was originally sent over 8 months ago on 2022-05-29. I have just resent it. Let us know if you still can't find it.

Can you ping 216.218.216.161 or 65.19.191.145?

First of all, sorry for the long delay on all of our replies. Gmail keeps flagging all of your emails as spam for some reason, so it has to be manually approved before anyone can reply to it. The IP I listed before has now been sold, and another customer is using it. If you were to buy a VPS right now the IP you would get is 65.19.191.152. Keep in mind that there is no server listening on that IP right now so pinging it will not work. If you do a traceroute the last few steps should look like this 11 75 ms 67 ms 74 ms 100ge0-50.core4.fmt1.he.net [184.105.65.214] 12 80 ms 79 ms 79 ms port-channel2.core2.fmt1.he.net [184.104.198.214] 13 port-channel2.core2.fmt1.he.net [184.104.198.214] reports: Destination host unreachable. If you can get to 184.104.198.214 then it means you will most likely be able to get to the final IP. Yes, we can give you a full refund if none of our IPs will work for you.

The best fix is to switch to MySQL or PostgreSQL. Not only do they provide much better performance, you don't have to worry about file and directory permissions and disk io. If you insist on using SQLite for some reason you'll have to deal with version 3.7.17 because it can't be upgraded to anything newer. Another option if you refuse to use MySQL or PostgreSQL and need a newer version of SQLite is you could switch to a VPS plan where you could install any version you want, but that starts at $4 per month.

Installed. Here is the current list of installed modules and versions aiohttp==3.8.3 aiosignal==1.3.1 aniso8601==9.0.1 appdirs==1.4.4 asgiref==3.5.2 async-timeout==4.0.2 attrs==22.1.0 Babel==2.11.0 beautifulsoup4==4.11.1 blinker==1.5 bs4==0.0.1 bson==0.5.10 certifi==2022.12.7 chardet==4.0.0 charset-normalizer==2.1.0 click==8.1.3 cssselect==1.2.0 discord==2.1.0 discord.py==2.1.0 Django==4.1.1 dnspython==2.2.1 fake-useragent==1.1.1 Flask==2.2.2 Flask-BabelEx==0.9.4 Flask-JWT-Extended==4.4.4 Flask-Login==0.6.2 Flask-Mail==0.9.1 Flask-Principal==0.4.0 Flask-RESTful==0.3.9 Flask-Security==3.0.0 Flask-SQLAlchemy==3.0.2 Flask-WTF==1.0.1 frozenlist==1.3.3 greenlet==2.0.1 idna==3.3 importlib-metadata==6.0.0 itsdangerous==2.1.2 Jinja2==3.1.2 lxml==4.9.1 mailjet-rest==1.3.4 MarkupSafe==2.1.1 multidict==6.0.3 mysql-connector-python==8.0.31 mysqlclient==2.1.1 parse==1.19.0 passlib==1.7.4 Pillow==8.2.0 protobuf==3.20.1 psycopg2==2.8.6 pyee==8.2.2 PyJWT==2.6.0 pymongo==4.2.0 pyppeteer==1.0.2 pyquery==2.0.0 python-dateutil==2.8.2 python-dotenv==0.21.0 pytz==2022.2.1 requests==2.28.1 requests-html==0.10.0 six==1.16.0 soupsieve==2.3.2.post1 speaklater==1.3 SQLAlchemy==1.4.43 sqlparse==0.4.3 stripe==2.58.0 tqdm==4.64.1 urllib3==1.26.11 w3lib==2.1.1 websockets==10.4 Werkzeug==2.2.2 WTForms==3.0.1 yarl==1.8.2 zipp==3.11.0

It looks like your invite was sent on 2023-01-09. I have resent it. Let us know if you still can't find it.

LMGTFY https://stackoverflow.com/a/34839029/2336864 It looks like Python was expecting a sequence of byte string values, but you gave it a str instead.

Awesome. Thanks for letting us know that it had stopped working.

By "reset" are you asking for your entire account to be deleted and remade? You can delete files and databases yourself so you don't need help from an admin for that.

I believe this was all taken care of via Discord. I'm going to mark it solved, but if you need help with anything else or if it's not solved just let us know.

There you go

I changed some forum settings. Are you receiving emails from the forum now?

We own 16 different IPv4 subnets, and the 65.19.141.66 one is reserved for internal use, not for VPS. If you were to purchase a VPS right now the IP you would get is 64.71.153.11. Does that one work for you?

Starting tomorrow we will be increasing the transfer rate from 20 invites per day up to 30 invites per day. We are also going to be fast-tracking the existing Tommy cPanel users so we can shut down cPanel and give full resources to Plesk as soon as possible. There are 149 users still on Tommy cPanel that haven't been invited to move to Plesk yet, and over the next 5 days they will receive their transfer invites. Then once everyone on Tommy cPanel has received their invite we will be allow one week for them to find the email and move their account. Anyone who hasn't moved their account off cPanel after that week is up will have their latest backup uploaded to https://heliohost.org/backup/ and their website will be taken offline to finally shut down cPanel for good. Since Tommy cPanel users are being prioritized over the next 5 days that means a few users may see their ETA increase by up to 5 days. The reason we're doing this is so we can shut down Tommy cPanel as soon as possible. Tommy Plesk is sharing server resources with cPanel right now and that's affecting the number of accounts we can put on Plesk, and it's also negatively impacting the uptime and speed of Plesk. You can check your ETA at https://heliohost.org/eta/ or improve your position if you want with the donation link at the bottom of the page. Let us know if you have any questions or comments.

Ahhh, ok. I sent a temporary password to recover your forum account. Once you get logged in I can merge this hotmail.com forum account with your gmail.com forum account if you want so all of your posts will be credited to the same account.

Yeah, your account is too broken to move. This has happened a few times so far. I have created a new backup at https://heliohost.org/backup/ deleted your cPanel account, and sent you an invite to create a new account. Once your new account is created you can restore your files and databases, etc from the backup. Let us know if you need help with any of that.

Closing due to inactivity.