wolstech

No need to change it then. If you ask for additional domains for extra projects, they automatically get their own document root. Your main domain is always ~/httpdocs/ , but extra domains would use a folder named after the domain instead of httpdocs (e.g. ~/extradomain.helioho.st/ ), so they're automatically separate. Changing the docroot was a common request back in the cPanel days because cPanel used to put the addon domain roots inside the main domain's root, but Plesk doesn't do that.

This is the software in question: https://codecanyon.net/item/max-profit-online-investment-platform/26164846 Worth noting that even if he had paid for it, he can't run it here because we no longer allow investments or other financial offerings as of our June 25, 2025 TOS update. (Our data center does not meet industry data security standards for handling or storing this sort of information).

Tons of other processes are still causing load even when Apache is stopped, such as: Plesk (which runs tons of stuff in the background), MySQL, PostgreSQL, mail server, system tasks, NodeJS apps and long-running Python apps on people's accounts, cron jobs, etc. Apache itself is only a fraction of the load, and while yes, load will drop when Apache stops because there's no requests (which means things like PHP and CGI stuff will not execute), it doesn't make much difference. The real determining factor is the number of vhosts in the config. Apache takes its sweet old time loading all those. It's worth noting that Johnny is really overcrowded for a Plesk server. Typical Plesk servers are meant to handle ~400 accounts per server. We have 991 on Johnny right now, and it was over 1000 a few days ago (several accounts archived and caused it to drop). We've actually been told by the software companies (both Plesk and cPanel before it) that they were amazed at what we've done with their products. Morty is much faster than Johnny for these restarts. There's substantially fewer users, fewer vhosts, and its running on hardware that's both newer and faster than what Johnny is on. It's been a while since I checked the numbers, but I remember Johnny's Apache restarts were like 5-10 minutes while Morty took just 9 seconds... TL;DR: Server has a lot more running than Apache, and is overcrowded.

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

Just the monitor not catching it. The monitor checks on an interval, and if happens to occur between checks, it simply never shows on the monitor. Server load also affects the speed at which it restarts, so during times of low load, the restart completes faster, resulting in shorter error duration and an increased likelihood of it being missed by the monitor. And finally, the 2 hours thing isn't a hard 2 hours. It's at least 2 hours between restarts. There's times where that restart is closer to 3 hours because the server delays maintenance tasks if it's experiencing high load. The background process we developed to handle routine server maintenance (including apache restarts) is designed to only do its work when server load is below a set threshold.

It's not crashing. We're forcing it to restart intentionally. The errors occur because nginx is used in front of Apache as a proxy, and it spits out that error when it can't reach apache.

Yes, it does take that long in our case, because there's several thousand domains hosted on one server, which means a ton of Apache vhosts. Johnny and Tommy each have about 5500 vhosts (a typical domain uses 2 vhosts, one for plain HTTP and one for HTTPS). Your typical VPS is probably going to have like 10-20 vhosts. An instance of apache on your home computer for localhost development likely has 1 or 2. Then there's the fact that the servers are also quite busy, so load is not always the lowest...

DKIM, SPF, and DMARC have been set up for the domain littlebosses.co.ke. 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.

Please see https://wiki.helionet.org/502_Bad_Gateway for information on this error.

Your domains are working for me. Where are you seeing this error?

It's not multiple people signing into the same account. It's multiple accounts being signed into by what appears to be the same person. Odds are since you mention you're doing this at school, someone else at your school also has an account and it's causing this. I'll just exclude your account from this detection because of the shared network. If these are being used for educational purposes and other students also want to have one, they're welcome to contact us or sign up with a school-provided email address and we can also exclude them. Also, i agree that these multiple accounts suspensions are annoying and cause a poor experience (and quite frankly I hate dealing with them), but we also don't have the server capacity to allow people to have more than one account and still have decent uptime. It's not fair to turn away people who have 0 accounts because other people Took more than their fair share of resources by having more than 1. Unsuspended.

The difference in the HTTP vs HTTPS protocols is security. HTTP (no s) sends data across the internet in the clear. Anyone with some technical knowledge can see what is being sent. HTTPS is a version of HTTP that encrypts the data during transfer so it cannot be easily sniffed by a third party. For nearly all things today, HTTPS is the preferred protocol.

It's for multiple accounts again. Either you have 2 Plesk accounts, or someone else is using the same network/PC as you to access an account with us. Do you know who else might be using our services from the same network/PC (family members are a common cause, as are accessing it from places like a school network)? If so, what are their usernames? (Note that your forum account doesn't matter, it's the Plesk account that you cannot have more than one of).

Let’s see what Krydos has to say.

The mailbox is not actually unlimited. The maximum size of a mailbox should be the same as the remaining free space on your hosting account (unless you manually cap the mailbox at a lower amount). The postmaster email used up a few KB at most, so just fit in there. If you have plenty of free space and you received this email anyway, let me know and I'll have Krydos look at it. As for the IMAP issue, odds are it's because your mail client is expecting the spam folder to be called something else, or is not configured to sync things other than inbox and sent. I've seen this happen before with the trash folder as well, for example some clients like older outlook would expect trash to be called "deleted items".