Jump to content

wolstech

Chief Risk Officer
  • Posts

    18,852
  • Joined

  • Last visited

  • Days Won

    742

wolstech last won the day on March 22

wolstech had the most liked content!

About wolstech

  • Birthday May 17

Contact Methods

  • Website URL
    https://www.raxsoft.com

Profile Information

  • Gender
    Male
  • Location
    Pennsylvania

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wolstech's Achievements

Grand Master

Grand Master (14/14)

  • Well Followed Rare
  • Reacting Well Rare
  • Conversation Starter Rare
  • Dedicated Rare
  • Very Popular Rare

Recent Badges

1.5k

Reputation

  1. You got suspended for using too much memory. The limit is 200GB per day. Please fix the issue quickly. Unsuspended. It may take a few minutes before you can login again, and domains can take up to two hours to function.
  2. You're the first person to report that the logs are slow only when node is enabled... that's an interesting observation. Morty would likely make it faster since the entire server is quite a bit faster than Tommy, but I'm actually kind of curious as to why this only happens to you when node is enabled. Maybe Krydos has some input on this?
  3. It was suspended for high load caused by systemd, which is likely due to excessive use of cron. The scheduled jobs have been turned off on your account and you've been unsuspended, please fix the issue quickly. It may take a few minutes before you can sign in again, and domains can take up to 2 hours to function.
  4. That domain is working properly for me. Please clear your cache. Note that this error is usually caused by running out of disk space, and you are very close to your limit (975 of 1000MB). I suspect you were over your limit earlier and have since dropped below due to something like log rotation freeing up space.
  5. error_log for domain twoofswords.net has been discarded. The best fix for this is to enable log rotation and set a max size that's reasonable (like 10MB) with a low maximum number of logs (like 3). That way the server will rotate them out and then eventually delete them for you. I've gone ahead and set up the rotation for you on that domain so this won't happen again.
  6. Escalating to have this enabled for you.
  7. Account senex has been unsuspended. It may take a few minutes before you can login again, and the domains can take up to two hours to function.
  8. Can you explain why all of the accounts have very similar usernames? (Also, on the off chance these are a result of you just needing multiple websites, you can have multiple sites on 1 account...a Johnny account can have up to 5 websites/domains on it).
  9. Domains that are already added as an add-on domain cannot be switched to the main domain without resetting your account. https://wiki.helionet.org/Changing_Your_Main_Domain#Account_Reset_is_Required_to_Swap_Main_and_Addon_Domain
  10. The pending suspensions for luisgalvan and backupchiquipoli have been canceled.
  11. There are actually 3 accounts associated with you this time (two of which are the luisgalvan and backupchiquipoli accounts you've been allowed to keep already). Did you or someone you know create a third account without contacting support for permission? Also, did you at any point use a VPN to access your accounts?
  12. Yeah you had a ton of load coming from Python (note these numbers have dropped off a bit because you've been suspended for a little while). 66.38 GB 120.2 /usr/bin/python3.12 -u -O /home/dragoe.helioho.st/httpdocs/AppFiles/Moonlark/moonlark.py -n DragoE 56.11 GB 28.1 /usr/bin/python3.12 -u /home/dragoe.helioho.st/httpdocs/AppFiles/Watchman-main/Watchman.py There was also resources being used by the system due to the long-running python processes (about 14GB as of this post), which you can't really do anything about...it's just the nature of linux managing sessions. Please reduce the memory consumption quickly. Unsuspended. It may take a few minutes to work again. Domains can take up to 2 hours to function.
  13. If you have the certificate file (and matching key file), you can likely install that instead of Lets Encrypt. Not sure how you do that on Hestia, but I'd imagine there's an option or guide for it. It should work provided the certificate is not expired and the common name and subject alternative names (SANs) are correct (the domain/subdomain you're securing needs to appear in one of those fields on the certificate unless its a wildcard certificate). A domain's certificate is sent to the browser by whatever server is serving that domain, so you'll need to install the PositiveSSL cert on your VPS if you want to use it once your (sub)domain is pointed to your VPS.
  14. Information sent by PM.
  15. That account looks like it has already been moved to Morty and unsuspended.
×
×
  • Create New...