-
Posts
17,655 -
Joined
-
Last visited
-
Days Won
656
Everything posted by wolstech
-
Sure. Since I have an actual Plesk backup from July 3rd for your account, I'm checking to see if we can just restore your backup onto Tommy vs. just reinviting you and you restoring data manually. I've asked about this possibility in a staff channel...if we can restore the backup directly it'll be a lot less work for you
-
As of the latest update, the hard disk rebuild failed. Krydos is looking into whether it can be recovered, but that is going to take quite some time assuming its possible. The good news is in your specific case, we had backed your account up on July 3rd for an unrelated reason, so you can download your backup to restore to how it was 2 weeks ago if needed. Many of our users are moving to Tommy for the time being, and VPSes are also an option.
-
I don't think the 2019 Tommy had RAID, so the disk dying just killed the server. Johnny's data was on a RAID1 volume (a mirror), but we're still trying to get the new disk to rebuild now that it's been replaced. If it ultimately refuses to rebuild and/or the second disk in the mirror dies, it's functionally the same as all of the other disk crashes we've had...
-
Sparkie is a vmware ESXi server. The -ie names are all physical boxes, the servers with -y names are VMs living on the -ie boxes. The physical boxes have various data stores made up of groups of disks. In Sparkie's case, there's 3 groups of disks forming 3 datastores (DS1, DS2, DS3) that store the VMs and virtual disks. The disk group that held DS2 is what failed. DS2 only contained the virtual disks for the /home and mysql/pgsql data partitions for Johnny, so Johnny broke. DS1 and DS3 are fine, which is why there isn't a more severe outage. The other virtual servers on the Sparkie hardware are working normally. Those include Lily (Windows hosting), Cody (an account management server), and VPSes rented by customers. Ricky was ultimately done away with due to the cPanel license being revoked. It ran for a while afterwards without a control panel until we transferred all the accounts off it, then we retired it. We currently don't have a Plesk license to rebuild it.
-
It was indeed high load. The memory went through the roof on your account for several hours before we suspended it. Please fix this issue quickly and make adjustments so this does not happen again. Unsuspended.
-
That IP address is null routed due to an ongoing DDoS attack. Your account was likely moved to a different IP address to restore service during the attack, or soon will be if it has not already. Please check in Plesk to see what your new IP address is, and try using that address instead of the .77 IP. You may also want to try using the host name of the server: tommy2.heliohost.org if neither of these work, I'll escalate this to Krydos.
-
[Solved] HelioHost VPS56 Index1337 | cancel end of month
wolstech replied to index_1337's topic in Escalated Requests
Krydos should be able to cancel the subscription on this so it won't renew automatically, but you can finish using the month. -
Disk was indeed bad. We had a tech at our datacenter visually check the server and one of the two disks in the array that supports Johnny's user data volume had a failure light on. That has been replaced and I believe the RAID is cloning from the remaining disk at the moment (the datastore that failed was a mirror/RAID1).
-
Please change the main domain for "alexgoldberg" account
wolstech replied to dosprn's topic in Customer Service
Main domain moved and subdomains added. It can take up to 2 hours for everything to start working. If you get a multiple account suspension once Johnny is back, just let us know and we'll reverse it. The system might do that automatically. -
No access to my account mensajesparapruebas@gmail.com
wolstech replied to vicente's topic in Suspended and Queued Accounts
Johnny is experiencing hard disk issues and is down for the time being. See https://helionet.org/index/topic/61310-more-johnny-issues/ -
If it goes like previous failures did, probably backups where possible followed by a rebuild again...
-
You're not suspended...I did add a bunch of domains recently for you and none have SSL support, so this is probably why you're seeing that message. Domains that are unconfigured or domains that are accessed over SSL without SSL support enabled show a suspended page on Lily. The suspended page is set as the default web server page on Lily due to how suspensions in IIS work (IIS doesn't redirect suspended domains...it treats them as if they're not added at all), a side effect of this is that domains that aren't configured show as suspended. On Plesk you'd see the "Default server web page" instead. This should be fixed.
-
We were seeing apache errors that listed your domain as the cause so the dosprn.com domain was removed to allow apache to restart. Removing a domain removes all subs automatically. That said, we have since discovered that the server your account is on (Johnny) has additional file system corruption due to what we think is hard disk failure. It is currently down for maintenance while we attempt to recover it. Once we successfully recover the server, I can add these domains back for you.
-
You were suspended for having more than one account. That said, we cannot unsuspend you at this time because server the account is on is down for maintenance.
-
Johnny is currently down for maintenance due to what we believe is a hard disk issue.
-
It is indeed load...again. This is your second time for load in the past 2 months, and you've had your email service disabled twice for sending too many emails as well. What steps have you taken to correct the issue so this doesn't happen a third time?
-
[Solved] Cancel Subscription and delete VPS
wolstech replied to ualtarh's topic in Escalated Requests
Krydos can do this for you. -
[Solved] Installing additional python dependencies for flask app
wolstech replied to jpmorr's topic in Escalated Requests
Let's see if Krydos can install these for you. -
[Solved] Installing additional python dependencies for flask app
wolstech replied to jpmorr's topic in Escalated Requests
Can you please go through this list and provide only the ones that need to be installed? The list of modules already present on Johnny is available at the link below. https://krydos2.heliohost.org/pyinfo/info3.10.py Note that we typically won't install anything that would require a GUI or terminal to use (we don't allow SSH access), anything that makes the app host its own server/listen on a port (we don't allow custom incoming ports), or anything that, if updated, would break other users' code. If any of these modules meet these conditions, a VPS is needed. -
To avoid potentially notifying actual abusive users (e.g. phishers, copyright infringement, etc.), we intentionally don't send emails when accounts get suspended (the lone exception to this being inactivity suspensions, which we do send reminders for) Anyway, your suspension is because you ran out of disk space because your Apache logs for timerestart.ga had ballooned to over 1GB. I deleted the logs for you, unsuspended you, and configured log rotation so your logs won't exceed 50MB. If you wish to keep more logs, you can do that in Plesk under Logs->Manage Logs->Log Rotation.
-
It is indeed high load. As you are probably already aware, WP is notorious for this. In fact, WordPress is probably the number one cause of high load suspensions here. Our typical advice is to not use WordPress due to how inefficiently written it is, and to avoid extensions if you do have to use it (three big extensions that we commonly see cause tons of load are woocommerce, wordfence, and elementor). Please fix it quickly. Unsuspended, it may take a few minutes to start working.
-
I see the payment on our side, you're good until January 9. Auto-pay typically attempts to charge you on your expiration date. If the auto-pay fails, I believe you get an email about it failing from paypal. We also send our own warning emails when your payment goes past due, and you get several days to pay before it shuts down. I'm not sure how long the VPS is kept before deletion once shut down, but it looks like we currently have one that was turned off several weeks ago and it still hasn't deleted (I suspect this time period is 30 days, but may be wrong on that). A VPS that was shut down for nonpayment can be recovered up until deletion by paying the past due bill then contacting support to have it turned back on.
-
[Solved] Suspended: mensajesparapruebas@gmail.com
wolstech replied to vicente's topic in Suspended and Queued Accounts
I'll basically guarantee that it was Wordpress related since you mention using it. WP is probably the number one cause of load suspensions here (with nodejs being a close second). Please fix the issue quickly (the best solution would be to get rid of WP entirely, though this is understandably not always possible). Note that this is your second suspension for this issue. A third suspension for WP-related load, if it occurs, might come with the condition of deleting Wordpress in order to be unsuspended. Unsuspended. It may take a few minutes to work again. -
I assume this is for VPS43? If so, try this link which should be specific to VPS43: https://heliohost.org/vps/pay/?code=pDzbrBcnmKVSB5oI It should just prompt you for how to pay, and should state above the payment options that it's for $37.80 for 6 months (the VPS is a 2GB RAM, 2 CPU cores, 50GB storage model with a 6 month term). If it's asking you to pick a plan and duration, you're looking at the regular VPS signup page, which should not be used for a renewal.
-
Unsuspended. It may take a few minutes to work again.