No, I'm just referring to the "Guacamole Proxy Parameters (guacd)"
section at the top the connection settings. It's pretty easy to
accidentally enter the hostname for the connection there instead of the
correct location in the "Parameters" section, inadvertently configuring
the connection to attempt to connect to guacd at an address that it
isn't listening, causing the error you're seeing.
If this is the case, the solution would be to edit your connection, move
the hostname and/or port to the correct spot, and hit "Save".
- Mike
On 8/6/2023 2:49 AM, André R. Basel wrote:
Hi Mike
Thanks for coming back. According to Portainer, guacd is running. In the
logs I can see RDP sessions but no mention of ssh sessions in any way.
The initial logs I gave were from guacamole.
I did not configure guacd in any way, just used default docker install.
RDP worked our the box. Looking at your comments, is there some other
configuration I need to do for SSH?
Kind regards
André Basel
027 640 2527
Sent from ProtonMail mobile
-------- Original Message --------
On 6 Aug 2023, 7:08 pm, Michael Jumper < [email protected]> wrote:
On 8/5/2023 2:14 PM, André R. Basel wrote: > Hi > > I have a simple
SSH connection: > Name: MyVM > Location: Root > Protocol: SSH > >
Hostname: IP Address > > I can access the above using Putty but
through Guacamole I get the below > > Frontend: > "The connection
has been closed because the server is taking too long to > respond.
This is usually caused by network problems, such as a spotty >
wireless signal, or slow network speeds. Please check your network >
connection and try again or contact your system administrator." > >
Logs: > "ERROR o.a.g.w.GuacamoleWebSocketTunnelEndpoint - Creation
of WebSocket > tunnel to guacd failed: java.net.ConnectException:
Connection refused > (Connection refused)" > This indicates that
guacd is either not running or not listening on the configured
address. Given the context (one connection works while another
doesn't), my guess would be that the hostname/address for the SSH
connection was inadvertently specified for the connection-specific
guacd parameters and not the network parameters of the SSH
connection. - Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
