wolstech

Nothing's finalized yet, but I will say your post here did come up in a discussion in a staff channel last night about possibly trying to improve these review numbers We were literally discussing this yesterday, so this post is rather timely. And yeah, reviews are always negative biased. You never hear from the 1000s of happy users, but you're certain to hear from the guy who got banned for abuse. I know a bunch of our old reviews are literally from people whining that they weren't allowed to use our service for illegal activity. At least one (not sure if on TP or elsewhere) was from a guy who was so disrespectful and arrogant that he got permanently banned for lying to staff after he got caught with multiple accounts and refused to admit wrongdoing, then tried to claim nonsense like we were controlled by hackers and such when he got banned (we removed the hacker nonsense, but here's the original support case that caused his ban). We routinely use him as an example of what not to do here.

I believe that's supposed be megabytes but is an older version of the chart that doesn't show usage beyond 100. The version of this chart that admins work with shows the memory usage in megabytes. This is your account as seen from my side. That spike peeked around 150MB. I asked about the charts differing in a staff channel for you. For a simple reference, if the app will run 24/7, keep your app's memory below ~70MB and you should be fine. 70MB continuous for 24 hours converts to 98.4GB, which is basically right at the 100GB cumulative daily cap.

Passenger error logs are in the system /tmp folder I believe. You can't access that yourself. As for the permission error with htaccess, I'll have to take a look. I'll see if I can post a log and check those permissions when I get a minute.

Account wxxle has been unsuspended. I'll let Krydos decide on whether the other account can be kept as well.

Merged since these are the same person. You're suspended for having more than one account. You're only allowed to have one account. Our system indicates that both of these accounts were created and are being used by the same person. Also, managing an account on behalf of another person is the same thing as having two accounts and is prohibited. Are you able to prove there are actually two separate people here?

ModuleNotFoundError: No module named 'djangotest' Code issue? The full log including traceback is visible in Plesk in the logs section

That error means remote access isn't set up, so it either was removed for some reason, or perhaps it was never configured for IPv6 (I believe that's been an issue in the past). Krydos can fix it.

Yes we usually do recommend resetting these legacy accounts. They have tons of weird issues (among the notable ones: Options directives not working in .htaccess, directory listings not being supported, and I've seen other strange behaviors at times like custom error pages being ignored). The reset will remove all of your data as well, so you'll need a backup and have to set everything up again. Do you want me to reset your account?

Code is cached yes. See https://wiki.helionet.org/tutorials/django/django-on-heliohost It can take up to 2 hours to take effect after you push changes. If you're using WSGI, it's possible to request WSGI control access, which will let you manually clear the cache by editing the dispatch.wsgi file (you can literally just add a space or something, the timestamp changing triggers it). https://wiki.helionet.org/tutorials/django/django-on-heliohost#wsgi-uses-server-side-caching

Krydos can assist with this.

Please check your PMs for information regarding your Lily account.

You're suspended for high load because your Node application ran away. Node is infamous for using too much memory, and is one of the fastest ways to get suspended for load. Off the shelf applications that are designed to run continuously will nearly always result in a suspension. One way to reduce memory is to design an app that can run through Passenger. An example of such an app and best practices are on our Wiki: https://wiki.helionet.org/tutorials/node.js Please fix the issue quickly. Unsuspended. It may take a few minutes to work again.

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.