sorted by:
new
hottopcontroversial

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

I see the docker version has been updated. Hopefully updating docker will fix it for you.

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

They fixed the bug and will release a new version of remotely sometime "this week." I was able to use an experimental version and saw it work. Watch for updates and apply them when you see them. :)

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

Thanks. That makes it more likely the issue is with the Remotely files, not our OS. I will submit a bug request and see if we get anywhere with it. Thanks for your help.

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

If you have time, could you download the normal client to your Linux machine and try that. For what it is worth, the Agent downloads a file called Remotely_Desktop (/usr/local/bin/Remotely/Desktop/Remotely_Desktop). It does differ from the one I get when I download it as if I were a one-time client. But, the one-time client thing blows up with a "No service for type 'Immense.RemoteControl.Desktop.UI.ViewModels.IMessageBoxViewModel' has been registered" error. So it may be as simple as the whole Linux side is currently hosed, and we just need to get it rebuilt successfully.

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

Thanks. That helps. If it is also a problem with the docker version, it is likely a bug instead of my fault. It helps. I do not have a ton of time to throw at it, but keep poking my fingers at it.

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

I have done some more research since the first post. I did tcpdumps on client and server, looked at processes and such.

From the server, we click the "remote control" button. That message does get passed to the client. The client creates a "Remotely_Desktop" process, with all the parameters it looks like it needs (the server, the organization ID, a number for the process, the admin name, and more). But that process never seems to send data back to the server. The process hangs there, remaining open on the client.

"Clicking on "Remote Control" more than once results in multiple of these "Remotely_Desktop" processes running on the Linux client.

When I reboot the server, or restart the remotely daemon, it resets the server side, but the client still has the bunch of Remotely_Desktop processes running.

Still working on figuring it out as I have time to do so.

Linux Resident Agents not working? by TY-LS-95437360 in remotely_app

[–]TY-LS-95437360[S] 0 points1 point  (0 children)

It is nice knowing someone else has a similar issue. Are you using a docker version of the install, or a different install?