GoldenEye22

I am been using Apache Guacamole for a few years now a reverse-proxy to access my unraid server from anywhere. Recently within the past month since that was the last time I can confirm it worked, I am now getting nginx error in log. I replaced "mydomain", "myip", "myguacamole" below for privacy from nginx error.log. I have been messing with this for a couple hours originally I had the guacamole.subdomian.conf set up slightly different, but no variations have helped. Note: my nextcloud and boinc reverse-proxy are working fine with nginx, boinc even uses guacamole. 2021/01/25 03:21:27 [error] 471#471: *2 connect() failed (111: Connection refused) while connecting to upstream, client: myip, server: mydomainguacamole.*, request: "GET / HTTP/2.0", upstream: "http://guacamoleip:8080/", host: "mydomainguacamole.duckdns.org" 2021/01/25 03:21:28 [error] 471#471: *2 connect() failed (111: Connection refused) while connecting to upstream, client: myip, server: mydomainguacamole.*, request: "GET /favicon.ico HTTP/2.0", upstream: "http://guacamoleip:8080/favicon.ico", host: "mydomainguacamole.duckdns.org", referrer: "https://mydomainguacamole.duckdns.org/" Originally I used this and got similar errors in log: 2021/01/25 03:03:04 [error] 481#481: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: myip, server: mydomainguacamole.*, request: "GET / HTTP/2.0", upstream: "http://unraidserverip:8089/", host: "mydomainguacamole.duckdns.org" 2021/01/25 03:03:04 [error] 481#481: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: myip, server: mydomainguacamole.*, request: "GET /favicon.ico HTTP/2.0", upstream: "http://unraidserverip:8089/favicon.ico", host: "mydomainguacamole.duckdns.org", referrer: "https://mydomainguacamole.duckdns.org/" Anyone else seeing this recently, did security parameters change for ApacheGuacamole recently that I missed? EDIT: SOLVED By blowing away the ApacheGuacamole AppData and reinstalling the application this issue was resolved.