Krydos

15 minutes after the reboot you website is loading a little faster, but you are already down to 90 free MB of memory, 400 MB of swap used, and your load is around 2.00. I'm going to increase you to 2 GB memory.

Your subscription has been canceled, and you won't be billed again. Thanks for using our VPS service.

Once the donation is verified we'll get you on Tommy. Since this is the first time anyone has donated Microsoft points we have no idea how long it will take to verify.

Your VPS has 58 MB of free memory, and 100 MB of free swap. The load was about 10. In order to have a fast website we need the load to be 0.50 or less. Preferably even lower than that, 0 MB of used swap, and 500-800 MB of free memory to handle spikes. Long story short, you need more memory. I rebooted your VPS to see if that helps, but if the load spikes back up super high again we'll need to try increasing the memory. You can check the load yourself with the top command via SSH.

root@control [~]# dig +short TXT @ns1.heliohost.org stichtingdecitadel.nl "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 include:smtp.spf.ziggo.nl ~all" root@control [~]# dig +short TXT @ns2.heliohost.org stichtingdecitadel.nl "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 include:smtp.spf.ziggo.nl ~all"

DKIM, SPF, and DMARC have been set up for the domain stichtingdecitadel.nl. We recommend sending a test 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. Plesk frequently produces DKIM values that are too long to fit on a single TXT record. In those cases you must break the TXT record into 2 pieces. You can take a look at the DNS zone now if you want to see how it's done.

Yes.

You might want to re-upload your files from a backup that you know is clean. root@vps109:/home/gzmo/web/gzmoperformance.co.uk/public_html# grep -i 'hacked' * -R wp-content/plugins/592c20f10b444977882b7d2b6d18765c/Green.php: echo "<center>Hacked BY MR.GREEN</center><br> wp-includes/ID3/module.audio-video.quicktime.php: $QuicktimeSTIKLookup[5] = 'Whacked Bookmark'; wp-includes/ID3/module.audio-video.riff.php: MDVD Alex MicroDVD Video (hacked MS MPEG-4) (www.tiasoft.de) It appears you really have been hacked. Since it was redirecting to the install page yesterday, I'm guessing this Mr. Green bot just finished the Wordpress install for you and uploaded some backdoor plugins. I would delete everything in public_html and start over.

That sounds like a great plan. Your account has been unsuspended. Keep an eye on https://heliohost.org/dashboard/load/ and let us know if you need help with anything.

The daily limit of 250 was not reached, but the default 10 emails per hour limit was exceeded. I have changed the limit for bsf@jchang.heliohost.org to 250 per hour, but keep in mind if you create any new email addresses they will have the default 10 per hour limit unless you request us to change them as well.

Which email address is sending the emails?

Oh, another thing you can do prior to the DNS cache expiring is you can use your hosts file to force your browser to go to the right IP, and you can start installing Wordpress before anyone else can even see the site.

It's working for me root@control [~]# curl --silent -v -H 'Host: gzmoperformance.co.uk' --insecure https://65.19.154.75/ * Trying 65.19.154.75:443... * Connected to 65.19.154.75 (65.19.154.75) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * CAfile: /etc/pki/tls/certs/ca-bundle.crt ... > GET / HTTP/2 > Host: gzmoperformance.co.uk > user-agent: curl/7.76.1 > accept: */* > ... < HTTP/2 302 < server: nginx < date: Sat, 24 Aug 2024 22:55:22 GMT < content-type: text/html; charset=UTF-8 < content-length: 0 < location: https://gzmoperformance.co.uk/wp-admin/install.php < expires: Wed, 11 Jan 1984 05:00:00 GMT < cache-control: no-cache, must-revalidate, max-age=0 < x-redirect-by: WordPress < strict-transport-security: max-age=31536000; Your server is responding on that domain and it's redirecting to /wp-admin/install.php. You just need to be patient like I said and wait for the DNS cache to expire. If you don't want to be patient, I suppose you could start driving to every DNS server in the world, get console access somehow, and clear the cache manually. Seems easier to just wait though.

The first problem I see is you have the NS records wrong. Our nameservers are ns1.heliohost.org and ns2.heliohost.org (not heliohost.us). The second problem I see is you never requested that domain to be added to our nameservers. With our hosting you can use external DNS, one popular free option is Cloudflare, or our nameservers, but if you want to use our nameservers you need to let us know that you're using them so we can create the domain DNS zone for you. I have created the DNS zone now pointed at your VPS, but until you fix the NS records on your registrar it won't work. After changing the NS records your domain could continue not working right for 2 to 48 hours depending on how long the wrong values stay cached. Give it at least 2 hours and if it's still not working we can take another look.

The account gzmo786 isn't a Hestia account, it's an SSH account. You have to create accounts through Hestia for them to be Hestia accounts, and gzmo786 was created when the OS was installed which was before Hestia was installed. What is the domain? What is the TLD of this domain? .com, .net, .org, .store?

WSGI control access has been enabled on the domain monnandre.heliohost.us. To restart your Flask app and load new code changes in simply edit /home/monnandre.heliohost.us/httpdocs/bs_credentials/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.

Remote access enabled. host=65.19.154.94 port=5432 username=fudobi_admin_bierhaus dbname=fudobi_bierhaus password=<set in Plesk>

Thanks for the donation. We really appreciate it.

Closing due to inactivity.

Installed. You can see the current list of installed modules and their versions on Johnny's Python 3.12 with this link https://krydos2.heliohost.org/pyinfo/info3.12.py

It looks like you have 3 Wordpress installs on your account. Even 1 Wordpress install is enough to easily get some people suspended, so 3 is definitely not recommended. Wordpress is so bloated and causes so much load that we have a wiki page dedicated to how bad it is located at https://wiki.helionet.org/misc/wordpress In the last month you've had 181.1 MB of bandwidth usage, which isn't much, but given how inefficient Wordpress is you still got suspended. We have several websites that push 100 GB of bandwidth every month and don't even come close to getting suspended because they are running much better software. I took a look at your access logs, and found that the casa- domain has 16,333 page hits from the IP 51.79.151.106 in the last month. Clearly that is no human. Some options for you: Move your Wordpress sites to a VPS which start at $4 per month so your load doesn't slow down other users. Reset your account back to the default empty state to clean up any potentially hacked or insecure Wordpress installs. Delete the Wordpress installs yourself and switch to better software. Convert your sites to static Wordpress sites, which are much faster and cause much less load. Let us know how you plan to fix your high load.

Your daily email sending limit has been increased to 250.

Our forums and our main website will be down for a bit for scheduled maintenance. We expect the downtime to only last 30-60 minutes. During the maintenance you won't be able to access heliohost.org or helionet.org. Websites on Johnny or Tommy plans won't be affected. If you need to login during the downtime you can do so directly at johnny.heliohost.org or tommy2.heliohost.org depending on which server you are on.

Your storage space has been upgraded to 6000 MB. Thanks for the donation.

You were suspended for high load on 2024-05-28 and then again for high load on 2024-06-23 and then high load again on 2024-08-14 What have you done so far to reduce your load?