wolstech

It’s not yet implemented. What domains do you need created? Krydos can create them for you.

It sounds like either broken software, or software that's incompatible with our server, especially if 3 separate install attempts all led to the same bad result. Unfortunately we can't really assist with troubleshooting the actual software as none of us are familiar with it. Have you asked on their forum about why you'd get this error when there's no prior installation and the system requirements are met? Specify when you start that you've already reinstalled 3 times and every installation had this error. It may be a bug they need to fix, or they may be able to tell you how to add the missing data.

You're the first to report one of these failing. Krydos will be the done to troubleshoot the internals of the registration system, but I do see that your invite was filled out in the system. As you'd imagine, the account never created, and oddly I don't see an entry in the account log either (normally there'd be an error that explains why it failed, it's as if the server never attempted it, or at least never got far enough that it could log the failure if it did). When did this error occur? Was it at the progress bar screen? Or perhaps immediately after you agreed to the terms of service?

Krydos has to change this. We don't allow users to change PHP settings using .htaccess for security reasons, which is why you're getting the 500 error. What version of PHP are you using?

We can take crypto for the wait list...BTC, LTC, ETH, ZEC, and BAT are all accepted. You'll need to post the transaction ID of the payment and Krydos can link it. XMR or Aeon can be accepted as well if you prefer privacy coins, though it will take several days to verify if you choose those since I have to boot up an old server and run a wallet sync to verify that (those wallets live on a turned-off VM that dates back to when we offered a donate-by-mining app called HelioMine 4 years ago, that program has since been discontinued due to lack of uptake). The 5 up top go directly to an exchange and convert to cash when donated, but the privacy coins do not. Please do not donate using Loki or TRTL. They're obsolete and need to be removed.

Unblocked. It was for failed IMAP logins...you have a mail client configured incorrectly somewhere.

Someone posted spam in here. I flagged the spam, but it apparently didn't unmark it as new... Since it's unlikely he still needs help after 7 months, locking.

For any domain you own (looks like a .tk), you can just change your name servers at your registrar if you wish to host the domain with a different hosting company. As soon as you change the name servers away from ours (and DNS propagates), our service will have no effect on your domain anymore. Please keep in mind that your .tk domain may also have been cancelled by Freenom (they're infamous for doing that, usually to extort money from the user). If that happens, you would need to see if you can register it again over there. Please note that your account's free subdomain lagrimasyrisas.heliohost.org cannot be taken to a different web host

We know, we've tried. In fact, we've actually spoken to an actual person at Google and they've refused to fix it. It's because we often deal with hacked accounts (and when it was possible to create accounts, abusive users) who send phishing email. In fact, this is enough of an issue that we have a News post telling people not to use our services with Gmail (https://www.helionet.org/index/topic/53714-problems-with-gmail/) and we even implemented Discord notifications for stuff like invites because of it (https://www.helionet.org/index/topic/53746-discord-notifications/)

The port number needs to be changed to 1373.

This is by design. Unlike the cPanel days, with Plesk your home folder has the name of the main domain instead of the username. I hate this too as changing the main domain breaks everything now. That said, because of this design, every additional domain you have will have a path that appears to be "inside" your main domain (though it's not, that second juliengarrigue.com folder, which is inside your home folder of the same name, is probably the actual docroot of your main domain). The path Moodle is showing is just the full server path of that 900m folder you see in file manager.

You need to change the hostname from tommy.heliohost.org to tommy2.heliohost.org.

You can create a filter that does that. Condition of "To" = support@heliohost.org, action of "Never send it to spam" should prevent the spam filter from flagging pretty much anything, granted this means actual spam will also make it to the forum.

To others reading: Note that balloons method doesn't keep the mail from being sent, it just tells everyone that there are no authorized sending servers for your domain, and as such they should not accept any mail that claims to be from your domain.

The script that posts the support emails to the forum has a history of getting stuck too.

You will get put on the ETA list, but you will not be given an account until you reach the front of the line.

Django is not available at the moment on the shared hosting. It's on the to do list though. If he's a VPS customer, the best way to get support for the VPS is to reply to the welcome email. That goes directly to the VPS team, whereas posting on the forum means you'll likely need to wait for Krydos to see it. That said, if you are a VPS user, a common choice for a control panel is hestia since it's free. Plesk on a VPS is I think $11/month extra to cover its license (Krydos can confirm), and I'm not sure we would even offer cpanel considering what they did to us. Obviously none of this applies to shared hosting where you get access to the user half of Plesk as part of your account.

Do you have a license for it? Plesk as a program isn't free. If you're looking to use Plesk, you'd need to either be a user on our shared servers when that becomes available for new accounts, or you'd need to buy your own copy of it to run your own server. (This does beg the question of whether our license would allow this since it would technically be running on an HH server...even if it's a dedicated/single user VPS...but it is not what they intended when they gave us our license). If you just want a control panel on your VPS, Hestia is a common free choice for VPS users.

I completely forgot about that being added...

There is no VPS Dashboard that I’m aware of. Support and modifications for VPS are best handled by replying to the welcome email you received. One of our two admins who handle VPSes will respond to you. To administer the VPS, you’d connect either via SSH (Linux) or RDP (Windows) using the credentials and IP in the welcome email.

I mentioned this on the first page: Google has been this way for years and old Tommy had the same issue. It very often (though oddly not always) rejects mail that comes from Gmail and forwards through a third party server back to gmail. I even asked Google's enterprise support at one point while I was on with them for a system issue at work (I have access to proper phone support for Google through my full time job due to our Workspace license). I asked sometime in 2016 or 2017 and was told the behavior is by design. Your easiest solution is to just set your forwarder to send the mail to a non-Gmail account. Google is the only provider that does this that I know of.

Krydos may be able to assist with a backup.

Due to federal law, HelioHost is unable to provide services to users who reside in the country of Iran.

Did you just move your account within the past 24 hours? I'm getting different DNS responses depending on what DNS server I use. My home internet's Comcast's DNS as well as Cloudflare DNS are returning old Tommy's IP for me still, but Google and our own ns1 and ns2 have new Tommy's IP. It looks like incomplete propagation. If Lets Encrypt gets served the old IP, it's going to hit the old cPanel server and not find the challenge file... Krydos can delete the unused domain for you.

If that's enabled, you should be able to connect to tommy2.heliohost.org with a mysql client on port 3306 and log in with that user unless there's a step I'm missing...is it not working for you?