Krydos

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.

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?

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

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.

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

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.

Closing due to inactivity.

Installed. Here is the list of currently installed modules: aiohttp==3.8.3 aiosignal==1.3.1 asgiref==3.6.0 async-timeout==4.0.2 attrs==22.2.0 certifi==2022.12.7 charset-normalizer==2.1.1 click==8.1.3 discord==2.1.0 discord.py==2.1.0 Django==4.1.5 django-bootstrap-modal-forms==2.2.0 django-nested-admin==4.0.2 Flask==2.2.2 frozenlist==1.3.3 gunicorn==20.1.0 idna==3.4 itsdangerous==2.1.2 Jinja2==3.1.2 MarkupSafe==2.1.1 multidict==6.0.4 paytmchecksum==1.7.0 Pillow==9.4.0 psycopg2-binary==2.9.5 pycryptodome==3.16.0 python-dotenv==0.21.0 python-monkey-business==1.0.0 pytz==2018.5 six==1.16.0 sqlparse==0.4.3 tzdata==2022.7 Werkzeug==2.2.2 whitenoise==6.3.0 yarl==1.8.2

There you go Test it out and make sure it works as expected.

Your VPS has been upgraded to 2 GB memory, and your old subscription has been canceled.

Here's the link to set up the new subscription. https://heliohost.org/vps/pay/?code=ijNhHKePX5ttw587 Once it's set up post back here and I'll cancel the old subscription, and increase the memory.

I'm not seeing it. Try one more time.

Yeah, this account took 21 minutes to unarchive. Probably because the load was high. The renew page gives up around 10 minutes I think, so that would make sense if they tried twice, and it still hadn't finished. The unarchive process was pretty thoroughly tested, but it's still relatively new so there are a few kinks to work out still. I still think it's a huge improvement over the old system where a root admin had to unarchive each account by hand. Are you able to login now?

Your IP has been unblocked in the firewall. You were blocked for trying to log into the SFTP account that had been deleted. In order to submit a password for your SFTP account securely please go to https://heliohost.org/password/ and submit the username, such as tstamp_root and the password you want to use. After you submit the password post back here and I'll create the SFTP subaccount for you. We will never have access to the plaintext password if you submit it this way.

A HelioHost user noticed, and reported to us that there was a minor SFTP vulnerability on our Plesk servers. We have confirmed the report, and have taken action to prevent it in the future. The main account's SFTP access was correctly chrooted to the home directory so when you connect to SFTP the only directories and files you can see are your own and you can't see the rest of the server. However, if you created an additional SFTP subaccount it was not correctly chrooted which would allow limited read-only access to portions of the filesystem. It looks like the only information people who used the vulnerability would have had access to is usernames and main domains of everyone on the same server as them, so not a huge deal, but it's best if they don't have access to even that. They were not able to see any directory names, filenames, passwords, emails, or access any files within your account. In order to prevent this vulnerability we have disabled the ability to create additional SFTP subaccounts, and deleted all of the existing subaccounts on the server. It looks like most of the subaccounts that were deleted were simply trash that was transferred over from cPanel, but a few users may have intentionally created SFTP subaccounts. If you intentionally created an SFTP subaccount and have discovered that it has been deleted you can either switch to using your main account for SFTP, or if you absolutely can't use your main username for some reason an additional subaccount can be created for you by an admin so that it will be properly chrooted. Thanks to the user who reported this to us, and thanks to everyone for understanding that we have to disable this feature to keep your account secure. Hopefully Plesk will fix their software at some point so we can re-enable it.

VPS password resets are not automated yet so I'm not sure where you're expecting to get an email from. Were you trying the forgotten password link from this forum? Anyways, you've been emailed a temporary password. Let us know if you still can't get logged in.