[Apache Guacamole] <ALL connections start timing out after a week>

[dpaceoffice]

Platform

Virtual Machine

bndiagnostic ID know more about bndiagnostic ID

ea8753f9-e110-61b6-9f04-1e9454814535

bndiagnostic output

===== Begin of bndiagnostic tool output =====

✓ Processes: No issues found
? Connectivity: Found possible issues
✓ Resources: No issues found
? Apache: Found possible issues

[Connectivity]

Server ports 22, 80 and/or 443 are not publicly accessible. Please check the following guide to open server ports for remote access:

https://docs.bitnami.com/general/faq/administration/use-firewall/

[Apache]

Found recent error or warning messages in the Apache error log.

[Sun Apr 14 04:32:32.010437 2024] [ssl:error] [pid 3162841:tid 140673634252544]
Press [Enter] to continue:
[client **ip_address**:37376] AH02042: rejecting client initiated renegotiation

Please check the following guide to troubleshoot server issues:

https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro rs-apache/

===== End of bndiagnostic tool output =====

bndiagnostic was not useful. Could you please tell us why?

Suggested guides are not related to my issue

Describe your issue as much as you can

After updating on march 4th, running guacamole version 1.5.4. After about a weeks time all connections, SSH and RDP, suddenly stop working and begin timing out.

Simply running ./opt/bitnami/ctlscript restart resolves the problem.

Not sure what the root of the problem is however... Any insights?

[gongomgra]

Hi @dpaceoffice,

Thanks for using Bitnami. I have checked the bndiagnostic information that you shared and I don't see any error related to Apache Guacamole. However, the bndiagnostic tool don't retrieve any information out of the Guacamole logs. Can you check if there is any error related to your issue in the /opt/bitnami/apache2/logs/guac_log file?

I also see there are some settings available via the "settings" > "connections" > "new connection" > "protocol: SSH" web menu. I don't have any active connection at this time in my test server, but you can find there the "server keepalive interval" parameter, that I think can be of help. You can get more information on how to configure SSH, RDP and other protocols in the official docs. I'm sharing here the link to the SSH network parameters

https://guacamole.apache.org/doc/gug/configuring-guacamole.html#ssh-network-parameters

[dpaceoffice]

Happened again as of today, no errors found, just a bunch of get requests in guac_log. As for the parameter you were referring to, I don't know if that would help because it happens for all connections which aren't strictly SSH. The connections also work fine the majority of the time. I just have to occasionally run ./opt/bitnami/ctlscript restart.

I just setup a cron job to do this around 4AM every other day, but this is obviously not a real solution. This is a quiet error.

[gongomgra]

Hi @dpaceoffice,

Thanks for your message. I saw in the Guacamole docs that other protocols have similar parameters, but I'm afraid I don't know if that can be the solution or not. Can you try increasing the verbosity of Guacamole logs to debug to tru to get more information on the error? You have to replace the level="info" setting with level="debug" in the /opt/bitnami/guacamole/webroot/WEB-INF/classes/logback.xml file. After that, restart the service for changes to take effect

sudo /opt/bitnami/ctlscript.sh restart guacamole

Take into account that increasing the verbosity of the logs will make the Guacamole log file size to increase rapidly, which will consume more disk space and can cause other issues if you run out of it. We recommend you to restore the level="info" log level once you have reproduced the issue and checked the logs.

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.