On Mon, Dec 19, 2022, 9:25 AM Dan Nessett <dness...@yahoo.com.invalid> wrote:
> I am still trying to figure out why guacamole is not working. I looked at > the journalctl output, but found nothing suspicious (see below for startup > journal messages). When I look at the output of journalctl after attempting > to use guacamole from a browser (i.e., http://<server external dns > name>:<external NAT port>/guacamole), there is nothing in the output from > tomcat, guacamole or apache. > > Can anyone more experienced than I see something that might give a clue > what is going wrong? The response at the browser when attempting to access > guacamole is: > > Not Found > > The requested URL was not found on this server. > ------------------------------ > Apache/2.4.29 (Ubuntu) Server at <DNS name> Port XXXXX > (I have changed the DNS name and external port number). Is it possible > that guacamole is getting confused because the internal port seen by apache > (i.e., 4443) is not the internal port used by NAT (i.e., 443). Also, is it > possible that the from address that tomcat sees is 127.0.01 might confuse > it when responding to the request? > No, this is a response from the Apache web server, not Guacamole or Tomcat. Your request is failing within Apache and thus is not reaching either of those levels. You should check your Apache logs and config to determine why your request doesn't match your configuration. - Mike
