New Topics

I'm not sure what you mean by "fully attached". In the settings we have, either a domain is not added to your account, or it is added to your account. There is no partial or full setting. I've now updated your account with the new requested main (primary) domain. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Changing_Your_Main_Domain#Custom_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache Since there is a risk of data loss when main domains are changed, I made a full account backup for you before I made the changes, in case you need any files from the old domain. You can download the backup here: https://heliohost.org/backup If you're not sure how to extract the backup files, please follow our how-to guide here: https://wiki.helionet.org/Account_Backups

Hi, Thanks for your reply. I was trying to sign in to my support@almhdy.sd account using the Gmail app, and it failed. That’s why I saw the Dovecot error appear on the Plesk panel. I understand that users don’t have the ability to restart Dovecot, so I agree it’s unusual for me to see it there. Regarding DKIM/SPF/DMARC — I checked using Mail-Tester, and it scored 10/10: https://www.mail-tester.com/test-dk68k2c7h So it looks like the authentication is working fine. Thanks for confirming — everything seems to be working now. Best regards, Elmahdi Abdullah

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).

...duplicates of what? I only see two other threads made by you.

Domain added. it can take up to 2 hours to start working.

Do you still need this database?

I've added those subdomains to your account for you. Please note that it may take up to 2 hours for the changes to take effect. If after a full 2 hours they don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

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.

Your initial post was made in the Contact HelioNet section, which is not for HelioHost support requests. I've now moved this thread to the right section: HelioHost Customer Service which is routinely monitored by the volunteer staff. I didn't notice an error when I checked your site. I see you haven't replaced the default Plesk index page. Is there a specific URL that the 504s are happening on? If you're getting 504s on Johnny, I'd recommend checking your account error logs which may give more insight about what's happening. If there's something you don't understand in the logs, post it here and we can have a look and try to help.

The account msbsurfi is being moved from Johnny to Tommy.

Thank you so much for updating my main domain and creating a backup beforehand—I really appreciate your help and care. I’ll follow the DNS instructions and wait for the changes to take effect. Your free hosting service makes a huge difference for students and developers like me.

Looking at the time of your post, this specific error was likely because MariaDB was restarting. It usually happens once a day, around the time you posted. Users on the Johnny server seem to notice it more, so if it's too disruptive you could choose to move your account to Tommy or Morty. To read more about the error and the account move options available, please see our Wiki page: https://wiki.helionet.org/500_Database_Error

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.

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.

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

Alright, it works now, thanks!

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.

Hello! Just so you know, you could have asked for the other domain to be removed and for this one to be added in the same thread. It doesn't really matter either way, but one post might have been easier for you. 🙂 I've added that domain to your account for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, please see the steps provided on our Wiki to either set NS records pointed at the HelioHost nameservers, or create A/AAAA records and point them to your server's IPv4/IPv6 address: https://wiki.helionet.org/Addon_Domains#Custom_Addon_Domains If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

I've removed that domain from your account. Please note there is a risk of data loss when domains are removed, since the folder for the domain inside Plesk will be deleted. I made a full account backup for you before I removed the domain, in case you need any of the old files. You can download the backup here: https://heliohost.org/backup If you're not sure how to extract the backup files, please follow our how-to guide here: https://wiki.helionet.org/Account_Backups

It's just not supported. Plesk doesn't officially have the listings enabled by default, so we made changes to have it do that (it was the same behavior our old cPanel servers had, we were tired of support tickets to explain the 403 error that Plesk showed by default, users preferred it and often asked for them to be enabled, and it often makes abuse stand out since they wouldn't hide the listing and leave files like "script phising.zip" in their root...yes that was a real file we found). Specifically, we forced it in the Apache config. Apache doesn't always let you override that option for some reason (the Options line in general doesn't very work well on Plesk). The easiest way to accomplish this on our service is to just put an empty index.html in the folder...

Domain changed, it'll take effect in about half an hour. Also, it looks like you have two accounts. If that's the case, please note that you're only allowed to have one account per our terms of service.

Domains added. Please be sure to configure DNS for them, either by using our name servers (ns1.heliohost.org and ns2.heliohost.org) or by setting A and AAAA records on external DNS pointed to the IPs shown in Plesk. Domains can take up to 2 hours to start working. Please keep in mind that there is a limit of 10 domains total, you're using 9. Also, as a reminder, users are limited to one account between Johnny and Tommy. If you need more than 10 domains, or need a second account for any other reason, the additional accounts must be on Morty.

If it's not the official font, it should be. I thought it was Mahameru at first, but the t in Host wasn't right. Then I thought it was Wind Doomsday, but that wasn't quite right either.