# Cannot reach mozilla.org through proxy **URL:** \ **Category:** Web Proxy, URL Filter & Update Accelerator\ **Created:** [5 February 2020 17:24 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156 "2020-02-05T17:24:02Z")\ **Posts on this page:** 19\ **Page:** 2
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [10 February 2020 12:40 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/21 "2020-02-10T12:40:49Z")
I just tried 63.245.208.195 to reach [mozilla.org](http://mozilla.org). I got the browser warning (regarding the certificate?) which I dismissed. Then I got a timeout like when I tried to reach [mozilla.org](http://mozilla.org) directly. [mozilla.org](http://mozilla.org) is also automatically inserted as the browser URL. So this means that the DNS is working, right? What else could it be? ---
**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/8252_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\ **Post date:** [10 February 2020 12:46 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/22 "2020-02-10T12:46:46Z")
> [@linus](#): > > What else could it be? Upstream proxy. Check the firewall log for the ip. ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [10 February 2020 13:04 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/23 "2020-02-10T13:04:58Z")
> [@xperimental](#): > > Check the firewall log for the ip. I do not see 63.245.208.195 in my firewall log. Accessing web pages (successful or not) does not seem to put an entry into the log. I only have entries with “Proto” being 2 or UDP… ---
**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/8252_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\ **Post date:** [10 February 2020 16:46 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/24 "2020-02-10T16:46:22Z")
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. ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [10 February 2020 16:59 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/25 "2020-02-10T16:59:51Z")
All right, thanks anyway! I will try to get some local support who can hopefully resolve this. Will tell you if we have found the cause for this… ---
**Author:** ![marquand](https://community.ipfire.org/user_avatar/community.ipfire.org/marquand/32/4218_2.png) [@marquand](https://community.ipfire.org/u/marquand)\ **Post date:** [11 February 2020 07:56 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/26 "2020-02-11T07:56:03Z")
Hello Linus, I got three questions on this. 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](http://mozilla.org) > [@linus](#): > > I got the browser warning (regarding the certificate?) which I dismissed. just to eliminate possible errors, do you have checked the local time and date settings on your clients? > [@linus](#): > > I have now set forward and outgoing in the firewall options to “allowed” and disabled all firewall rules. > But the problem that I cannot reach the mentioned urls via the HTTPS proxy still remains. > > I also tried to assign the primary and secondary DNS (1.1.1.1 and 8.8.8.8 aus you suggested) and did a reboot of ipfire afterwards. But this still does not change anything. > > What else could be the cause for this? 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. > [@linus](#): > > I do not see 63.245.208.195 in my firewall log. possibly it is logged not as ip but as fqdn? ---
**Author:** ![marquand](https://community.ipfire.org/user_avatar/community.ipfire.org/marquand/32/4218_2.png) [@marquand](https://community.ipfire.org/u/marquand)\ **Post date:** [11 February 2020 08:04 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/27 "2020-02-11T08:04:55Z")
i got another idea: just for testing purposes - do you got the same error message if you change the port of the proxy - and enable/disable the transparent proxy? ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [13 February 2020 15:08 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/28 "2020-02-13T15:08:24Z")
Thanks for your suggestions. 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? > [@marquand](#): > > do you have set your ipfire as primary ntp server of your network? 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… > [@marquand](#): > > possibly it is logged not as ip but as fqdn This is what my firewall log looks like: ![Untitled-1](https://community.ipfire.org/uploads/default/original/1X/e2cbf12d943e8416fc75a401d39f982a7ea461ff.jpeg) ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [17 February 2020 15:43 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/29 "2020-02-17T15:43:21Z")
Hi everybody, it seems we solved the mystery! 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? ---
**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/8252_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\ **Post date:** [17 February 2020 15:49 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/30 "2020-02-17T15:49:12Z")
127.0.0.1 is the local recursor when - for example - your dnssec fails. ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [17 February 2020 15:51 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/31 "2020-02-17T15:51:22Z")
> [@xperimental](#): > > 127.0.0.1 is the local recursor when - for example - your dnssec fails. So do you understand why it works for me when I put `nameserver 1.1.1.1` into `/etc/resolv.conf`? Is this even a “good solution”? ---
**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\ **Post date:** [17 February 2020 15:51 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/32 "2020-02-17T15:51:37Z")
127.0.0.1 is the localhost. This means the local unbound is used as DNS Server. The servers assingned in the webgui are used from unbound. IPFire reset /etc/resolv.conf at every boot to its default so it should again not work after a restart. ---
**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/8252_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\ **Post date:** [17 February 2020 16:17 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/33 "2020-02-17T16:17:34Z")
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. ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [17 February 2020 16:21 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/35 "2020-02-17T16:21:05Z")
OK, back to square one then… 🤪 ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [17 February 2020 16:42 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/36 "2020-02-17T16:42:50Z")
One more question if I may: Does the fact that chaning the DNS in `/etc/resolv.conf` seemingly solves my problem, hint at where to search for the real cause? ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [11 March 2020 16:18 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/37 "2020-03-11T16:18:15Z")
Maybe the cause for my problem is that there is no DNS server setup for **dnsmasq**? ([https://wiki.archlinux.org/index.php/dnsmasq](https://wiki.archlinux.org/index.php/dnsmasq)) I tried to check, but my ipfire VM does not have the `/etc/dnsmasq.conf` file. How can this be configured?? Thanks! ---
**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\ **Post date:** [12 March 2020 08:06 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/38 "2020-03-12T08:06:53Z")
> [@linus](#): > > I tried to check, but my ipfire VM does not have the `/etc/dnsmasq.conf` file. > How can this be configured?? Thanks! IPFire has no dnsmasq anymore so there is no config. We have switched to unbound years ago. > **[IPFire 2.19 - Core Update 106 released - The IPFire Blog](https://blog.ipfire.org/post/ipfire-2-19-core-update-106-released)** > > This is the official release announcement for IPFire 2.19 - Core Update 106 > which comes with a number of exciting new features, many bug fixes and a few > security improvements. ---
**Author:** ![linus](https://community.ipfire.org/user_avatar/community.ipfire.org/linus/32/314_2.png) [@linus](https://community.ipfire.org/u/linus)\ **Post date:** [12 March 2020 10:49 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/39 "2020-03-12T10:49:16Z")
> [@arne\_f](#): > > IPFire has no dnsmasq anymore so there is no config. We have switched to unbound years ago. Hm, is it possible my IPFire is that old? ``` [root@ipfire /]# netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 11414/dnsmasq tcp 0 0 0.0.0.0:222 0.0.0.0:* LISTEN 2652/sshd tcp 0 0 10.16.1.254:800 0.0.0.0:* LISTEN 3776/(squid-1) udp 0 0 0.0.0.0:57927 0.0.0.0:* 3776/(squid-1) udp 0 0 0.0.0.0:53 0.0.0.0:* 11414/dnsmasq udp 0 0 0.0.0.0:68 0.0.0.0:* 11891/dhcpcd udp 0 0 192.168.2.102:123 0.0.0.0:* 2596/ntpd udp 0 0 10.16.1.254:123 0.0.0.0:* 2596/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 2596/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 2596/ntpd ``` uname -r 3.14.65-ipfire uname -v #1 SMP Tue Jun 14 06:21:39 GMT 2016 What should I do? ---
**Author:** ![anon65703081](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/90ced4/32.png) [@anon65703081](https://community.ipfire.org/u/anon65703081)\ **Post date:** [12 March 2020 11:00 UTC](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156/40 "2020-03-12T11:00:23Z")
Hi Linus, make a backup of your settings. Do a cleaninstall of Ipfire 2.25 Core 141. Restore your backup. [Previous page](https://community.ipfire.org/t/cannot-reach-mozilla-org-through-proxy/1156.md?page=1)