SimpleHelp 6.0 Release

Hi David,

You probably reached this conclusion as well, but I’ll post as it may help others.

For the disappearing MAC OS computers, Remote Access is actually running but it seems that the update did not take with it the server details so what you get is a blank remote server and so the workstation cannot connect.
Has to be added manually, which sucks, as you have to have someone local with admin access rights.

Check the pic …

I have still to discover as to why some of my macs have gone to terminal mode only (icon) without actual access to computer (terminal mode or other), will post if and when I can get a handle on this problem.

Regards,

GS

1 Like

Ok, So I have a solution for the “TERMINALly “ dead MACS (forgive the pun :rofl: )

This is them:

It seems that the update transformed the http://URL:443 type URL to a https://URL.. WHY???

Solution:

1 - Select the workstation;

2 - Click on the “Advanced menus and controls” icon;

3 - Click on the “Configure” icon;

4 - VERY IMPORTANTE - FIRST add the correct URL to the “Remote Access Servers” (http://URL:443) and then, ONLY THEN, remove the https://URL;

5 - Save Configuration

6 - The workstation will then appear as should be albeit with an “AUTODECT” identification name.

Note: You’ll lose any personalised name you have given the workstation, so take note before hand

Hope this helps.

NOTE TO DEVS - If and when you need a PAID betatester be shure to call me!

:rofl:

2 Likes

P.S. Be patient as it takes a little bit to refresh the “Terminal” icon to the little “Green Ball”

I can confirm this works, obviously this release was not properly tested with MacOS, which seems to be a trend.

1 Like

I am not going to lie, I am disappointed with SimpleHelp.

I have been a SimpleHelp customer since August 14, 2018, and I genuinely loved the product for many years. Unfortunately, each update now seems to introduce more problems, and the application has become noticeably more buggy and unreliable overall.

I miss the days when I could connect to a remote machine, have every display work properly, and move around the system smoothly. Now, I regularly encounter black screens, random disconnections, and sessions that fail to reconnect correctly. In many cases, I have to completely close the application and reopen it just to reconnect to the machine.

The new design of both the SimpleHelp website and the application also feels like a step backward. Frankly, neither looks particularly polished or appealing to me. More importantly, when features are supposedly being improved, basic and useful functionality should not disappear in the process. Removing common-sense features such as search fields does not make the product better. It makes routine tasks slower and more frustrating.

The customer portal is another major disappointment. Despite being a customer since 2018 and having made multiple purchases, the invoice section says I have no invoices, and there is no meaningful billing or purchase history available. It is 2026. Customers should have access to a real customer portal that shows their complete account history, purchases, invoices, licenses, billing information, and support activity.

The lack of a proper helpdesk is equally frustrating. Support should be accessible directly through the customer portal, with the ability to open tickets, review previous requests, track responses, and maintain a complete support history. Customers should not have to rely on an informal or disconnected support process for a commercial product.

I am perfectly willing to pay for a reliable, well-supported product. I have repeatedly ignored recommendations from others to consider alternatives such as RustDesk because I preferred SimpleHelp and wanted to remain loyal to the platform.

I do not want this review to come across as unnecessarily harsh. My frustration comes from having used and supported the product for nearly eight years and watching the experience gradually become more difficult. Each year, I find myself more annoyed by problems that either remain unresolved or are created by changes that do not seem focused on the everyday needs of actual users.

It increasingly feels like the focus is no longer on improving the core remote-support experience. Instead, the priority appears to be adding unwanted features and finding new ways to monetize the product on a per-machine basis.

I would much rather see SimpleHelp focus on stability, reliable reconnections, multi-display functionality, performance, preserving useful features, restoring basic usability such as search fields, creating a modern customer portal with complete account history, and providing a proper integrated helpdesk before introducing additional features or pricing changes. Heck I will pay more for my license, if the product is stable and fast.

2 Likes

Yeh similar issues, except some of our techs can’t login to the tech console at all just keeps looping them and clearing the username and password box. It’s more than likely filtering related but it wasn’t an issue with 5.9. We unblocked *.simple-help.com issue remains. Chris sends requests for more logs etc, but for how long its taken to get version 6.0 released these issues aren’t great. 3 days without it for some of our techs so far.

I suspect the issue to be down to the tech client calling home to the Simple Help license server, that or a new QR URL for 2FA is being used and some how this bugs out now.

Hi Josh,

Been back and forth with support due to similar issue, user with MTA (2FA) active before update had no MTA after update.

Resolved by creating new User and new Group with same permissions as before.

Logged in the new user, had an MTA(2FA) Challenge/configuration window, configured new MTA(2FA) via QR and was working as normal.

Regards,

GS

6.1

Installed on windows, connecting from windows11 to windows11

Am regularly getting a ‘connected’ strip across screen

I’ve rebooted everything involved but issue persists

I thought I read through all the issues and their linked upgrade guide, but it seems that I’m not stuck with a broken system, lost time trying to get it working and a tech unable to work on a remote case.

Email sent to support, but not response yet…not exactly the fastest method of communication for support tickets.

Shouldn’t that be there automatically if your support is up to date?

1 Like

I have to reconnect to Windows 11 machines constantly to get a solid remote connection. 3-4 times at least especially if they are using RDP connections.

I’m having the same issue, especially with multi-monitor systems.

We ran into a lot of issues with connection stability and general usability that support was unable to resolve so we rolled back to 5.5.16. Now we have to run through and re-install all the agents…

All we were able to get from support was a pdf to troubleshoot on our own.

Version 6 is an absolute disaster.

The platform is so unstable that I am being forced to reconnect every two to five minutes. Sessions regularly have to be manually terminated and restarted because screens are completely blank, fail to render, or load only about 75% of the interface. Sessions constantly hang, freeze, and lag, including on computers connected to the same LAN and the same network switch.

The connection method makes no difference. UDP, TCP, and HTTP all produce the same unacceptable results. File transfers repeatedly stop and will not resume. Basic functionality that should be dependable is now unreliable at every level.

I genuinely do not understand how this release passed any meaningful quality-assurance testing or was considered ready for production use. The software is fundamentally unstable and is actively disrupting our ability to work.

I have been a customer since 2018. I tried to remain patient, give the benefit of the doubt, and assume the initial issues would be corrected. At this point, there is no reasonable way to defend the condition of Version 6.

It is, quite frankly, one of the worst software releases I have ever been expected to use.

This needs immediate attention, a clear explanation of how such a defective release was approved, and a concrete plan to restore a stable and usable product.

Telling customers to continue troubleshooting or changing connection settings is not an acceptable response when the failures occur across multiple systems, connection types, and network conditions.

Version 6 & 6.1, in its current state, is unacceptable garbage. It added some bulls**t Ai component no one asked for, I guess to try and ride the Ai wave, and has broken the very core features and reason for its existence. Was this release built by Ai? It would certainly explain all the bugs.

I was a Simple-Help fanboy, and I currently find myself apologizing to others I convinced to use this software.

4 Likes

I have the same stability issues. I’m also having to force quit the JDK process if idle sessions are left open for a while as it drives the CPU to 100%. It takes several connections to get a session with a client after much delay. Sometimes it does reconnect, but with a banner stuck across the screen that says Connected. There are mouse cursor artifacts flashing everywhere. This version is barely usable. I will have to look to going back

1 Like

Thanks for everyone posting and alpha testing these releases. Many of us who aren’t posting use this information to carefully gauge when to start deploying or testing releases. Though you all are suffering, you have saved us countless hours of troubleshooting and frustration by taking the time to post and indicate these issues.

Thank you all so much.

1 Like

Hello…I have been following this thread and I have to be the contrarian voice here. I deployed 6.1 directly over 5.5.16 supporting about 740 endpoints with Windows, Linux and Mac and have had very few issues. The first thing I did was run through the server security checkup wizard and applied all the recommendations including the crypto settings, etc. The only issues I have had are below:

  1. Connections to my Rocky linux boxes only display the shell directly and I do not have the other features like console, statistics, processes, etc. Ubuntu boxes are fine.
  2. Some issues with the columns on the interface resizing, etc. Minor annoyance.
  3. I have seen the “Connected” bar across the screen a couple times on some on-demand windows sessions but I saw that occasionally on 5.5.x.

Aside from those items I am happy with 6.1. My server is Ubuntu linux 24.04 with Fedora linux KDE (Plasma w/Wayland) as my tech console. I have been running for a little less than 2 weeks. Maybe I just have not run into the issues in this thread yet but I will be sure to post back if I do.

EDIT: Just a little side note for others. My Linux box is sitting in a VPS with UFW enabled only with geoblocking, etc. Basically everything is blocked except the required ports for SH. The point is there is no stateful firewall in place with web filtering, etc running on it. Now I have noticed in 6.1 that some of my customers behind Sophos firewalls have had issues with the Sophos Web filter service where my connections would drop all the time with terrible connections similar to what everyone is describing above. This even happened with my URL whitelisted in the web filter. My only solution for these few customers was to temporarily disable the web filter and all was well. Again this happened when I went to 6.1. 5.5.16 was fine. I am just throwing this out there for others who might actually have their SH server behind a stateful inspection firewall with services running on it that might be causing these issues. Just FYI.

EDIT #2: So I was able to resolve my Sophos firewall issue but creating a dedicated firewall rule scoped to my SH server as the destination which has web filter, DPI/IPS and app control disabled. Once I did that the connections are perfect. Now I do remember with 5.5.x when I was connected to devices behind Sophos firewalls I would always have a 10 second hang every 10 minutes or so but it was consistent across the board on all Sophos firewalls. And based on what I am reading SH 6.x completely revamped their underlying network stack with higher throughput and stricter TCP controls. Perhaps this is what is happening to others here.

1 Like

Wow, I’m glad I trusted my gut and didn’t upgrade from 5.15 to 6.x. Given the last few upgrades I’ve gone through, “disastrous” would be an understatement. At times, every upgrade felt like playing Russian roulette—you never knew what would get fixed and, more importantly, what would end up broken afterward.

So.. have these issues listed been resolved in 6.1?

Nope! I wish it had.

1 Like