wolstech

Uptime Robot is incompatible with Cloudflare when the proxy feature is enabled. If he turns off the proxying on CF for the root domain's A record, it will work. The problem he's seeing is because he's trying to check a nonexistent mail server in Cloudflare's data center instead of the actual mail server on Tommy. Similarly, a monitor for HTTP will have the opposite problem (always reports as up even when its not because CF will respond even when Tommy is down). If you want to use the CF proxy feature, set Uptime Robot to watch the server's host name instead of your own domain (it'd work if he points it to tommy2.heliohost.org instead). I use the same config and chose the tommy2.heliohost.org option since I wanted the proxy for speed.

That explains the issue...the admin mailbox is unmonitored. From my understanding that mailbox is mostly used for receiving automated notifications from our service providers and such, and most of the people who provide support here (including me) don't have access to it. This support@heliohost.org address is the proper place to email for support requests, including cancellations. The messages sent to support are made available on our forum, so they are seen and responded to regularly. We'll be looking at a solution such as an auto-reply on that unmonitored admin mailbox to help prevent this from happening in the future. We're always looking to improve how we serve our users, and if you have any additional ideas or comments for this issue, feel free to let us know. Thank you for the feedback on your experience.

You can't set this up yourself on our free subdomains (or any other domain that's using our DNS). Krydos has to do it for you.

Your account is showing as being on Johnny, so you should be using johnny.heliohost.org and port 1373. (Note that even if you had a Tommy account before, when you migrate to plesk, your account moves to Johnny for capacity reasons, Johnny is faster anyway at the moment...at some point in the future we'll offer the ability to move back to Tommy).

Please try using Filezilla. I don't use Total Commander, and it's not a client we test with or recommend, so no guarantees it'll work. We usually recommend Filezilla or WinSCP. I just tested these configurations using Filezilla and they work fine: Plain FTP or FTP with explicit TLS on port 21 (both tested using passive mode) and SFTP using port 1373. No other configurations (such as implicit TLS, FTP/FTPS on ports other than 21, etc.) are supported.

You're using the wrong protocol. Port 1373 uses SFTP, not FTP. Make sure you're using the right protocol. If you want to use plain FTP or FTPS (which is not the same thing as SFTP), change the port to 21.

Please keep your issue in your original topic.

ASP.NET is only available on our Windows server Lily, which does not have a control panel. I have to configure IIS manually for each user, and you get FTP access to upload your code. Lily does not have Postgres, but you can use the one on the Plesk server (you'll need to request remote access from 65.19.141.70 if you want to do that). Do you want me to set an account up for you? Please keep in mind also that Lily will likely be rebuilt with Plesk at some point in the future so it can have a control panel, but there is currently no ETA on when this will happen. Krydos can do the remote Postgres.

Account mxtech has been deleted and an invite for a new account has been sent.

Restored. It may take up to 2 hours to work.

Krydos is the Python expert here. That said, I looked at the code, and based on the last few lines of code (which are supposed to make it listen on 0.0.0.0 port 5000), it looks like this is a custom daemon (standalone server that listens on its own port and doesn't serve through Apache/Nginx), which is not supported on the shared hosting. If that's how this is supposed to work, you'd need to buy a VPS.

Bookmarked PhpMyAdmin links are not supported. Plesk's mysql security works differently, and by design, your username no longer has access to every database on your account. You're supposed to access them individually through Plesk. For applications to access databases, you need to create and assign users just like you did back on cPanel, then give the application the username and password you created.

Lets see if Krydos has any input on these issues.

Should be fixed, might take 2 hours again. We disabled a bunch of domains a while back that weren't hosted here any longer to improve server performance. It's kind of weird it didn't re-enable when I changed it though. I guess it's a rename instead of delete and create new, so it kept the disabled status?

Ack. I completely missed the fact phradham was an old Johnny account because he said it was moved to Plesk and didn't bother to go looking for it (I guess he meant he finally got reinvited...).

Domain changed. It can take up to 2 hours to take effect. You'll need to either set your name servers to ns1.heliohost.org and ns2.heliohost.org, or create an A record pointed to the IP address shown in Plesk (click your domain in Plesk, the IPs are shown at the bottom below all of the options).

Krydos may want to look at the password issue for the unarchived account, so I'll escalate this to him as well.

You can log in at https://heliohost.org/login/ You may be able to get a backup of the cpanel account here: https://heliohost.org/backup/ however it’ll be from July 2021. If you need something newer or the backup isn’t found, Krydos would need to generate it for you.

It's working for me. When I visit either of those links I see a WordPress login. If you just had the domain created right before installing it, I wonder if you hadn't waited for it to finish setting up...

Plesk's mysql security works differently, so this is normal. Your username is no longer a master account with full access to all of your databases like it was in cpanel. You have to create the DB users and assign them to the DBs they need access to. For best security, you should access PMA through Plesk and just delete that installation you have on your website as it's no longer necessary with a working control panel. As for the not found errors, if the files exist, those are likely related to your htaccess file. If you renamed it to disable it (or if it needs things Plesk doesn't support), the site could break. For example if the site used rewrite rules to generate URLs, those rewritten URLs won't be valid with the htaccess missing.

This is by design. Plesk Tommy is completely full at the moment since it has fewer resources due to sharing with the old cPanel Tommy server, and as a result we couldn't fit all of the accounts from the cPanel Tommy on the plesk Tommy server. We hope to fit more accounts onto Plesk Tommy once we are able to get rid of the old Tommy, but for now we have to put the accounts somewhere, so they're all being sent to Johnny. It is possible that at some point in the future there will be an option to move to Tommy again, but we don't know if or when such will be offered.

First thing's first, which one do you want to keep? You're only allowed to have one account, so the other needs to be deleted. If you want to keep phradham, you should use the password you used for cpanel (we can reset it if you forgot it). If you want dhammadh, Krydos needs to look at it (considering it worked until archived then not after it was unarchived, it makes me think the password didn't restore correctly).

All 4 of those links show the same thing as the picture I posted above...the site works. Since clearing your cache didn't help, it sounds like your ISP (or perhaps the local network if you're at work or university or the like) is caching the site or otherwise doing something weird. Can you try it on a cell phone using the data plan (Wifi turned off) to rule out your ISP?

Please clear your cache. I see this website for the domain Pansani listed above, which appears to be hosted on Johnny:

Krydos can delete your account and send you an invite for a new one