OpenSSL problems

Imho, something is wrong with DNS on your router (192.168.0.1)

please post:

dig @9.9.9.9 upwork-usw2-desktopapp.upwork.com
[chawila@devTool ~]$ dig @9.9.9.9 upwork-usw2-desktopapp.upwork.com

; <<>> DiG 9.16.13 <<>> @9.9.9.9 upwork-usw2-desktopapp.upwork.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

What about

dig @1.1.1.1 upwork-usw2-desktopapp.upwork.com

?

[chawila@devTool ~]$ dig @1.1.1.1 upwork-usw2-desktopapp.upwork.com

; <<>> DiG 9.16.13 <<>> @1.1.1.1 upwork-usw2-desktopapp.upwork.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

[chawila@devTool ~]$ dig @8.8.8.8 upwork-usw2-desktopapp.upwork.com

; <<>> DiG 9.16.13 <<>> @8.8.8.8 upwork-usw2-desktopapp.upwork.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

To me, this looks like your ISP is blocking DNS queries. :face_vomiting:

Me too. Can you disconnect your router from the power for a minute and the connect it again? I donā€™t have high hopes, but maybe something happensā€¦

1 Like

You mean restart it?

Yes, but completely disconnect it from the power for a minute.

Could really help I guess. Somehow the DNS cache on the router or so seems to be screwed up.

Just did and the results are the same.
iā€™m using a wireless modem it uses simcard.

it generates new IP on every reboot.

This is why I told you how to configure NetworkManager to use nameservers of your choice.
The settings of the router would not matter then.

Please try:

dig @208.67.222.222 upwork-usw2-desktopapp.upwork.com -p 443

443 should go through i hope.

@Nachlese i did try that and it stopped my internet. or mybe i did it the wrong way. perhaps you can assist on how.

@moson here is the results:

[chawila@devTool ~]$ dig @208.67.222.222 upwork-usw2-desktopapp.upwork.com -p 443

; <<>> DiG 9.16.13 <<>> @208.67.222.222 upwork-usw2-desktopapp.upwork.com -p 443
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32553
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;upwork-usw2-desktopapp.upwork.com. IN	A

;; ANSWER SECTION:
upwork-usw2-desktopapp.upwork.com. 300 IN A	104.18.89.237
upwork-usw2-desktopapp.upwork.com. 300 IN A	104.18.90.237

;; Query time: 246 msec
;; SERVER: 208.67.222.222#443(208.67.222.222)
;; WHEN: Wed Apr 28 23:19:41 SAST 2021
;; MSG SIZE  rcvd: 94

voila. at least it resolves the correct address with that DNS.

Now Iā€™m not sure if you can also put a port number into the DNS settings in networkmanager.
maybe @Nachlese knows.

no, I donā€™t :wink:

Iā€™m just watching here, interested ā€¦

Booom!!!
i changed the nameserver to 208.67.222.222 and it workedā€¦


EDIT

But the strange thing is that i tried 1.1.1.1 and 8.8.8.8 earlier/yesterday and it didnā€™t work.

Should i mark it as solved or the error will come again?

So it looks like they donā€™t block port 53 per se, but only certains DNS provider addresses.

Can you do (Iā€™m just curious now):

dig @208.67.222.222 upwork-usw2-desktopapp.upwork.com
[chawila@devTool ~]$ dig @208.67.222.222 upwork-usw2-desktopapp.upwork.com

; <<>> DiG 9.16.13 <<>> @208.67.222.222 upwork-usw2-desktopapp.upwork.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32228
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;upwork-usw2-desktopapp.upwork.com. IN	A

;; ANSWER SECTION:
upwork-usw2-desktopapp.upwork.com. 300 IN A	104.18.89.237
upwork-usw2-desktopapp.upwork.com. 300 IN A	104.18.90.237

;; Query time: 236 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Wed Apr 28 23:29:58 SAST 2021
;; MSG SIZE  rcvd: 94

Ok, well, then just use that DNS server for the momentā€¦

You mean i should leave it like this for now?