Popups in Web Sessions?

Hello

We previously had the same problem on Windows: https://forum.devolutions.net/topics/39937/open-anydesk-session-from-browser-session.

This should be very straightforward to fix, I'll open a ticket and we'll post back once it's corrected.

In the meantime, you might workaround the issue by right-click the link and copy it, then switch to Terminal.app and do "open {paste link here}". I understand that's not very ergonomic but hopefully it helps in the meantime.

Kind regards,

I don't think that the link works without authentication against Atera, but if you are aware and the fix is underway, this is alright. thanks!

Hello

I took a look at this and actually, I think it should work already, but the implementation is something I don't quite understand.

To be clear: is your problem that you want the popup asking to open the external application, or you just want the custom URL protocol (in this case, anydesk?) to work properly?

The first time you click on a custom URL protocol (without special handling on our side, like tel://) nothing happens. If you click it again (and any other time in the same session of using RDM) it should open the external application. Does that work?

I tested on my side with 2025.3.9.2: open RDM, click an anydesk:// link and nothing happens. Click it again and it works. All subsequent clicks work. This is implemented specifically in this way (the first link clink to a custom protocol is ignored), although I don't understand right now why it's done that way.

Please let me know if something isn't clear

Kind regards,

We are usually using Splashtop, but I tried with AnyDesk as well. But yes, there are interesting differences:

splashtop:

1. first click, nothing
2. second click, nothing

anydesk:

1. first click, nothing
2. second click, anydesk wants to start but the custom installer is considered malware by apple (jesus..)

So, something is different with splashtop. Directly in Microsoft Edge, which I'm using on macOS (I know.. :D) - it works with the first click.

Hello

Ok, thanks. So I need to look into why it was done that way (the multiple clicks).

For Splashtop, what do the links look like? Could you paste an example in this thread (and just anonymize anything specific to your environment)?

Thanks and kind regards,

This one is quite hard to find. Only the big button in the device page and only the drop-downs there give me a link which makes sense.

It looks like this for Splashtop: https://app.atera.com/new/rmm/device/def3*f8-f*d-4c*2-a**5-*2dc*******5/agent#:~:text=bysome_name-,Splashtop,-FREE

And like this for anydesk: https://app.atera.com/new/rmm/device/def3**f8-f*6d-**b2-a4*5-****/agent#:~:text=FREE-,AnyDesk,-FREE

Hello

Thanks for that, although sadly the links aren't helpful. Atera is surely doing some custom logic when you click the links (which are something specific to Atera) and then, in theory, redirecting you to the protocol handler for the specific application.

In the case of anydesk I know this is anydesk:// and as we've seen, it works - although you need to click a second time for reasons I'm working to understand.

In the case of Splashtop, I'm not so sure because I don't have an environment here but it seems it should work the same, just with a st-rmm:// protocol. But for some reason it doesn't.

Would you mind:

• Go to Help > Performance Profiling
• Switch to the "Debug Only" tab and change the "Debug level" to 131
• Leave the profiler window open, and go click a couple times on a Splashtop link in Atera in an embedded browser session
• Reply back here with what is printed in the profiler window

Please let me know if something isn't clear

Thanks and kind regards,

Can we move this into a support ticket so that I do not accidentally post sensitive data here?

Hello

I will ask the support team to step in and give you something private to share that.

Thanks and kind regards,

Hello Perler,

We would like a bit more information to better understand the issue. Could you please collect Profiler logs for us?

Please follow the documentation below to generate the logs, set the profiler number to 131, then reproduce the issue. After that, upload/send the logs using the link I emailed you.

https://docs.devolutions.net/rdm/commands/help/profiler/

Best regards,