wolstech

OK. I think this should be fixed. Your account is a weird one because it's a legacy cPanel account that was recovered from the failed RAID back in July. It will take an hour or so to start working. Your document root is indeed public_html since it's a legacy account, though it shows a July 2024 date which confused me (normally these accounts all have dates prior to July 2021). If it does not work after the next Apache restart, your account will need to be reset in order to fix it. Tthese legacy accounts are well known to have numerous issues that simply aren't worth the time to fix, so resetting them is the fastest way to get them working.

The httpdocs folder should have come with the account (if it was a new or reset account). If it was a migrated account it will be called public_html. If you deleted this folder, an admin has to recreate it since it needs special permissions. I’ll have to take a look at your account when i get a minute to see what’s wrong with it.

Please check your PMs for information regarding your Lily account. Note that your Lily username is lilyaayush instead of the more standard practice of putting a 2 on the end (aayush02) that we normally use because Lily accounts cannot start with "aa" ("aa" and "test" are reserved by the system on Lily).

The domain professionalpetart.com doesn't work because it points to an IP that hasn't been used in months. If the domain doesn't work, it cannot get an SSL certificate either. You need to update the DNS entries for that domain to point to the IP addresses shown in Plesk.

Please check your PMs for information regarding your Lily account.

Not much detail in that one. I was hoping to see the results of the SPF check and DKIM check. Not sure about your client, but in Gmail you can see it by selecting "Show Original" on the menu in the upper right of the email. I'm looking for a section of the header that looks like the example below (this email was sent by a domain on Lily to a Gmail account, so IPs and domains are different): Received-SPF: pass (google.com: domain of no-reply@raxsoft.com designates 65.19.141.70 as permitted sender) client-ip=65.19.141.70; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@raxsoft.com header.s=dkim header.b=NUmfdGLe; spf=pass (google.com: domain of no-reply@raxsoft.com designates 65.19.141.70 as permitted sender) smtp.mailfrom=no-reply@raxsoft.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=raxsoft.com dkim-signature: v=1; a=rsa-sha256; d=raxsoft.com; s=dkim; c=relaxed/relaxed; q=dns/txt; h=From:Reply-To:Subject:Date:Message-ID:To:Content-Type; bh=b9UyF5AzNjAOx3cmnC4c/vBhOcjVjR1QtMOm7KUSqtY=; b=NUmfdGLeKPUCt77s0mxb01xWCUKKiOnVz/WKukgMxDad9mQyFfXbCfGHBw+he50I+1IMbocKFtfTjVYfQsMdGlR2evln+H0T95cKlcwE/kH2k5mtihDlM2Xz4hTR7/GF2h/OKjoDKBACTNhfaUvU9al/wgzzMl4gFYGpwyzwWWs=

DNS is now showing this SPF, which is correct. Plesk does not support DKIM signatures on system emails, so that shouldn't be failing (DKIM signature should be absent). "v=spf1 ip4:65.19.141.66 ip6:2001:470:1:1ee::3 ip4:66.220.18.186 ip6:2001:470:1:1ee::2004 ip4:65.19.154.90 ip6:2001:470:1:1ee::1002 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 include:_spf.google.com ~all" Would you be able to post the entire email header?

It's probably a leftover from the wildcard domain (some parts of the system, especially the Plesk API and non-Plesk components of the system, treat the * as a _ ). If you manually reissue the certificate, it should stop trying to renew this in the future.

Domain added. It can take up to 2 hours to work.

Krydos has to set this up for you.

DKIM, SPF, and DMARC have been set up for the domain platform.biz.id. We recommend sending a test email to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.

It was because the system thinks you have 2 accounts. Unsuspended. I see you're in the Philippines. Are you by chance affiliated with this university? https://www.usls.edu.ph/ If so, do you have a school-provided email address we can assign to the account? We've had a lot of students from that school recently start using our service, and they all got suspended for multiple accounts because our system see them as one person due to the shared school network. We've been unsuspending them upon request.

MTA-STS has been added, wildcard has been removed. It may take 2 hours for the changes to take effect.

Domain added. It can take up to 2 hours to work.

This is because the SPF record is stale at heliohost.org...it references old IPs from before the Tommy/Johnny rebuilds. Thanks for pointing it out. Also, admin@heliohost.org is a real email address, it's just not one that's monitored. Not sure if it these alerts can be easily changed to support or not, though it would make sense so people can reply to submit a ticket if they have questions. Escalating...

Addon domains cannot be converted to a main domain easily. Making an addon domain primary involves removing it entirely, then changing the main domain to it. The process usually results in data loss as the process of removing the addon domain sometimes deletes the addon domain's document root and all of its content. Are you sure you want to do that? It might be easier for you to just disable the free subdomain in Plesk and ignore it. MTA-STS requires a policy file be hosted on your account. I can add the subdomain, but you'll need to provide the policy file yourself as Plesk doesn't offer a way to generate it. I'll hold off on adding this because if I add it now and you still want to go through with the main domain change mentioned above, I'd have to remove it again. Users cannot add their own domains because our DNS system does not talk to Plesk. We use external scripts to handle it at the moment (basically a script that updates multiple systems one after the other). Developing that integration is on our to do list but is low priority due to other projects.

Please check your PMs for information regarding your Lily account.

This VPS has been rebuilt with windows server, please check your email for login information.

OK. Turns out mariadb restarted in the middle of your unarchive and caused it to not see your domains, so the zone never recreated. The missing DNS zone has been created and your site should start working soon

The DNS zone didn't recreate after the account unarchived for some reason...I've asked in a staff channel about why this might have happened. Once I have an answer to that issue, we'll manually create the missing DNS records to get you online

This was handled by PM since this is a Lily user. He purchased VPS113 but picked linux by mistake and needs it rebuilt as Windows Server 2022.

You were suspended for high load. Please be mindful of your CPU and memory usage. You can watch your load here: https://heliohost.org/dashboard/load/ If this happens again, you’ll need to provide us with information on how you plan to fix the issue. Unsuspended. It may take a few minutes to work again.

Unsuspended. It might take a few minutes to start working again. Node is one of the few things you have to be very careful with on here because it consumes exorbitant amounts of memory very easily. Please don't run this app here again. I would suggest looking at the node tutorial on our wiki if you plan to use it. Most pre-built node applications out there are designed to be run on a VPS where you have the entire server to yourself.

It's suspended for high load. Whatever you were running is WAY too heavy on memory. You used your entire day's quota (100GB cumulative use in a 24 hour period) in ~2 hours. How do you plan to fix this so it doesn't happen again?

Your third party DNS provider's servers are broken and aren't propagating records. Since you aren't using our DNS, you'll need to contact your DNS provider (looks to be a service called mydomain.com) for assistance. https://www.whatsmydns.net/#NS/ronvdc.com If you would like to use our DNS instead, please update the NS records for your domains at your registrar to point to ns1.heliohost.org and ns2.heliohost.org and wait 24 hours. EDIT: looks like this may have resolved while I was writing this post. It's showing correctly now. Some of your domains are now resolving on our side again (dutchoutpost for example). Guessing mydomain.com just had an outage or something...