Krydos

Tommy server load is still a little higher than it should be, but I installed wordpress on my Tommy account, and ran a speed test. It says the fully loaded time is 1.0s which isn't too bad for wordpress. But like everyone has said the best way to fix wordpress being slow is to not use wordpress at all. https://gtmetrix.com/reports/krydos.heliohost.org/HnPasLcD

.htaccess files in directories can affect subdirectories. For instance if you have a file /home/sohamb03/public_html/.htaccess the rules in it can apply to /home/sohamb03/public_html/panthergroup.eu.org/ as well. So try deleting or renaming your .htaccess on that addon domain AND any .htaccess in directories below it as well.

Yeah, you're right. There was a typo in that database name. It should work now.

It looks like our suspension script might be a little too sensitive. I'm not seeing a full 50 emails sent. I have adjusted some settings that should help. Thanks for the feedback.

There you go https://citisnet.heliohost.org/test.jsp and https://citisnet.heliohost.org/cbook/

There you go https://fjmduran.heliohost.org/BackHelioHost/

Done. You should now be able to log in and your website should start working within 2 hours.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

When was your account suspended?

Remote access enabled.

4.91 is the latest currently available through apt. You could install the latest version by compiling it from source, but that would likely break things worse than they already are. I didn't do anything with spamassassin. It's been installed since before you logged in to the vps for the first time. I haven't done anything to your VPS since I last posted that I rebooted it for you. Yes, I really think this is the main issue, and it doesn't cost you anything to try it. I'm pretty sure it went smoothly because of the extra memory. It might be that gmail is blocking your emails because it thinks they're spam. You mentioned that your domain changed from stockdiv.com back to vps13 so maybe that's why google doesn't like this vps anymore. Can you send another email to https://www.mail-tester.com/ and post the result link?

Done. You should now be able to log in and your website should start working within 2 hours.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

I rebooted your VPS and everything seems to be working. Let me know if the mail issue still happens.

I specifically asked you if the load was because you were undeploying and redeploying and you said the load happened before you did that...

Marked solved. Glad everything is working for you now.

According to https://forum.vestacp.com/viewtopic.php?t=12995 it looks like your server just needs a reboot to make exim start working right again. Want me to do that for you?

Thank you for making this a post rather than a PM. I always forget to check my PMs, and I've never even attempted to provide support through PMs before you. I'm not ignoring you, I've just been really busy lately with work and real life. You say you're worried about making HelioHost look bad with all of your VPS issues, but there are a couple things here. First, HelioHost has always been completely open and transparent about our strengths AND our weaknesses. Most businesses try to hide everything behind ticket systems where no one can see anyone else's problems. The main problem with that is it increases the workload for the staff because they have to deal with the same problems over and over, where on a forums like we have here anyone can search for their issue and see how other resolved it in the past. Not only does this make things easier for our staff, but it also gives new volunteers a chance to help out, and become promoted to admin themselves. We recently promoted Flazepe for this exact thing. He helped out a lot without asking anything in return, and we gave him a promotion so he can help out even more. Even I was just a regular user looking for customer support a long time ago. I liked the concept that I just outlined, and started helping out myself. Maybe Flazepe will have my job some day. Who knows? Anyways, my point is if someone else has this same sort of VPS issue in the future they can read this thread to see things to try. Second, you're not making HelioHost VPS look bad because you're the only person, out of about 20 right now, that is having these sorts of load issues. It's much more likely it's a software issue than it is any kind of "hardware" issue that would indicate HelioVPS are poor quality. Don't worry about making us look bad by posting publicly. In your screenshots it looks like vesta is still doing updates on its own, which is odd because I unchecked the box for auto-updates, and it appears to still be disabled. You can see it called v-update-sys-rrd. We discussed this before you even bought the VPS. You asked basically, "How will we know if my VPS needs more memory?" This here, exactly what is happening with the load spikes, is what lack of memory looks like. My offer stands: I'll give you double memory for a week for free. If the load spikes get better or go away completely you can make the decision to continue paying for the extra memory after that. I really think this is the best solution. I'm checking on your mail issues now. I'll edit/post again when I have information.

@robev, have you tried removing the domain, and re-adding it yet? If so please let me know and I'll take a look at it.

That's just a shell script to install https://github.com/tpruvot/cpuminer-multi @wolstech, will that mine turtle?

It's working for me https://stockdiv.com/Stockdiv/Stockdiv

I'm glad it's working for you now.

Remote access enabled.

Rather than letting tomcat create the file you could try creating an empty file yourself that tomcat has permissions to write to.

They actually didn't stop; they're just that far behind on everyone else. The way they work is they process whoever is the furthest behind next. I ran logs on your account manually. That puts your account at the bottom of the list to have logs run next, and the server was trying to get caught up on the thousands of other accounts first before running logs on your account again. I once again ran logs manually on your account.