What do you see in your guacd logs for RDP (with debug-level logging)?

On Mon, Feb 20, 2023, 10:11 AM Pablo <[email protected]>
wrote:

> correct, I get the same error in my environment, RDP doesn't work, I can't
> log to report.
>
> > El 20 feb. 2023, a la(s) 14:09, Michael Jumper <[email protected]>
> escribió:
> >
> > On Mon, Feb 20, 2023 at 6:02 AM Nick Couchman <[email protected]> wrote:
> >>
> >>> On Mon, Feb 20, 2023 at 8:43 AM Pablo <
> [email protected]> wrote:
> >>>
> >>> Hello
> >>> guacamole 1.5.0 and guacd 1.5.0 docker does not work for me vnc only
> with ssh, guacamole 1.5.0 and guacd 1.4.0 works perfect.
> >>> What can be ?
> >>
> >> You need to provide more detail than this and do some investigation on
> >> your own to help figure out the problem. It's not even clear to me
> >> which protocols work in 1.4.0 vs. 1.5.0 for you.
> >>
> >> Look at the container logs to see what messages guacd is giving you,
> >> and, if those aren't clear or you need help interpreting them, feel
> >> free to post back, here.
> >>
> >
> > Testing this myself, I also see connection failures when using the
> > "guacamole/guacd:1.5.0" image with VNC connections:
> >
> >    guacd[99]: ERROR:        Unable to connect to VNC server.
> >
> > I do not see this behavior with the "guacamole/guacd:1.4.0" image nor
> > with a local build of 1.5.0... It could be something related to the
> > image now using Alpine, but not sure what that could be at the moment.
> > We do globally override LDFLAGS during the build to ensure musl's
> > stack size matches glibc's default, so that's probably not it.
> > LibVNCServer did recently release 0.9.14, but forcing the build to use
> > 0.9.13 doesn't affect the behavior, and 0.9.13 is what I have locally.
> >
> > Something specific to the new image appears to be resulting in
> > rfbInitClient() failing.
> >
> > - 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]
>
>

Reply via email to