You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have gotten SSH and RDP working without an issue for most of my hosts, but can not seem to understand why all my asus routers are not able to be ssh'ed with the tool.
I haave 7 routers which if i log into the Ubuntu Mate server which is hosting guac and ssh to them directly there is no issue. When i try to do the ssh with the guac tool I get "Connected to Guacamole. Waiting for response..." If I go to my router logs, I see that the connect is authd correctly, but immediately closes the connection with
dropbear[25710]: Exit (USER) from <GUAC_UIP:46318>: Exited normally
I already have a ticket open on the ASUS side of things, but is there any way to get more logs on what might be causing the connection to made and close immdiatly?
Sorry if this is not specific to the guac-install part of this forum, but there seems to be no offical easy way to open a ticket to guac themselves.
The text was updated successfully, but these errors were encountered:
Hello thanks for the easy install tool.
I have gotten SSH and RDP working without an issue for most of my hosts, but can not seem to understand why all my asus routers are not able to be ssh'ed with the tool.
I haave 7 routers which if i log into the Ubuntu Mate server which is hosting guac and ssh to them directly there is no issue. When i try to do the ssh with the guac tool I get "Connected to Guacamole. Waiting for response..." If I go to my router logs, I see that the connect is authd correctly, but immediately closes the connection with
dropbear[25710]: Exit (USER) from <GUAC_UIP:46318>: Exited normally
I already have a ticket open on the ASUS side of things, but is there any way to get more logs on what might be causing the connection to made and close immdiatly?
Sorry if this is not specific to the guac-install part of this forum, but there seems to be no offical easy way to open a ticket to guac themselves.
The text was updated successfully, but these errors were encountered: