The connection has timed out
Have you tried https://lite.duckduckgo.com ?
Ah, lite.duckduckgo.com works. Why?
Hmmm… okay, strange, then please run curl -v https://duckduckgo.com > /dev/null
and when you paste the output, please select the text and press the </>
button in the toolbar.
There should be an option to add the security exception, either permanently or for the session. That should get you to the site. I haven’t used PaleMoon in quite a while so can’t remember what comes up with that one. Try with the IP you received as well, maybe.
= curl -v https://duckduckgo.com >/dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0*
Trying 79.125.108.55:443...
0 0 0 0 0 0 0 0 --:--:-- 0:02:09 --:--:-- 0*
connect to 79.125.108.55 port 443 failed: Connection timed out
* Failed to connect to duckduckgo.com port 443: Connection timed out
0 0 0 0 0 0 0 0 --:--:-- 0:02:09 --:--:-- 0
* Closing connection 0
curl: (28) Failed to connect to duckduckgo.com port 443: Connection timed out
spaces
Please run sudo iptables -L
= sudo iptables -L
[sudo] password for naz:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Please run sudo mtr -T -P 443 --report duckduckgo.com
= sudo mtr -T -P 443 --report duckduckgo.com phaedrus:~
Start: 2020-09-12T21:05:45+0200
HOST: phaedrus Loss% Snt Last Avg Best Wrst StDev
1.|-- fritz.box 0.0% 10 0.6 0.7 0.6 0.7 0.0
2.|-- 10.140.43.226 0.0% 10 10.1 9.6 9.3 10.1 0.3
3.|-- 138.187.18.74 0.0% 10 9.3 9.5 9.2 9.9 0.3
4.|-- 172.16.22.205 0.0% 10 9.2 9.3 8.8 9.7 0.3
5.|-- 212.101.3.173 0.0% 10 10.4 11.1 10.0 17.3 2.2
6.|-- d11sol-bbm02-x-0-0-21.sol 0.0% 10 10.3 9.9 9.4 10.9 0.5
7.|-- iwbbas-bbm02-x-0-0-3.soln 0.0% 10 10.8 10.8 10.5 11.1 0.2
8.|-- iwbbas-bbr02-et-0-0-2.4.s 0.0% 10 10.2 25.5 9.8 123.5 36.7
9.|-- ixnzrh-bbr02-ve9.solnet.c 0.0% 10 12.5 11.5 11.1 12.5 0.4
10.|-- as16509.swissix.ch 0.0% 10 11.7 11.5 11.2 11.9 0.2
11.|-- 52.93.42.42 0.0% 10 12.7 12.4 12.0 12.7 0.3
12.|-- 52.93.42.143 0.0% 10 12.0 12.1 11.2 15.5 1.2
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
24.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25.|-- duckduckgo.com 60.0% 10 38.6 36.8 35.5 38.6 1.3
I’m guessing that steps 13-25 are all duckduckgo internal, and they don’t respond to pings.
60% loss… interesting. Maybe it’s a network issue somewhere? Has it ever worked?
Worked just fine until a couple weeks ago. Still works fine on other machines here.
Just tried it for lite…
= sudo mtr -T -P 443 --report lite.duckduckgo.com
Start: 2020-09-12T21:14:57+0200
HOST: phaedrus Loss% Snt Last Avg Best Wrst StDev
1.|-- fritz.box 0.0% 10 0.6 0.6 0.6 0.7 0.1
2.|-- 10.140.43.226 0.0% 10 10.0 9.7 8.9 10.7 0.5
3.|-- 138.187.18.74 0.0% 10 10.0 9.8 9.0 10.7 0.5
4.|-- 172.16.22.205 0.0% 10 9.1 9.5 9.1 9.8 0.2
5.|-- 212.101.3.173 0.0% 10 10.3 10.2 9.5 10.7 0.4
6.|-- d11sol-bbm02-x-0-0-21.sol 0.0% 10 9.7 9.8 9.3 10.3 0.3
7.|-- iwbbas-bbm02-x-0-0-3.soln 0.0% 10 14.8 14.7 10.5 45.0 10.7
8.|-- iwbbas-bbr02-et-0-0-2.4.s 0.0% 10 69.1 16.8 9.9 69.1 18.5
9.|-- ixnzrh-bbr02-ve9.solnet.c 0.0% 10 11.5 11.5 11.0 12.0 0.4
10.|-- swissix.microsoft.com 0.0% 10 11.6 11.4 11.2 11.6 0.1
11.|-- ae22-0.icr01.zrh20.ntwk.m 0.0% 10 11.9 12.3 11.8 14.9 0.9
12.|-- be-120-0.ibr02.zrh20.ntwk 0.0% 10 22.9 23.5 22.9 25.9 0.9
13.|-- be-6-0.ibr02.fra21.ntwk.m 0.0% 10 23.5 23.7 23.2 24.7 0.4
14.|-- be-9-0.ibr02.ams30.ntwk.m 0.0% 10 22.9 23.0 22.6 23.7 0.3
15.|-- ae122-0.icr02.ams30.ntwk. 0.0% 10 22.7 24.6 22.3 33.9 3.6
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
23.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
24.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
25.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
26.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
27.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
28.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
29.|-- 40.114.177.156 0.0% 10 23.2 27.4 23.0 61.5 12.0
Unless my eyeballs need serious adjusting, Palemoon no longer offers duckduckgo on the list of search plugins, and searching for it finds nothing. Say what?
Never mind, that’s because it’s one of the default search engines in Palemoon.
OK, well, at least I have a workaround: use lite.duckduckgo.com. It looks like, at least for the moment, I’ll have to be satisfied with success. Thanks @BG405 and @pobrn for your help.
Looking on the line with WireShark, it is evident that my packets are going out to duckduckgo, but nothing comes back. Curiously, after the first SYN is sent out, a second one is sent out just 250ms later. After that it’s just TCP Retransmissions until the timeout occurs. I don’t know nuthin about the innards of TCP/IP, but that 2nd SYN seems a bit hasty to me.
That seems a little too fast indeed. Are you sure it’s the same connection?
I have several captures, all with the same timing.
Comparing the two SYN’s, aside from the checksums, in IP only Identification is different. In TCP, only TSval is different, by about 250. In particular, the TCP Seq is always 0. I have no idea if that’s correct or not.
Wireshark is showing relative sequence numbers by default. That might explain it.