wolstech

Lily is a weird server...it's the only one we have that does not run Plesk (or anything else for that matter). We have so little demand for Lily that I actually configure it manually for each individual user (and if you can't figure out web.config, I can probably just change the settings in IIS for you if you let me know ). I think we have like 20 accounts on Lily compared to several thousand on the Plesk boxes. There's been talk about converting Lily to Plesk to make it easier to use and eliminate the dependency on the other servers, but we don't have an extra license for Plesk at this time (the 3 we have are allocated to Johnny, Tommy and the upcoming Morty server), and doing so involves a full rebuild, so there is no estimate for when or if this will ever be offered. If you want a Lily account, you can pick either Johnny or Tommy to start, then request Lily here and I'll PM you a username and password for Lily. Your Lily account will appear as a subdomain of your Johnny or Tommy account (i.e. if you pick aaroneus.helioho.st, your lily account will be at lily.aaroneus.helioho.st unless you ask for a different domain).

1. Gmail users can receive our email provided SPF and DKIM are configured for the sending domain, but it will likely end up in their spam folder until they "Not spam" the messages once or twice. 2. Automatic SSL is supported on Plesk servers and is available by request on Lily. Keep in mind that Lily has no control panel, it only has FTP access. Many settings can be changed using the web.config file if you're familiar with IIS. To get a Lily account, you need to have a Plesk account first, and then request the Lily account be added as a second account. The Plesk account's email accounts and database functions can be used with Lily (databases will require you enable remote database access from Lily's IP for them to work).

Krydos has to do this.

Flask should already be present. Krydos can install the module for you.

This account cannot be reset because it was deleted.

It's the same exact thing. The button just isn't implemented on the user side for self service yet. I will have to manually set your domain back to stew.heliohost.org after you finish the reset, as heliohost.org is no longer offered for user domains. During registration just pick something else, then let me know when you're finished setting up the new account so I can set the domain back to stew.heliohost.org. Your account has been reset, please look for an email with a link to complete the process. (It may be in your spam folder).

What version of Python are you using?

Resetting your account completely deletes the account as the first step in the process, including the domains and certificates, so you will need to set those up again. Do you still want to reset your account?

Uncheck the wildcard certificate option and try again. That option is not supported at this time.

It might be easiest to reset your account if its broken. Do you want me to reset it? If so, your existing account will be deleted and an email will be sent with a link to create a new one.

The contents of httpdocs have been deleted and your account has been unsuspended. It may take a few minutes to start working.

C# / .NET will not run on Tommy. Only Lily supports .NET and related technologies because it's the only server running Windows. You can actually have a Johnny + Lily account and you'd still send mail through Tommy using this method. The server you pick for the Plesk account doesn't really matter honestly because it's not even really used. It's only a requirement because back in the cpanel days Lily leaned on those servers for a lot of things. Plesk obviated the need for it for the most part. That said, the main differences nowadays from what was posted then are that the hostname is now tommy2.heliohost.org, and the IP for the SPF record is now 65.19.141.77.

We don’t offer redis service. If it needs that you’ll need to have an external redis server. That said, port 5432 is for Postgres, which has nothing to do with redis…

Are you willing to remove the nulled software from your account and refrain from using such software in the future? If so, let us know when you're ready to remove it and we'll give you 24 hours to clean it up.

Krydos can do this for you.

We currently do not support Java on the free service. It hasn't been offered in 3 years (support was removed when we switched to Plesk), and we have no estimate on when or if it will be offered again. You'll need a VPS to run Java.

You are indeed suspended for having two accounts. Accounts accessed from the same network or computer will get flagged as a TOS violation unless approved in advance. Since you've asked for unsuspension and the other account is still suspended, I'll unsuspend yours. If your friend wants an unsuspension, he'll need to request it separately and have the account reviewed. Unsuspended. This is by design. The only notices that are currently sent are for inactivity suspensions, and we plan to eventually send warnings for load related suspensions as well so users can reduce load to avoid them. For all other reasons, the ban is issued without warning.

I'm guessing you figured it out since you marked your own post solved, but for the others who may find this, that error is not related to DNS at all. Internal server error is usually the software installed on your account being broken. Depending on what you're doing, it could be caused by PHP throwing errors, invalid .htaccess files, malformed CGI scripts (wrong line endings, etc.), incorrect permissions such as Python scripts not given execute, and similar can also cause them.

That account is already active.

Your DNS zones were deleted due to being archived. I've recreated them and they should be working now. Might take some time for DNS to propagate.

Krydos has to do this.

The ability to pay to not go inactive is a feature of the Morty plan that's coming soon. Morty also won't have load suspensions either (price goes up instead). As long as the bill is paid and you don't violate the terms of service, a Morty account will stay up indefinitely. We're hoping to release that plan later this year, but there's a lot of development work needed yet.

I haven't heard anything, but then people do ask for things like module installs on occasion, so the environment is subject to changing. Also, these are in the logs for your account. I'm not exactly sure what would suddenly start causing them, but suspect high load could be to blame as it is a common cause of timeouts. They seem to have started regularly occurring on Feb 4. Krydos would know more about this. 2024-02-11 13:46:07 Error 2001:470:1:1ee::2009 (70007)The timeout specified has expired: AH00574: ap_content_length_filter: apr_bucket_read() failed Apache error 2024-02-11 13:46:07 Error 2001:470:1:1ee::2009 (70007)The timeout specified has expired: AH02550: Failed to flush CGI output to client Apache error 2024-02-11 13:46:07 Error 2001:470:1:1ee::2009 7970#0: *329872 upstream timed out (110: Connection timed out) while reading upstream nginx error

That account is already active.

Krydos can set this up for you.