wolstech

If it's a demo, that's fine, but it needs to either be: Clearly marked as a demo meant for testing/fake info (e.g. "FOR DEMONSTRATION ONLY - DO NOT ENTER ANY REAL INFO INTO THIS SITE") if the site is available to the public, OR you can password-protect it so it's only visible to those who are supposed to review the demo. (Note if you decide to use the password options in Plesk to secure it, they can up to take 2 hours to go into effect) Please make one of the changes above (either a clear notice on all pages, or add password protection so it isn't public) within 24 hours. Failure to do so will result in resuspension. Unsuspended. It may take a few minutes to let you log in again, and the domain can take up to 2 hours to start working.

It was suspended specifically because you set a job to run every 5 minutes to start your bot. This is not a recommended or supported way to do this. The bot itself was perfectly fine and caused basically no load...just start it once (manually) and let it run and do its thing. Stop and restart whenever you update the code. It is best practice to not run a script every few minutes to start it over and over, as doing so causes tons of load (using shell commands is load-heavy, so running them repeatedly just wastes your daily CPU allotment, this is one of a few reasons why exec is disabled for PHP via Apache). Please do not do this again. The recommended ways to start and stop a bot can be seen here (this article is for discord but the concepts apply to other Python-based bots as well): https://wiki.helionet.org/Discord_Bot#Starting_and_Stopping_Your_Bot I've deleted the scheduled task and unsuspended you. It may take a few minutes before you can log in again.

From our terms of service: Can you explain how your site complies with this condition? (If it's a demo, it needs to be clearly marked that it is a visual demonstration and does not actually accept money or provide any services).

You're suspended for excessive load caused by overuse/misuse of cronjobs (scheduled tasks). Can you explain why this might be and how you plan to fix it?

See https://helionet.org/index/topic/67256-account-unsuspension/?do=getNewComment

Account rushi1819 has been unsuspended. It may take a few minutes before you can login again, the domains can take up to two hours to start working.

The email is legit, but it comes from trustpilot directly so we don't have any control over the language used in them. They always say purchase, even if it was a donation or even a free user. It's just a request for a review. These have a chance of being sent whenever our system sends an email to you, in your case that review request actually was triggered by the terms of service update.

The fact you posted from the matching forum account with matching email is all we need. Your account is being reset. You'll receive an email when the process completes containing a link to create a new account. If you need any of your old data, it will be available for download at https://heliohost.org/backup/ once the reset finishes.

We have to add it for you. What domain do you want added?

DKIM, SPF, and DMARC have been set up for the domain logospres.heliohost.us. We recommend sending a real email (not just the word "test" or a blank 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.

This issue appears to be resolved now that the protection has been disabled and apache has restarted. Your site is now working.

This is a DNS issue. You have the news.burken.com subdomain pointed to Morty's IP address, but the account is on Tommy. You'll need to correct the A and AAAA records at your DNS provider.

Did you already remove the protection in Plesk and wait a full 2 hours after doing so?

I just changed both upload_max_filesize and post_max_size to 50MB for you since that's what the defaults are on other PHP versions. The changes can take up to 2 hours to take effect.

This should be fixed now. Please let us know if you're still having issues with mail on Johnny.

We are not a domain registrar and cannot accept domain transfers. That said, you can host your domain here by changing your DNS records (use NS records pointed at ns1.heliohost.org and ns2.heliohost.org, or A and AAAA records that can be seen in Plesk) and requesting the domain be added to your account.

Krydos is still working on it. The mail server on Johnny is (was) broken due to missing certificate files. Tommy had this issue a few weeks ago. We'll let you know when its fixed.

The intermittent 502 error is going to be Apache restarting...that's normal for Johnny. As for the 500 error and the mail delays, we're looking into that for you. The 500 error in Roundcube especially appears to be affecting everyone, as I can reproduce it on my test account too.

Krydos can take care of it since he also needs to process the refund. Please keep in mind there is a $0.50 transaction fee for a refund. Escalating.

I'll have Krydos take another look, but considering what was posted in your last topic and the fact the issue returned, it sounds like what you're running might just be too heavy. I'm not sure if there's further reduction possible or not. If not, the permanent fix may require buying an upgrade. I'm not sure if a trial would be possible for the upgrade to see if it would actually fix the issue before buying it. Escalating again to see if any further improvement can be made.

That domain cannot be added because the contents of your account violate the terms of service. Note that this prohibition also includes selling access to IPTV and related services, even if the actual content is hosted elsewhere, becuase IPTV and related services are illegal in the USA where we are located (copyright infringement).

VPS admin would need to check on this for you.

Removed.

Escalating to have this turned off for you.

What username are you trying to use to log in? The account that I think is yours (sharecirclee) is active on Morty on my end, and the website is working fine.