I’m a SimpleHelp reseller and I have 15 customers all on their own Ubuntu SimpleHelp servers using DigitalOcean droplets. Every single SimpleHelp server has started crashing with memory errors. I just go into SimpleSetup and stop/start SimpleHelp services and it’s back up….but then crashes again a few hours later.
The servers are in different regions, so I know it’s not a DigitalOcean issue. They are on different versions of Ubuntu, so I know it’s not a new patch or something with Ubuntu. They are all on the latest release 5-5-20250819-172905.
Yes, we are having the same problem with memory errors using Digital Ocean droplet. The server been running for over 10 years and this is the first time something like this has happen. Also, we have noticed many failed technician logins for the past two days. Right now, however they seem to stop but who know when they might start again. I’ll check out the thread mention earlier.
I have had this issue, exactly as you described. I submitted tickets to DigitalOcean Tech Support. Although the support response was ‘very polite’… I typically only receive links to ‘Tutorials’ and things to check. I never get anyone actually doing any sort of hands-on resolving of my problem.
This is why I decided to move my SimpleHelp Server to my own server in my own network. I also switched from running on Linux to running on Windows.
Hi Drew, we have continued to have these types of issues since all of this started a week or 2 ago.
I’ve been insanely slammed so I haven’t been able to look into it, and fortunately we only use SH for a hand full of machines (less than 150) now as we’ve transitioned everyone else over to datto rmm, but something is happening. My gut says it’s an attack of some type, as it all started happening in coordination with unsuccessfull technician logins.
It’s fairly simple to enumerate simple-help server installs, I guess I just don’t understand to what end this is being done though. We have seen it continue to happen though even yesterday.
I don’t know if this helps, but 5.5.13 had a memory leak. I also noticed that after one of the upgrades, though it appeared that every setting had migrated successfully, the allocated system memory had reset to its minimum level.
Took me awhile to figure out why everything had slowed down and wasn’t working as well, it was because the server was running out of memory, due to not having any allocated to it.
Remote Support
Remote Access
Monitoring and Management
Presentation
Remote Work
Standard
Business
Enterprise