Found the issue. Wasn't setting the requisite nginx proxy rules *face palm*.
Cannot believe I overlooked something so basic. Had you not brought it up, I
never would have thought to check that. You saved me from bashing my brains
dude. Seriously. Thank you, thank you, thank you. HTTPS is now
The only possibilities are:
* You are actually connecting to the same machine and XRDP is kicking off
one user in favor of the other.
* Something on the network is causing Guacamole to fall back to HTTP, and
you are hitting browser limits on max concurrent HTTP connections per
domain.
Guacamole
Take a peek at the docs coverying proxying guac through Nginx (and if you
already have, double-check):
http://guacamole.apache.org/doc/gug/proxying-guacamole.html#nginx
It's fairly easy for misconfiguration to result in WebSocket effectively
being blocked. Guac will then fallback to HTTP, which
Spoke too soon. I'm back to the same problem of when I'm logged in with one
user, as soon as the next user logs in (to a totally different machine),
guacamole kicks the first user. What gives, this behavior is truly bizarre.
--
Sent from:
Not seeing anything specifically related to HTTPS/fallback. Since you
mentioned that, however, I went ahead and disabled HTTPS on my nginx proxy
and that seems like it may be the culprit. I have a connection going right
now and it has been solid for the past five minutes. What settings do I need
Do you see any warnings from Guacamole in your Tomcat logs about having to
fallback to HTTP?
- Mike
On Tue, Nov 6, 2018, 21:27 doyouhas Sorry if I didn't explain the situation more clearly. The connections are
> not
> pointed at the same machine, they are pointed at different machines (ec2
>
Sorry if I didn't explain the situation more clearly. The connections are not
pointed at the same machine, they are pointed at different machines (ec2
instances). I have literally zero problem maintaining a consistent
connection connecting with a standard RDP client to the exact same instance.
Are both connections using the same RDP username? It sounds like session
management within XRDP is killing one session when a new session is
established, which is the expected behavior for multiple connections
attempting to access the same desktop session.
This isn't something within Guacamole's
Bizarre. I was finallysomehowable to get a stable connection via
guacacmole, for about twenty minutes. As soon as I added another connection,
my original connection timed out and it went in a loop where one session
would be disconnected and the other would connect. What gives?
--
Sent
On Tue, Nov 6, 2018, 16:42 doyouhas I was able to get the instances to connect via guacamole by changing the
> xrdp.ini file authentication to rdp instead of negotiate. Only problem now
> is that the connection is stable for a few minutes before crapping the bed.
> It will stay stuck in that loop
I was able to get the instances to connect via guacamole by changing the
xrdp.ini file authentication to rdp instead of negotiate. Only problem now
is that the connection is stable for a few minutes before crapping the bed.
It will stay stuck in that loop of working, then disconnecting, until I
On Tue, Nov 6, 2018 at 15:47 doyouhas wrote:
> Hey guys,
>
> I'm really confused as to why I am receiving the aforementioned error when
> trying to initiate an RDP connection. I have tested that I am able to
> connect to this machine when using the Microsoft Remote Desktop client on
> Mac.
Hey guys,
I'm really confused as to why I am receiving the aforementioned error when
trying to initiate an RDP connection. I have tested that I am able to
connect to this machine when using the Microsoft Remote Desktop client on
Mac. However when trying to access that same instance using
13 matches
Mail list logo