Sorry just getting back to this project on getting my Site back up and running.
Ok more details, I tested that I could access my site via our Public IP from anywhere outside the network domain. The server is still up and running and I just can't reach it via the URL hostname that was created for it. And I can also reach it within the Network domain via the servers IP address. ________________________________ From: Sean Hulbert <shulb...@securitycentric.net.INVALID> Sent: Tuesday, March 25, 2025 12:35 PM To: user@guacamole.apache.org <user@guacamole.apache.org> Subject: Re: I can access IP but not the URL site. No.... Linux just about every version DNS location. However should not need to set this on the guac system DNS is more client based when accessing the portal /etc/resolve.conf is OS DNS settings assuming you have a FQDN and control over setting cname or A records /etc/hosts will override DNS Example: 1.2.3.4 guac.domain.com On your client system accessing the portal you can modify your Windows OS hosts file Example: 1.2.3.4 guac.domain.com C:\Windows\System32\drivers\etc\hosts Note you will need to open notepad in admin mode or change the permissions on the hosts file. Depending if you are running Apache or NGINX, you may need to alter configuration file to the web server name, default install should work with the above unless the person who installed it set the name in the config. Thank You Sean Hulbert Security Centric Inc. A Cybersecurity Virtualization Enablement Company StormCloud Gov, Protected CUI Environment! [cid:part1.7Ce3wKmI.Ps5ARNTF@securitycentric.net] Industry's most secure CMMC/iTAR virtual desktops! FedRAMP MIL4 in PMO Review System Award Management CAGE: 8AUV4 SAM ID: UMJLJ8A7BMT3 AFCEA San Francisco Chapter President If you have heard of a hacker by name, he/she has failed, fear the hacker you haven’t heard of! CONFIDENTIALITY NOTICE: This communication with its contents may contain confidential and/or legally privileged information. It is solely for the use of the intended recipient(s). Unauthorized interception, review, use or disclosure is prohibited and may violate applicable laws including the Electronic Communications Privacy Act. If you are not the intended recipient, please contact the sender and destroy all copies of the communication. Content within this email communication is not legally binding as a contract and no promises are guaranteed unless in a formal contract outside this email communication. igitur qui desiderat pacem, praeparet bellum!!! Epitoma Rei Militaris On 3/25/2025 9:26 AM, Brian Sorto wrote: Thank you, sorry Yes it's difficult to give more information as I didn't do the installation, and I have little Linux experience. But I'm stuck with trying to maintain it for right now. The server is setup on a localhost , OS is Monjaro. Logged into the Guac properties and guacd-hostname: localhost and guacd-port: 4822. Which I believe is where the DNS configuration would be? Hopefully that helps some. Thank you, ________________________________ From: Nick Couchman <vn...@apache.org><mailto:vn...@apache.org> Sent: Monday, March 24, 2025 12:28 PM To: user@guacamole.apache.org<mailto:user@guacamole.apache.org> <user@guacamole.apache.org><mailto:user@guacamole.apache.org> Subject: Re: I can access IP but not the URL site. On Mon, Mar 24, 2025 at 12:23 PM Brian Sorto <br...@phoenixts.com<mailto:br...@phoenixts.com>> wrote: I can access the site via IP address and ping it successfully. But the Host name I can not ping get no reply. Error when accessing the site just says "site can't be reached" Tried starting the server back up already and that didn't work. Other then that I haven't made any changes. Restarting the server isn't likely to fix DNS issues. If you can't ping the hostname, then something has gone wrong with your DNS configuration. You need to make sure that whatever controls DNS for your location has the correct DNS records such that the host name resolves to the IP address of the Guacamole server, and that the client systems are configured with the proper DNS servers, search domains, etc. It doesn't really sound like this is anything in particular gone wrong with Guacamole, specifically, but that your DNS zone has a missing or invalid record pointing your expected hostname to the IP address of the server. Unfortunately, without knowing exactly how you have DNS set up in your environment (Active Directory, BIND, dnsmasq, local Internet router, AWS Route53, Azure DNS, dynamic DNS, etc., etc.), it's a bit hard to direct you to the exactly solution to the problem you're encountering. -Nick
