To resolve the issue with SRWare Iron not displaying your LAN domain intranet.testdomain.ee:Problem:
1.) Setup any website/webpage in local LAN that uses a domain.
On other server/pc than localhost 127.0.0.1.
2.) In router dns forwarder/dnsmasq create domain for website/webpage.
example: intranet.testdomain.ee A record 172.17.250.112
Probably can also test with hosts file,
but that is not proper DNS, then skip nslookup check if using hosts file.
3.) Validate with nslookup that domain gets LAN webserver IP address.
I used CNAME thus shows Alias, but same issue with A record also AFAIK.
nslookup intranet.testdomain.ee
...
Non-authoritative answer:
Name: webserver.str
Address: 172.17.250.112
Address: 127.0.0.1:49342
Aliases: intranet.testdomain.ee
4.) Try said domain in browser http://intranet.testdomain.ee
EXPECTING to see website, result with Iron is:
This site can’t be reached intranet.testdomain.ee refused to connect.
Try: Checking the connection Checking the proxy and the firewall
ERR_CONNECTION_REFUSED
Problem Scope:
This problem exists on older and newest Iron version 106.
The expected result: http://intranet.testdomain.ee shows website
Happens on all other browsers I try..
Ungoogled Chromium older and newest 107.
Google Chrome and Edge. FireFox and LibreFox
Maybe this is some security setting against Man in the middle attacks?
This hinders web developers work who use LAN side testing servers with one IP and many domains.
Webserver via IP http://172.17.250.112 shows apache2 default page with also Iron.
Setting up multiple Alias IP-s for webservers is not industry standard though..
LIVE/PRODUCTION webservers all use multiple domain setups.
And if domain intranet.testdomain.ee is configured on WAN side and webserver port NAT-ed.
Then DNS must point to WAN IP for Iron to show website.
Or VPN must be used for Iron to appear to approach website from WAN IP.
This is not desired workaround as LAN side development websites should not be accessible via WAN ip.
How to resolve?
What Iron config setting might cause this issue?
Browser Settings: Visit chrome://flags in Iron and disable DNS over HTTPS or experimental flags affecting DNS.
Direct A Record: Use an A record instead of CNAME in your DNS setup for the LAN domain.
Verify Virtual Hosts: Ensure your webserver is configured to handle requests for intranet.testdomain.ee.
Hosts File Test: Add the domain to your local hosts file to bypass DNS temporarily and confirm it's a browser issue.
Check Firewall: Ensure no firewall or proxy settings are blocking the connection.
If these don't resolve the issue, contact SRWare support for specific guidance.
Statistics: Posted by HalfWolf — Thu Dec 12, 2024 11:32 am