search

flcontainers / guacamole

A Docker Container for Apache Guacamole, a client-less remote desktop gateway. It supports standard protocols like VNC, RDP, and SSH over HTML5. For x64, arm64 and ppc64le.
https://hub.docker.com/r/flcontainers/guacamole
GNU General Public License v3.0
338 stars 65 forks source link

totp is not working #68

Closed fate8383 closed 1 year ago

fate8383 commented 1 year ago

I have tried all the recent 1.5 versions (and latest) and also testing tag all the composes working fine. I do not have logs as I used to have like login IPs, and totp is absolutely not working at all. RPI4 arm64 and VM AMD via portioner. All tried fresh installs and tried -e timezone with or without cannot validate totp.

MaxWaldorf commented 1 year ago

A new version of 1.5.0 is compiling I tried to see what could be the issu but no idea so far...

fate8383 commented 1 year ago

A new version of 1.5.0 is compiling I tried to see what could be the issu but no idea so far...

tried from new docker hub flcontainers/guacamole latest and it is not working still, no logs no totp, otherwise it is working.

MaxWaldorf commented 1 year ago

I use totp on my current install and it is working fine...

I'll try a fresh one to see...

MaxWaldorf commented 1 year ago

Tested locally... Works 100% on amd64 and arm64.

Somethng isn't right with your setup...

YannicNoe commented 1 year ago

Hey, I'm from germany and I could get totp to work. I noticed, that the log Time did not match witch my local time. So I setup the Raspberry to use the correct timezone and bound /etc/timezone and /etc/localtime from the host to the same place in the container. I did it as read only. TZ Environment variable did not work at all and I suggest to document the solution if it does work for others too.

fate8383 commented 1 year ago

Hey, I'm from germany and I could get totp to work. I noticed, that the log Time did not match witch my local time. So I setup the Raspberry to use the correct timezone and bound /etc/timezone and /etc/localtime from the host to the same place in the container. I did it as read only. TZ Environment variable did not work at all and I suggest to document the solution if it does work for others too.

yeah clearly this is timezone issue like all totp failures would lead you to :) thanks. as I mentioned in the previous tickets as well. I thought -e TZ works, but I noticed just now only updates the GUA app time so not the postgress and being postgress always in UTC breaks totp. Good catch with bounding etc/timezone, not that I will do it but it should be documented or perhaps complete fix would be more granular solution such as accepting -e TZ and apply to all apps. I have tried 3 different cpus, 3 diferent timezones all fails. I don't have an instance in UTC to test, that might have worked just fine.

MaxWaldorf commented 1 year ago

check dev branch and Testing image (currently compiling)...

MaxWaldorf commented 1 year ago

New container pushed... Should resolve incident

fate8383 commented 1 year ago

New container pushed...

Should resolve incident

Cannot test now but I see latest tag is 5 hours old, I will use the testing tag? Which is 25 min ego

MaxWaldorf commented 1 year ago

it take an hour to compile on public runners...

Shouldn't take too long from there

fate8383 commented 1 year ago

it take an hour to compile on public runners...

Shouldn't take too long from there

TOTP with tag testing does not work, tag latest does not work. with -e TZ or without as fresh install.

fate8383 commented 1 year ago

it take an hour to compile on public runners...

Shouldn't take too long from there

TOTP with tag testing does not work, tag latest does not work. with -e TZ or without as fresh install.

Tested again throughly and even other composes from docker hub. It seems like my distant amd instant is the only one not working with totp all others are working such as arms. I cannot think of why but instant is on another time zone and I am in another I doubt that this is the problem but I even tried bringing all to the same time zone and it still says verification failed try again. This is more like me problem I think. Unless there is something with the amd compile(s). Otherwise it works, thanks. Still missing the logged in IPs logs though in all of the instances.