Don’t know if this happend because of the customization of the login-page .
The database with connections, users etc. still exists.
But I can’t open a remote session.
It sticks on “waiting for response” when I try to connect to a Win10-machine.
Just a short try. Will play more with it later.
I think it not a problem of guacamole itself, more a networkproblem/Windowsproblem here.
So, great work Markus!! Thanks a lot for your effort on this!!!
It seems to be a problem of my Win10-clients.
With one client on Win10 2004 it works, with another client on Win 10 20H2 it doesn’t work???
But I can do a windowsremotedesktop from the Win10 2004 client to the Win 10 20H2 client.
So remotedesktop on the 20H2 client is working, but not guacamole.
Strange windows world…
EDIT: When I deactivate WOL in connection it works with the 20H2 client.
I think to recall you could configure guacamole to make the server send a WOL packet to wake-up a specific computer and set a wait/delay for the computer to be up before effectively trying RDP connection.
I’m getting a 404 after upgrading.
All the services are running, but I noticed that guacd is running on 4822, while the apache conf is set on 8080:
[root@smart guacamole]# systemctl status guacd
● guacd.service - Guacamole proxy daemon
Loaded: loaded (/usr/lib/systemd/system/guacd.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-02-25 10:32:53 -03; 29min ago
Main PID: 2043 (guacd)
└─2043 /usr/sbin/guacd -f
Feb 25 10:32:53 smart.nethserver systemd: Started Guacamole proxy daemon.
Feb 25 10:32:56 smart.nethserver guacd: Guacamole proxy daemon (guacd) version 1.3.0 started
Feb 25 10:32:56 smart.nethserver guacd: Listening on host 127.0.0.1, port 4822
Feb 25 10:32:56 smart.nethserver guacd: guacd: INFO: Guacamole proxy daemon (guacd) version 1.3.0 started
Feb 25 10:32:56 smart.nethserver guacd: guacd: INFO: Listening on host 127.0.0.1, port 4822
Hint: Some lines were ellipsized, use -l to show in full.
systemctl status tomcat8 -l
● tomcat8.service - Apache Tomcat 8 Web Application Container
Loaded: loaded (/usr/lib/systemd/system/tomcat8.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-02-25 12:03:32 -03; 4 days ago
Main PID: 2101 (jsvc)s
On a production server I see an update to guacd, should I uninstall the testing version and try the updated one from official repos?
Don’t know how much work this is to include the db prop, but for flexibility reason I’d say yes.
IIUC it would also be possible to use any LDAP-property you wich to use, or not?
So also a computer name or a group name would be possible.