On Thu, Mar 28, 2019 at 8:16 AM <[email protected]> wrote: > Nope, nothing changed in the environment that I could see. I just looked > at the other 2 servers running Guacamole 0.9.13 with my custom branding > extension, and they come up fine with no errors in the debug console. But > the new one with 1.0.0 throws that error whenever I have my extension > loaded. So what would I change to stop the error? >
The cause of the error would need to be established first. Do you see anything in the Tomcat+Guacamole logs? Turning off AV is not an option since our IT group has that locked down so > we can’t change it. > If 0.9.13 is working fine from the same machines having the same AV, then that's probably not the cause. - Mike
