Apache Guacamole fails on some computers
by Lindgren from LinuxQuestions.org on (#6J97P)
Hi!
Since a couple of months I have had issues with Guacamole, earlier it always worked perfectly for several years. At first I noticed that my instance was a bit outdated so I removed it and installed a new one, this time through a installer script which added it to dockers with 2FA and the whole shebang! Super nice I thought as I tested this at home, no problem.
Checked this on my work-laptop and after the login part and 2FA, it fails.
All still works perfectly on my phone and personal laptop, and the logs doesn't say much really either.
Quote:
Quote:
Quote:
There is a couple of warnings such as misplaced pid-files and also the "Execution of ping query 'SELECT 1' failed: The last packet successfully received from the server was 142,599,441 milliseconds ago..." however I am quite sure that is not relative to my connections, but only that it fails after a long couple of hours with no data. I can still connect on my phone so it must be something else.
I am also using a nginx reverse proxy, which I rechecked the settings with the settings they recommend.
There is also the "mbind: Operation not permitted" which I cannot really trace, since there is no time stamp and also it comes... sometimes, not always when I connect.
The error screen simply says "An error has occurred and this action cannot be completed. If the problem persists, please notify your system administrator or check your system logs." which I see mostly if there is an sql error on the back-end but I cannot figure out why or where..?
Since a couple of months I have had issues with Guacamole, earlier it always worked perfectly for several years. At first I noticed that my instance was a bit outdated so I removed it and installed a new one, this time through a installer script which added it to dockers with 2FA and the whole shebang! Super nice I thought as I tested this at home, no problem.
Checked this on my work-laptop and after the login part and 2FA, it fails.
All still works perfectly on my phone and personal laptop, and the logs doesn't say much really either.
Quote:
guacd[1]: INFO:Guacamole proxy daemon (guacd) version 1.5.4 started guacd[1]: INFO:Listening on host 0.0.0.0, port 4822 |
2024-01-24 10:48:13+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.25-1debian10 started. 2024-01-24T10:48:13.675944Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.25) starting as process 1 2024-01-24T10:48:13.695331Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-01-24T10:48:14.222890Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 2024-01-24T10:48:14.434970Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock 2024-01-24T10:48:14.551802Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 2024-01-24T10:48:14.552146Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel. 2024-01-24T10:48:14.554544Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory. 2024-01-24T10:48:14.589704Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.25' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL. mbind: Operation not permitted mbind: Operation not permitted mbind: Operation not permitted mbind: Operation not permitted |
16:07:24.137 [http-nio-8080-exec-7] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 16:07:42.907 [http-nio-8080-exec-3] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:44:55.487 [http-nio-8080-exec-4] WARN o.a.i.d.pooled.PooledDataSource - Execution of ping query 'SELECT 1' failed: The last packet successfully received from the server was 142,599,441 milliseconds ago. The last packet sent successfully to the server was 142,599,441 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem. 08:45:35.763 [http-nio-8080-exec-1] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:45:51.991 [http-nio-8080-exec-8] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:47:58.088 [http-nio-8080-exec-9] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:48:15.904 [http-nio-8080-exec-2] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:48:26.315 [http-nio-8080-exec-6] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:48:37.178 [http-nio-8080-exec-3] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 08:48:55.428 [http-nio-8080-exec-9] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 09:08:40.677 [http-nio-8080-exec-2] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. 09:08:57.009 [http-nio-8080-exec-5] INFO o.a.g.r.auth.AuthenticationService - User "johan" successfully authenticated from [x.x.x.x, 172.16.8.1]. |
I am also using a nginx reverse proxy, which I rechecked the settings with the settings they recommend.
There is also the "mbind: Operation not permitted" which I cannot really trace, since there is no time stamp and also it comes... sometimes, not always when I connect.
The error screen simply says "An error has occurred and this action cannot be completed. If the problem persists, please notify your system administrator or check your system logs." which I see mostly if there is an sql error on the back-end but I cannot figure out why or where..?