wolstech

Yeah, the www record was indeed missing. It's been fixed and the cert has issued successfully.

Your account has been reset. You should receive an email shortly with a link to finish the reset process. If you need anything from the old account, a backup can be downloaded from https://heliohost.org/backup/

Sure. Escalating.

Flask cannot be installed on Python 3.9 because it would conflict with the version installed on 3.12.

Added. Please be sure to configure DNS. The domain can take up to 2 hours to work.

Deleted. Thank you for using HelioHost. Please note that our system doesn't store any bank information. All we receive is a transaction number and the amount of your payment from Paypal when you pay, which we use to determine how much you paid and what size account to assign. Paypal stores the actual bank information on their end in your Paypal account, and HelioHost does not have access to that data.

Krydos would need to open this. In the meantime, is it possible to have the remote end reconfigured to be accessible over a port that’s already open like 3306?

Glad to hear its working for you now Please let us know if you need anything else.

Unsuspended. Please fix the issue quickly. Also, I've put deny from all in your .htaccess to keep it offline so it cannot be attacked until you can fix it. Please remove this line once the issue is resolved. If this happens again, another unsuspension might come with the requirement that you eliminate Wordpress.

Your Wordpress install got attacked by bots and basically broke Johnny due to load. This was Johnny's response time while your site was active (the spikes to the top of the chart were the server timing out), and I've also attached a picture of a traffic log. Your site being attacked repeatedly caused intermittent downtime for ~2000 other websites. This is why we say not to use Wordpress. How do you plan to fix this?

We blocked the site intentionally to keep you from being suspended because it was being attacked or otherwise malfunctioning. That cliff is where we disabled your website for you. You were at over 9800 CPU and quickly approaching the limit of 10000. It was either "block the site and keep the account active" or "get suspended for high load". We decided to block the attacked site for you so you could at least keep using the rest of the account. If you want to unblock the site, you can remove the deny from all in your .htaccess file. In many cases we've just blocked bots and such specifically for users, and you would never notice anything, but since your site uses CF, we only see CF's proxy IPs, not where the attack is coming from, and so had to block everything.

Changed. It can take up to 2 hours to take effect.

You'll need a VPS for this. We don't allow users to programmatically add and remove domains on Plesk, and we're certainly not going to constantly change your 10 domains daily.

Please clear your cache. It's working for me.

Account raqbul has been reset. You'll receive an email shortly with a link to click to complete the reset process. Please let us know if you need anything else

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.