wolstech

Many of the accounts probably aren't going to migrate perfectly anyway. I can almost guarantee there will be things that need changing like paths, host names, or database credentials for many sites even if the data moves over completely. Plesk itself isn't being rewritten, the account migration script is, so I took the options to be "Wait in line for account migration" or "Get an empty account without waiting and restore backups manually". If the other non-migration components like load management were finished, this is exactly what I would be suggesting. Backups are available for download for every account we have. We could have easily gotten everything that isn't migration working, and offered users an empty account instead of moving it for them. The user isn't losing their data either way. An empty account + backup just means they have extra legwork to set things up, which I'm sure many will gladly do if it means they can get a working account sooner. We could have then worked on fixing the migration scripts last, just moving the users who decided not to take the empty account + backup. All self-restore users would already be moved at that point...

Suspended.

What happened here is that Plesk's conversion script didn't perform as advertised. They told us they would be able to easily import cPanel accounts with the provided scripts, but those scripts don't actually import the accounts properly or completely. As provided, those scripts were effectively useless. Krydos was trying to rewrite those scripts and is flying solo on that project. None of us have any insight or input into what's happening. Honestly, my opinion is that we should have scrapped the migration idea the day we found those scripts didn't work and moved on to getting the more important things working (there's a lot of custom stuff we use to manage accounts, load, abuse, java support, etc. as well, and all of that needed to be ported to plesk before we can accept new users). HelioHost is far from out of business, but for now our primary focus has been on that migration and paid VPS services. Those services are open for new customers, but the free offering doesn't look like it'll be available for the foreseeable future unless something changes.

Krydos can update this for you.

We no longer have a license for cpanel so we can't create any new accounts on the old servers. We haven't been able to create new accounts in 6 months. We're moving to Plesk but that isn't done yet.

It's also worth noting that this user will not be moved to Plesk. He was archived at the time the licenses were revoked, so he will need to sign up again and restore his backup once we actually have working servers. The archive is available for download at https://heliohost.org/backup/

Krydos can add your donation for you. Escalating.

It's hit or miss. We don't officially support it, though it often does work now (we figured out why it never did before a while back). Plain is most compatible though. We have a bunch of users that couldn't use encrypted communications at all. Most often it's due to restrictions on their network (e.g. work or school with a filter), but in some cases it's an entire country (there are several countries where encryption is banned or requires special approvals and/or configurations to use). We don't provide service to the most notable two countries with such laws (Iran and North Korea), but some others we do serve have similar restrictions as well. We have insecure connections available to support these users.

One point about that: If you use plain FTP, it must actually be plain FTP (the important one is "no encryption" as moneybrz shows in his picture). If you use the "quick connect" or similar in Filezilla instead of adding the site and setting it up completely, it will default to FTP over explicit TLS, which is not supported.

It can take time for a security service to rescan and remove the listing on their own. I would check to see if they have an option to submit the site for review or to contest their malicious designation, but that’s about all you can do. Since blocking it is their decision, there isn’t anything we can do on our end to fix it.

I agree. Probably not a popular opinion for many, but I personally think K should never have gone down the path of trying to fix the scripts, and instead just thrown out the idea of a migration and re-invited everyone once we realized it wasn't as easy as claimed. Migrations/imports often come with tons of (sometimes hidden) issues that can manifest weeks, months, or even years later. Look at it like a PC operating system: Do you upgrade Win7 to Win10 and hope you don't find quirks in your files and software due to the running migration, or do you toss Win7 entirely and install fresh Win10? The latter tends to work better, but the former is more convenient.

We aren't accepting new users for the shared hosting at this time because our licenses for cpanel got revoked. We're in the process of moving to a new platform (Plesk) but that isn't done yet. Django was supported on our free accounts when we had cpanel, and I imagine it will be supported once Plesk is working as well since it was a pretty common request.

I just looked and this is not frozen or down. I can see the console just fine, and it is responding enough that I can type in the password box (strange to see a GUI installed on a linux server, but still, it's not down on my end).

As of now, you can't. Krydos or yash has to restart them for you. Odds are unless you shut it down, it's more likely to be frozen from broken software or perhaps misconfigured if you were changing something when it went down (I've seen users firewall themselves out of their VPS for example...).

HTTPS is working fine for me on your site. For malwarebytes, I don't blame them for flagging it malicious. Your website freezes my browser shortly after it's opened due to the size of that table, followed by the tab crashing with a memory error. As for FTP, you're supposed to be using tommy.heliohost.org as the host name for FTP, not your domain. We do not support custom domains nor custom certificates on FTP.

The servers still aren't ready. We don't have any idea when anything will happen for free users because the plesk migration simply has not gone to plan. None of us really know about Plesk (been in the cP camp forever), so we're learning as we go, and the migration scripts they gave us were unfit for purpose so a solution for that had to be custom developed. It also doesn't help that Krydos is doing most everything himself, including VPS support. Like us he's a volunteer, so there's a real life he has to tend to and only so much time in his life to do this. Since none of us really know much about Linux (I'm a Windows guy, so I'm not much help...), there isn't much for me or the other admins to do except tend to the forums and Discord. We do plan to continue offering the free/donation plans you know from the cP days with the same space/resource limits/etc. as before Only our newer Morty offering with more resources will be marketed as a paid product. HH operates at a loss currently, which is not sustainable long term...we got to keep the lights on somehow.

Krydos has to do this for you

Escalating to Krydos since the account in question doesn't exist according to the database. It also doesn't exist on any server that I can find. My guess is it was archived or suspended when the licenses were revoked...we deleted all of those from the database (I really wish we hadn't done this, it would make researching things much easier...). Suspended ones can be restored assuming they're eligible to be unsuspended, not sure how archived ones are handled though since they don't actually exist as an account. @Krydos: Would it be possible to update the ETA tool to understand archived/suspended accounts? As it stands the ETA tool doesn't even seem to understand the concept of a nonexistent account let alone a suspended/archived one. If not, can we at least make a list of these accounts visible to admins somewhere?

There is no such account according to the database. Krydos might be able to find it, but I can't escalate the news post. Please make a new topic for this issue.

It's also worth noting that at this point, we also have no idea when Plesk will actually be available. I personally had expected it to take no more than 2-3 months at the outset, but it's been 6 with no end in sight. Krydos is trying to get it working, but apparently the conversion tools Plesk provided for importing the cPanel accounts were severely inadequate and had to be basically rewritten. In the meantime, you can use SFTP to administer your site, or download a backup https://heliohost.org/backup/

You can view existing mail by downloading the mail files from SFTP (they're kept in the mail folder in your home folder). There are folders inside for each domain and mailbox. The files with the really long random looking names are the actual emails. They are RFC 2822 compliant text files, and if you download and rename them to have a .eml extension, apps like Outlook and thunderbird can open them for viewing, sometimes with minor errors (.eml is a subset of RFC2822, the files you download meet 2822 but not necessarily the .eml substandard). As for accessing new mail, the mail server stopped working entirely when the licenses got revoked, so the mailbox shouldn't have any new mail. It's been bouncing since July.

Krydos needs to do this.

Gone.

Krydos has to do this...

Krydos can update this for you.