Unabletoupdateparrot-APTkeyerror/websitefails

Briefly describe your issue below:

First, let me apologize for the title of the topic. 50 characters is really not nearly enough for a concise yet brief statement of the problem in the subject line. Plus it acts like it’s really stopping after only 25 characters. Eliminating all the spaces was the only way to put the relevant information in there. Hope y’all can decode that mess…

I logged on today, and realized it’s been at least a couple of weeks since my last update. So, before I went to do any “real work” I decided to get the update done. What was supposed to take ~10 minutes has now turned into an ordeal that’s gone on over an hour now. Here is the error I’m getting from apt:

┌─[(redacted)@(redacted)]─[~]
└──╼ $sudo apt update
[sudo] password for happyoutkast:
Hit:1 https://repo.skype.com/deb stable InRelease
Err:2 https://deb.parrot.sh/parrot rolling InRelease
Could not connect to deb.parrot.sh:443 (2604:a880:cad:d0::5ed:5001). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (198.251.90.161). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (2604:a880:400:d1::7c7:f001). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (165.227.40.43). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (178.128.183.175). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (2604:a880:2:d0::22ac:7001). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (142.93.8.207). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (198.98.49.91). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (209.141.60.226). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (2605:6400:10:669:aaaa:feed:dead:beef), connection timed out Could not connect to deb.parrot.sh:443 (2605:6400:20:795:aaaa:feed:dead:beef), connection timed out
Err:3 https://deb.parrot.sh/parrot rolling-security InRelease
Unable to connect to deb.parrot.sh:https:
Reading package lists… Done
Building dependency tree
Reading state information… Done
3 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
W: Failed to fetch https://deb.parrot.sh/parrot/dists/rolling/InRelease Could not connect to deb.parrot.sh:443 (2604:a880:cad:d0::5ed:5001). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (198.251.90.161). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (2604:a880:400:d1::7c7:f001). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (165.227.40.43). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (178.128.183.175). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (2604:a880:2:d0::22ac:7001). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (142.93.8.207). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (198.98.49.91). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (209.141.60.226). - connect (111: Connection refused) Could not connect to deb.parrot.sh:443 (2605:6400:10:669:aaaa:feed:dead:beef), connection timed out Could not connect to deb.parrot.sh:443 (2605:6400:20:795:aaaa:feed:dead:beef), connection timed out
W: Failed to fetch https://deb.parrot.sh/parrot/dists/rolling-security/InRelease Unable to connect to deb.parrot.sh:https:
W: Some index files failed to download. They have been ignored, or old ones used instead.
┌─[(redacted)@(redacted)]─[~]
└──╼ $

Additionally, when I try to go to the website via chrome (https://www.parrotsec.org), the page refuses to load due to an invalid certificate error. According to google chrome, the certificate expires today (you would think there would be a grace period, or a way to get around this error, but google just refuses to let me see the page with no link to proceed anyway which is usually found when clicking "advanced. It was only by some minor miracle that I was able to even get to this website, as http://parrotlinux.org didn’t seem to want to load either. I’m guessing this forum is on a different server…

What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)

Security edition, v 4.7, amd64, with a custom kernel (updates worked fine previously with this kernel, v5.3.6 built from kernel.org stable sources). Additionally, my uname -a output:

Linux (redacted) 5.3.6-nopreempt+a6-1-custom #1 SMP Wed Oct 16 02:26:23 EDT 2019 x86_64 GNU/Linux

What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)

Debian standard ncurses interface, originally parrot security v4.5. This system has been installed and operational for at least 9 months.

Configured to multiboot with other systems? (yes / no)

yes, with windows 10, until steam play gets better support for FSX steam edition under linux

If there are any similar issues or solutions, link to them below:

None that are current, everything is over a year old with irrelevent/out of date fixes or data.

If there are any error messages or relevant logs, post them below:

Already posted above in OP, more will be added below this line upon request.

Hello @happyoutkast :slight_smile:

As far as I am aware, That is true & We apologize for the inconvenience. There is a lot going on at the moment. Furthermore, certificate Has been renewed to you should not have any more failed to establish secure connection errors with parrot domains.

Try to hit the update once again if possible, I did (at the time of writing this) without any errors.

sudo apt-get update

P.S try to avoid using any sort of VPNs or proxies or Tor while updating/upgrading the database/OS. Not that it’s necessary. but from my experience, chances are few mirrors may refuse connection because that particular IP provided by VPN or proxy or Tor to you maybe blacklisted by the mirrors that host the package on the remark of any malicious attempts on those mirrors.

Let us know how it goes!

Cheers! :blush:

1 Like

Hi Happyoutkast. Also if you ever have a problem like this again you can also change your mirrors
check out the documentation at: This text will be hidden [https://docs.parrotlinux.org/mirror-list/]

There was a problem with our servers yesterday (or CDN server) and we fixed it.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.