wolstech

This support request is being escalated to our VPS admins.

Escalating to get Hestia installed for you.

Someone probably just did a normal domain add. When we add domains, they automatically get set up as an additional website because our admin tools do not support aliases even though Plesk itself can handle them. The domain codecreature.net has been manually converted to an alias. It can take up to 2 hours to function.

Unsuspended. It may take a few minutes to work again.

You're suspended for signing up with a disposable email address. Per our Terms of Service, disposable email addresses are not allowed. Please provide us a real email address and we will update your account and unsuspend you.

The administrator folder has been discarded and the account unsuspended. Please fix it quickly as the account only has 3MB of space free.

It was already unsuspended here: https://helionet.org/index/topic/65497-hh247916-utf-8qmy_account_is_suspended_e29aa0efb88f/

Support requests have a turnaround time of up to 24 hours for replies. Please do not bump your request unless at least 24 hours have passed, as we work the oldest requests first, and doing so just moves you to the back of the line. I’ll try to take a look at this later tonight when I’m at a computer…

Your account has two problems: Fist, you ran out of disk space. We can either delete something for you, or you can purchase more space. Do you want me to delete something for you to bring the account below 1000MB? If so, what do you want deleted? If you want to buy more space, you can do that here: https://heliohost.org/dashboard/storage/ Second, the main domain's DNS doesn't appear to be set up correctly. It doesn't resolve for me. Since it's on CF, you'll need to fix that yourself before the domain will work (verify that the A and AAAA records are correct).

The account that owns the steamspace.in domain is suspended because the website was compromised and infected with malware. The forum account you're posting from does not match the username or email addresses on that account, so we can't provide any additional support or information. If this is your account, please post from a forum account that shares an email address with the hosting account.

The settings look correct. While not good practice from a security standpoint, does it work if you check the box at the bottom 'Trust any certificate' (which basically tells it to just blindly use whatever certificate is offered by the server without verifying it)? The certificate provided by our server is issued by Lets Encrypt, and its possible Hubspot explicitly chose to not trust LE or our servers because both are a free service. Also, what are you using for a username and password to log into the mail server? It needs to be an email address and associated mailbox password that exists on your Plesk account. Authentication is required for our servers, and it has to specifically be a mailbox you created (you cannot use your heliohost username and password for email). Finally, if unencrypted connections are allowed, try ports 143 (IMAP) and 25 (SMTP)

We don't support using your own domain in the mail server hostname fields for any protocol (IMAP, POP, or SMTP). As has been said earlier, you MUST use johnny.heliohost.org as the mail server name. The domain mail.yieldandco.com is not valid or supported, so expecting TLS to work on it is kind of silly. Can you post a picture of the mail settings in your CRM so we can verify they are correct?

It's because both of those domains had the same document root. This is likely because you have a cPanel migration account (these accounts act really weird when you modify them, my guess is the main domain change broke it). I've separated the two domains, and you'll see a new folder called survisionmagazine.com now. Please place the content for that site in there. Use public_html for the main domain. You'll need to wait up to 2 hours for the changes to take effect.

For others who may find this, please see this wiki article. https://wiki.helionet.org/502_Bad_Gateway

Due to the amount of RAM this feature requires, it would result in a load suspension on Johnny within hours. On Morty there are no load suspensions, but its still so heavy that it instantly causes an overage fee for RAM usage instead. It costs almost $2/month extra just to have it enabled.

1. No 2. 1.1/1.2/1.3. For SMTP, you need to connect on port 465 for TLS support. Use 993 for IMAP. 3. No. We use dovecot. 4. Allowed by default but IPs get blocked if they try to log in incorrectly too many times.

Crappy free hosts disable it as a lazy way to avoid people sending spam. I've never known a paid host that blocked it, and we don't block mail() here even on our free plans. Rather ironically, our experience is that very few legitimate apps actually use phpmailer...most apps use mail(), SimpleMail (which is ultimately a wrapper for mail() ), or some SMTP implementation instead. Mail vs PHPMailer has nothing to do with mail landing in spam, as the resulting emails are identical from both methods. Content, DNS configuration, and domain reputation are the major factors. Mail() doesn't support authentication or encryption because they aren't applicable. It uses the server-wide mail settings in php.ini and doesn't even accept a mail server name. Also, is this AI generated nonsense? We don't appreciate AI generated posts here...they're often inaccurate and could get you banned from the forum for spam.

I think this has happened before...Krydos can exclude it. Escalating.

Change both the outgoing and incoming mail sever settings to johnny.heliohost.org as above and try again. Many programs don't like when you use your domain in the mail server fields because the server identifies itself as johnny.heliohost.org when you connect. Also, (while not the case here) some people use Cloudflare, which can't pass mail connections.

That feature is only available for Morty users.

You wouldn't create an A record pointed to the name servers, you'd make an A record pointed to the IP shown in Plesk (the one ending in .94 in your case). The IPs for a domain can be seen in Plesk at the bottom of the domain below all the options. Note that by using external DNS, some features of our service will not work properly or may require additional configuration. The most notable is that your domains will stop working due to an IP address change if your Morty account were to ever move to Tommy due to nonpayment. (If you use our NS, we just change the records for you and you experience a zero-downtime move). Email service will also not function properly unless you create the additional records on your DNS server to support it (there's an MX record and several TXT records that are required, plus an A record for webmail if you want that).

Correct. Use mydomain.com/landingpage instead. Wildcard certs will technically work on the server if you were to manually generate them (you'll need to use external DNS as well as a third party tool to do this) then upload them to Plesk, but you'll have to do this process manually every 90 days. It's specifically the automatic issuance and renewal of wildcard certs that's not supported, not the certificate itself.

The account niyhi has been unsuspended.

Automatic issuance of Wildcard certs is not supported. That said, the error also makes no sense because both of your domains have an Ipv6 assigned already. Both of your domains have valid certs for HTTPS, and I enabled webmail/mail certs for you (they should fill in automatically next time the server tries to issue certs).

That account is not suspended for inactivity, it's suspended because Wordpress was hacked and your account was compromised. That's pretty typical of WP and is a major reason we don't recommend using it. Because your account is compromised, it will need to be reset to fix the issue, then you'll need to set your site up again. Are you ready to have your account reset?