Krydos

Closing due to inactivity.

It's been 9 days with no response so I'm going to free up the reserved memory, void the above upgrade payment link, and close this request as inactive to keep the escalated section tidy. If you would like to try upgrading your VPS again please make a new request with this link https://helionet.org/index/forum/45-customer-service/?do=add

Your domain has been changed back and it should start working in about 13 minutes.

There is nothing we can do to make Gmail accept our emails. Even getting a perfect 10/10 on the mail tester, and even contacting a Google employee they can't do anything about it either. The Gmail spam filter uses algorithms that aren't under direct control by Google employees, and it just does whatever it wants. If the email gets sent to the spam box you can ask your recipients to mark it "not spam" and Gmail will eventually learn that your domain is sending good emails that people actually want to read. Gmail doesn't have any whitelists or blacklists. It just has AI that decides what happens to the email.

You can't actually register username.heliohost.org domains anymore because we had issues with phishing accounts getting our main heliohost.org domain flagged by services that didn't realize that we allowed our users to create subdomains. So when you recreate your account you'll need to pick a temporary username.heliohost.us domain or a username.helioho.st domain. If you'd like your username.heliohost.org back any moderator or higher can change the domain for you. If you'd prefer the new .us or .st domain anyways you can definitely keep it though. Anyways, I have deleted your account and sent you an invite to recreate your account.

The domain has been added to your account.

No one has ever turned DKIM back off after I enabled it for them and set up the DNS so I wasn't aware that the key would change. Furthermore the first 39 characters and the last 7 characters didn't change so I would have had to compare them really closely to make sure all of the 216 characters were correct so it makes sense that it wasn't obvious. Anyways, third try will probably work.

This is so close to being correct too. VMware virtual network devices are never named eth0 though. Generally our VPS use the interface ens160, but I've also seen ens192 depending on the version of VMware that the server is running. The best way to be sure of the interface device is to run the command ip addr

You were so close! Your forgot to set up an IPv6 gateway. The IPv6 address was added correctly, but without the correct gateway it has no idea where to send or receive the data from. The gateway for your IPv6 is 2001:470:1:1ee::1. I finished setting up IPv6 for you, and tested it. One other thing I'd like to mention is it looks like you have SSH set up to only allow connections from certain IP ranges which is a pretty great improvement in the default security, but I added an additional rule to allow SSH connections from HelioHost in case you need support again in the future. We only connect to user's VPS if they ask us to, and there are only currently 2 VPS admins with the security clearance to access your VPS, Yashrs and myself, but we may train more admins in the future as we get more and more VPS to provide support for. You're welcome to remove the firewall rule if you want, and if you need support Yash and I can gain root access in a slower method that requires rebooting your VPS several times, but this firewall rule will save us quite a bit of time if you need help with something. We respect the privacy of our customers and only check things out if there is obvious reason to suspect that the user is violating our terms of service, the VPS has been hacked and the hacker is violating our terms of service, or if the customer requests help with something. Anyways, let us know if you need help with anything else.

Yeah, that's pretty much the conclusion we've arrived at. Accounts that were transferred from cPanel to Plesk are unable to use Options, but accounts that were created directly on Plesk are able to. It's extra perplexing because Options was allowed on cPanel so it's strange that it gets turned off somehow during the transfer. There are 8031 places in the Apache configuration files where the issue could be, and a similar number on Johnny so it makes it difficult to figure out where the issue is. Furthermore, each time the Apache configuration changes it takes 2 hours for the changes to appear to find out if it is fixed yet. Probably the best way to solve this is to try transferring an account to Morty where we can restart Apache every 5 seconds to test changes because there are no accounts on there yet rather than trying to figure it out on a live production server with thousands of accounts. It's definitely on my todo list. Anyways as far as ways to fix the issue immediately, probably the simplest way is for you to make a full backup, delete the broken account, and create a new account directly on Plesk so it doesn't have this issue anymore, and then restore your backup onto the new account. If this is something you'd like to do please let us know when you're done backing everything up and any moderator+ can delete your account for you and send an invite to recreate it.

Remote access enabled.

First of all, here's what your disk usage looks like. Keep in mind your account is limited to 1000 MB. Backups 0 MB Emails 0 MB Files .12 MB Logs 1783.26 MB PSQL 0 MB MySQL .35 MB Total 1783.73 MB Your error_log is 1.7 GB on its own. I emptied it and unsuspended your account. Here is what your load graph for the last 24 hours looks like. As you can see your memory usage and CPU usage spiked quite a bit right before you were suspended. Obviously the load dropped to zero when your account was suspended. Your logs were set up to rotate daily and keep 14 days worth of logs. You got 1.7 GB of errors in less than 1 day so obviously 1.7 GB multiplied by 14 is 23.8 GB of logs, which isn't acceptable when you're allowed to have 1000 MB. I instead changed your logging policy to rotate after 10 MB and keep 14 files so roughly 140 MB of logs will be kept. It might be a good idea to take a look at the error log and fix all of your PHP errors anyways. Let us know if you need help with any of that.

It looks like you lost 2 points for not emailing real content. Simply sending the single word "test" will always get flagged as spam. An actual issue is your DKIM got turned off somehow. The DKIM box was checked yesterday, but between yesterday and when you sent that test email it got turned off somehow. I turned it back on again for you. You can test an email with real content now if you want to.

Thanks for the feedback and the honesty. You are correct that there's not a lot we can do about the DDoS. We were working closely with our ISP to mitigate the effects as much as possible, but a large enough DDoS can overwhelm any website in the world. Each individual user can choose to use a service like Cloudflare that helps hide the server, but a smart enough criminal can use MX records instead of A records to find the host. Each individual user can choose to use a service like Zoho that helps hide the MX records, but it's not reasonable for us to require everyone to use Cloudflare and Zoho. Our ISP helped a ton by null routing the targeted IP address at the perimeter to help keep the rest of our IPs online, but the attacker kept changing targets when they got null routed so our network would get overwhelmed again for a while until the new IP was null routed too. Our ISP was even kind enough to move us off of the shared port and give us a dedicated port for free so we wouldn't be reduced by the bandwidth of their other customers as well. Regarding the hard drive glitches, when we first started building VPS we didn't realize how much the performance would drop as we added more and more VPS to the same raid array. We tested the raid array quite a bit before we built the first VPS and the speed and latency were really good, but as we kept piling them on there the performance started to drop below an acceptable level. Then we had the infamous VPS33 that really ruined it for everyone. He was using so much disk I/O and CPU that everything really fell apart. That's when we started a fundraiser to buy some higher performance hard drives to help isolate his load from everyone else. He was paying us about $30 per month so it's hard for us to decide whether to kick off a paying customer that isn't violating any of our terms of service. Since we're a non-profit powered by donations and run by volunteers we can't just order a new server and have it delivered and installed the next day like a for profit company could so it took us a few months to get the money and get it all installed. Things have been going much more smoothly since then, but we're taking everything we've learned so far and buying our next server to provide even better shared hosting and VPS hosting. We're already to 67% of our goal so hopefully we can get it set up soon. Another thing we can do for you is move you to a faster server immediately if you're still having problems. We have some free space on one of the hard drive arrays that we bought from our last fundraiser. We don't just offer people upgrades like that without them coming to us first though because it causes a few hours of downtime to move a VPS between servers, and if people are happy with where their VPS is currently there is no reason to cause unnecessary downtime. You've still got a month of VPS time prepaid so if you want to try the faster server for this last month and don't mind a few hours of downtime while your VPS is moved just let me know. We can also give you a free rebuild to a newer OS if you want. You signed up in 2020 and it looks like you're running Debian 10. We could upgrade you to Ubuntu 22 or Debian 11 if you want to try them. We can also rebuild you with Debian 10 again if that's what you prefer although security support for Debian 10 ended 7 months ago so it's probably a better idea to upgrade to a newer OS. Anyways, thanks for using our VPS service, and thanks for recommending us to people you know. It doesn't bother us for you to let us know if things aren't working well enough for you. If people don't say anything we have to assume that everything is working well. If something isn't working well enough we can try to come up with options to make it work better.

When you donate to get an account the invite is sent to the email address that PayPal has on file, and then the account is created with that same PayPal email address. When the account is created it is set up with a default Let's Encrypt SSL certificate using that same PayPal email address, which is what you're seeing in the top right corner of the SSL/TLS page. The way you can change that value yourself is by clicking the unassign button to remove the existing SSL certificate, and then click install to set up a new SSL certificate using the current email address that Plesk has on file. I went ahead and did this for you to save you some time so when you go to the SSL/TLS page you should see the new email address in the top right corner. Please be aware that since the old SSL certificate was removed and won't be renewed you will probably receive a warning email to your PayPal address from Let's Encrypt in a couple months letting you know that the old certificate is about to expire. You can just ignore those emails and Let's Encrypt will leave you alone after that. Thanks for the donation by the way. Let us know if you have any other issues or have any questions.

SPF, DKIM, and DMARC have been set up for the domain thebigdickcock19.helioho.st. We recommend sending a test email to https://www.mail-tester.com/ to make sure everything is set up correctly. If the score is anything less than 10/10 you can link the report to us and we can help you fix any issues. I would also like to mention that based on your domain name, in case you didn't read our terms of service closely enough, we don't allow porn sites to be hosted on our servers. If you would like to review the terms of service again they can be found at https://wiki.helionet.org/hosting/terms

It looks like you made your last 6 month payment on October 5th so 6 months from that date is April 5th. However, looking at the payment before that it looks like you made your October payment early. Our system doesn't account for a previous balance so when it sees a payment it just moves the expiration date forward 6 months from the payment date. This works fine for automatic subscriptions which 99% of our users have, but doesn't work as well for people like yourself who make non-recurring payments, and don't check their email often enough to see the warning to get it figured out prior to the VPS being powered off. Of the 500 or so VPS that we've sold over the years only you and one other person, also from India, have ever had a problem setting up a recurring subscription, but we do plan to upgrade the payment system eventually so people can just make one-time payments when needed rather than relying on PayPal to bill you automatically as some people would probably prefer that. I'd like to point out that our VPS service is extremely stable, suitable for public facing websites, and we have 99.99% uptime with only maybe an hour or two of scheduled maintenance per year. This is actually the first time anyone has claimed that our VPS are unstable. Are you referring to your VPS being powered off for lack of payment, or were you having some other issues prior to this? Anyways, your VPS has been powered back on, and your expiration date has been manually set to May 5th which is one year from the start of your first 6 month payment.

Your Ricky account has been deleted and you can signup again using the same username and domain, or change to a new username or domain, at https://heliohost.org/signup/ Currently only Johnny is available for free signups, and Tommy is donor only starting at $1. Johnny free signups reset at midnight UTC. Let us know if you have any issues signing up again. Free signups are generally available for a few minutes up to a few hours depending on the day so if you miss the window one day you can just try again the next day.

Your subscription has been canceled and you won't be charged again. Thank you for using our VPS service. If you don't mind providing some feedback, what were you expecting from a VPS? Perhaps we can explain it better on our website so this doesn't happen to anyone else?

Remote access enabled.

The extension pgcrypto has been created on the database landho_ratemyskipper_production.

Remote access enabled.

Your VPS is rebuilding. You'll get an email when it's done.

Probably the easiest way is to run the command top occasionally and sort by memory usage. If you see some process using like 80%+ of your memory you found the problem.

Remote access enabled.