wolstech

Marking solved because user has deleted their account.

Several of these domains such as api.helioho.st and dev.helioho.st already belong to other users. The helioho.st domain is shared by thousands of users, so common names like this aren't going to be available on it. Is it OK if we put these domains underneath the texu one instead (e.g. api.texu.helioho.st, files.texu.helioho.st, etc.)? And no, since you'll be at 10 once these are added, you won't have any slots left to add subdomains under them.

Your Lily account has been cancelled. You can cancel Morty here: https://heliohost.org/dashboard/delete/

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

Domains require a suffix. Do you want it to be latelierdutraitbrule.helioho.st?

What is your hosting account's username? (There's no account matching your forum email or username.)

That domain is working fine for me: https://paul70.helioho.st/

Your account is suspended for copyright infringement.

This is your issue. Nonstandard outbound ports are blocked. Are you able to change the remote end's port to something standard (like 5432), or move the database to a server where a normal port can be used? If not, I can escalate this to see if the port in question can be opened.

Were you by chance watching Dexter on the website "xcrow.cc"? If so, the website has been taken down for copyright infringement.

That feature is only available to Morty users.

Neat. Glad to see you got it working

Where are you seeing the dovecot error? Users don't have the ability to restart that, so kind of a weird one for you to see. As for DKIM/SPF: DKIM, SPF, and DMARC have been set up for the domain almhdy.sd. 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 sort of traffic is basically normal for any website that's been around for more than a few weeks. It's almost entirely malicious bots that are searching for things like a vulnerable Wordpress installation to break into or configuration files with database credentials so they can steal your data. The nginx errors are usually because the server is overloaded. That's pretty normal for Johnny when server load is up. Apache restarts can also cause these. They're less of an issue on Tommy and nonexistent on Morty. We generally just advise users to block unwanted traffic like this in .htaccess if they are causing load issues, though in your case you said they're hitting nonexistent files and getting 404 errors, which cause so little load that you likely won't even see it register on the load chart. We do not have an edge firewall or similar (we can't afford one due to our funding structure), though the server itself has a software firewall that we've used in severe cases to address an account under attack. If you're would like, you can also file an abuse report with the owners of the incoming IP addresses in question. You'll need to find the company that owns the IP (pretty easy to do by googling it), then follow whatever that company provides for an abuse complaint. I've had success reporting addresses that are based in the US and EU, but you're unlikely to receive responses from hosting companies in countries like Russia and China (if they even accept abuse reports), where this sort of activity is tolerated (if not legal).

It's suspended for multiple accounts. Same person as https://helionet.org/index/topic/66172-solved-hello-administrator-please-help-me-restore-my-account-thank-you/ You're only allowed to have one account.

I just did some research on this, and even ignoring the "Why?" aspect of this, the behavior of .phps (colorized source view) is apparently a function specifically provided by the mod_php module for apache. It's not a function of PHP itself. Since Plesk does not use the apache module, this isn't supported. Your best bet is going to be a solution like Krydos suggested: Write a PHP script that displays another script's contents. Once you have that, you can probably be creative with .htaccess rewrite rules to make calls for .phps files redirect to that script with the requested file as a parameter to emulate the behavior.

You probably need to reissue the cert with the webmail option enabled. Once you do that, wait another 2 hours and it should work. In the meantime, you should be able to click advanced and continue anyway to ignore the error and access the webmail.

Domain added. You will need to configure DNS (either by using our name servers ns1.heliohost.org and ns2.heliohost.org or by using A and AAAA records pointed to the IPs shown in Plesk). The domain can take up to 2 hours to function.

It shouldn't disable the setting for SSL/TLS for Mail (this one relates to IMAP/SMTP connections), not sure about the webmail one. I don't think it turns the webmail certificate off, but I would expect that certificate to not renew while the webmail is disabled.

Domain changed. It can take up to 2 hours to finish changing and start working. Please be sure to configure DNS if you have not done so already.

Domain changed. It can take up to 2 hours to finish and start working.

This was done intentionally due to poor performance on Johnny. When this happens, it happens to all accounts on a given server regardless of usage. We don't have a way of knowing which people are actually using it.

This one is a Krydos question.

Unsuspended and web shell deleted. It may take a little while to start working.

Your account has been reset. You'll receive an email shortly with a link to create a new account. Please do not upload or attempt to run a proxy on your account again.