This is a CentOS7 system running the downloaded install of guacamole-1.1.0 - but using the yum install guacd (guacd-1.1.0-1.el7.x86_64). Even if I have an older version, the error msg you see (Log in failed. Please reconnect and try again) is also misleading. No amount of reconnecting is going to fix this :-) Shouldn't that error literally be what guacd was reporting in the logs? Way more useful to the end-user
Oh yeah, it is behind an apache reverse proxy - so maybe that changes the error message? On Fri, Mar 13, 2020 at 8:18 AM Mike Jumper <[email protected]> wrote: > On Thu, Mar 12, 2020 at 12:39 AM Jason Haar <[email protected]> > wrote: > >> Hi there >> >> I just tried using guacamole-1.1.0 to log into an AWS Linux virtual. Type >> username and password, hit ENTER, pause and "the network connection appears >> unstable". >> >> I then looked at the guacd logs and see this >> >> guacd[13051]: Password and keyboard-interactive authentication are not >> supported by the SSH server >> >> This all makes sense. By default AWS Linux doesn't allow passwords - so >> indeed it should have failed. But as an end-user, that "network error" msg >> is confusing. >> >> Can that error be better exposed to the user? So they don't end up >> bashing their heads wondering what's going on? ie why can't the user see >> that sshd error message. >> > > Testing this myself against a build of 1.1.0, I don't see this behavior. > The message you note from guacd is logged, as would be expected, however > the error presented to the user is: > > "Log in failed. Please reconnect and try again." > > I'm not sure why you would be seeing the unstable network warning instead, > so it's worth figuring out why that is happening in your case, but it's > definitely not the intent. The intent is the above message. > > - Mike > > -- Cheers Jason Haar Information Security Manager, Trimble Navigation Ltd. Phone: +1 408 481 8171 PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
