Can't access the specific website after configuration in Netgate Pfsense
-
Can't access my.anydesk.com after configuration in Netgate Pfsense, can anyone help me, where do I start looking to get back access again?
-
Just tested :
Since I don't know anything about your setup, I can tell you what's mine : default settings, and it will work.
-
@tiger-0 said in Can't access the specific website after configuration in Netgate Pfsense:
after configuration in Netgate Pfsense
After what configuration exactly?
-
@stephenw10 We use a default configuration, i was able to access again the website but now I can't connect again. What could be the problem here?
Thank you
-
@tiger-0 said in Can't access the specific website after configuration in Netgate Pfsense:
What could be the problem here?
Don't take my question wrong, but : how should we know ?
For example, does the host name resolve ?
Can you ping the host name ? Can you ping the IP 138.201.173.252 ?
Looks like the host is somewhere in Germany :
traceroute to 138.201.173.252 (138.201.173.252), 64 hops max, 40 byte packets 1 192.168.10.1 (192.168.10.1) 0.778 ms 0.351 ms 0.364 ms 2 80.10.239.117 (80.10.239.117) 8.110 ms 9.101 ms 9.254 ms 3 ae119-0.ncbor202.rbci.orange.net (80.10.154.10) 26.951 ms 26.929 ms 26.84 5 ms 4 ae42-0.nipoi202.rbci.orange.net (193.252.100.30) 31.844 ms 55.471 ms 48.8 37 ms 5 * 193.252.137.14 (193.252.137.14) 26.370 ms 26.535 ms 6 ae-26.a00.parsfr05.fr.bb.gin.ntt.net (129.250.66.141) 29.471 ms 27.023 ms 26.499 ms 7 ae-14.r21.parsfr04.fr.bb.gin.ntt.net (129.250.2.70) 39.564 ms 29.157 ms 27.192 ms 8 ae-11.r21.frnkge13.de.bb.gin.ntt.net (129.250.5.26) 36.987 ms 548.770 ms 1036.858 ms 9 ae-8.r01.frnkge13.de.bb.gin.ntt.net (129.250.6.51) 37.091 ms 37.146 ms 36.995 ms 10 213.198.82.130 (213.198.82.130) 39.688 ms 39.676 ms 39.485 ms 11 core23.fsn1.hetzner.com (213.239.252.38) 42.600 ms core24.fsn1.hetzner.com (213.239.252.42) 41.701 ms core23.fsn1.hetzner.com (213.239.252.38) 54.206 ms 12 spine3.cloud2.fsn1.hetzner.com (213.239.239.134) 81.651 ms 61.454 ms 42.313 ms 13 * * * 14 16335.your-cloud.host (49.12.27.170) 41.932 ms 41.961 ms 41.716 ms 15 * * *If able, set up a VPN and try again.
-
Yup, we need more information to even start guessing. How exactly is it failing?
If you're running a default config though there's not much to go wrong.
Steve
-
@stephenw10 Hi,
Sharing the screesnshot of the configuration in this temp link https://we.tl/t-7nJ3hozyy0
Also the ping and traceroute results.
Hoping that you could help me.
-
The IPv4 is ok. So resolving - DNS, works fine.
The traceroute also 'knows' there is an end point.
The (a) reasons you can not connect : your WAN IP isn't accepted.
You can exclude this reasons very easily : change your WAN IP ..... or use a VPN. -
OK, so you have Squid running in transparent mode. That's certainly not default.
Does it connect OK without Squid?
Steve
-
@stephenw10 said in Can't access the specific website after configuration in Netgate Pfsense:
so you have Squid running
Wt*** ?!?
Couldn't you just post images like :
The issue would have been solved in a couple of seconds. That is, for us.
For you it would have been solved after you know how it set up 'Squid'.
