On Mon, Apr 3, 2017 at 4:39 PM, youpiyo <[email protected]> wrote: > Hi, Mike, > > Thanks for your answer. I investigated, the log and you right the version in > the syslog is correct: > "Apr 3 18:37:13 youpi guacd[1574]: Guacamole proxy daemon (guacd) version > 0.9.12-incubating started > Apr 3 18:37:13 youpi guacd[1573]: Starting guacd: guacd[1574]: > INFO:#011Guacamole proxy daemon (guacd) version 0.9.12-incubating started > Apr 3 18:37:13 youpi guacd[1576]: Listening on host 127.0.0.1, port 4822 > Apr 3 18:37:13 youpi guacd[1573]: SUCCESS > " > in the man guacd, I have "version 0.9.11-incubating" I guess the manual > wasn't updated.
Yes. > > Regarding the client, yes I cleared the cash, and I just tried with firefox > which I never use anymore: > <http://apache-guacamole-incubating-users.2363388.n4.nabble.com/file/n718/Clipboard01.jpg> > so I guess the version present client side is not correct. > The version should read "0.9.12-incubating" if the latest release has been deployed. If you're seeing an older number, then an older version is being used. If you're certain that the new .war is in place, and that browser cache is cleared or not applicable, then it may be that Tomcat simply hasn't deployed the new .war, and the contents of the ".../webapps/guacamole/" directory are from your old version. Please try: 1) Stop the Tomcat service 2) Remove the ".../webapps/guacamole/" directory, such that the "webapps" directory contains the new .war file only 3) Start the Tomcat service 4) Wait a bit for Tomcat to extract the .war, and verify that the directory has been recreated That may bring things up to date.
