I got the browser warning (regarding the certificate?) which I dismissed.
Then I got a timeout like when I tried to reach mozilla.org directly. mozilla.org is also automatically inserted as the browser URL.
I think I canât help you with that. I would switch RED to WWAN just to make sure itâs not related to my ISP. I canât explain why ipfire should filter websites when itâs not supposed to and donât come up in the logs.
First of all, do you have set your ipfire as primary ntp server of your network? (and if yes, do you set the ntp server at your dhcp options tab?)
On your clients where you try to access mozilla.org
just to eliminate possible errors, do you have checked the local time and date settings on your clients?
On your clients, where you have set your proxy settings? do you have set it in the OS proxy settings or in the browser settings? - If not, you can try it again and set the proxyserver also at the browser settings tab.
Setting up the proxy also in the browser (instead of not just in the OS) did not change anything.
Switching between âTransparent on Greenâ on and off in the IPFire proxy configuration did also not change anything.
The local time of my clients seems to be the correct time of my time zone.
What do you mean by changing the port? Just enter a port other than 800 for âproxy portâ in the IPFire configuration? Which should I use?
I am afraid I donât know how to do this⌠As I said, the network and firewall here was setup by an external contractor. I am trying to get hold of them since last weekâŚ
When running nslookup on an ipfire shell, we realised that the used server was 127.0.0.1.
So we changed this in /etc/resolv.conf to: nameserver 1.1.1.1
We then restarted IPFire via the browser interface and from there on it worked.
Could anybody explain to me what has happened here?
What is the difference between the DNS server set in /etc/resolv.conf and those (primary and secondary) set in the Network -> Assign DNS-Server?
No I donât know. That shoudnât happen. As arne said the change will be gone after a reboot and as long as you donât write a script that changes it at every boot time you will have to redo the chnage every time again. Also I donât think itâs an good idea. In my understanding the change will make the system not to use unbound as dns server anymore and you shouldnât have the ability to use the url filter etc.