Error when update the system - apt update

robylix
robylix Posts: 2 ✭✭
edited June 2021 in Linux only

When update the system ( linux mint 19.1) i look this error:

E:Failed to fetch https://linux.teamviewer.com/deb/dists/stable/InRelease  403  Forbidden [IP: 52.84.221.31 443], E:The repository 'https://linux.teamviewer.com/deb stable InRelease' is not signed.

into repository file there is: deb https://linux.teamviewer.com/deb stable main

Comments

  • DanielForgie
    DanielForgie Posts: 2 ✭✭

    I just got the same error on my Rasbperry Pi 3b+ :


    Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]

    Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]

    Err:3 https://linux.teamviewer.com/deb stable InRelease

     403 Forbidden [IP: 54.230.18.92 443]

    Get:4 http://archive.raspberrypi.org/debian buster/main armhf Packages [375 kB]

    Reading package lists... Done

    E: Failed to fetch https://linux.teamviewer.com/deb/dists/stable/InRelease  403  Forbidden [IP: 54.230.18.92 443]

    E: The repository 'https://linux.teamviewer.com/deb stable InRelease' is no longer signed.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

  • PaddyLandau
    PaddyLandau Posts: 14 ✭✭

    Likewise here on Ubuntu 20.04, except that it's http not https, and the IP address is different:

    Failed to fetch http://linux.teamviewer.com/deb/dists/stable/InRelease  403  Forbidden [IP: 52.84.138.16 80]

    The repository 'http://linux.teamviewer.com/deb stable InRelease' is not signed.

    I deleted the PPA and reinstalled TeamViewer, because the .deb is supposed to add the repository, but it didn't add the repository.

    I re-added the PPA from the backup, and the error persists.

    For now, I've commented out the PPA to prevent the errors, but until this is fixed, I'll have to manually check for TeamViewer updates.

  • l0f4r0
    l0f4r0 Posts: 8 ✭✭

    Same thing here on Debian 10 (stable).


    # apt update

    [...]                                                                                                                              

    Err:6 hxxps://linux.teamviewer[.]com/deb stable InRelease                                                                                                                                                          

     403 Forbidden [IP: 52.222.174.18 443]

    [...]

    E: Failed to fetch hxxps://linux.teamviewer[.]com/deb/dists/stable/InRelease 403 Forbidden [IP: 52.222.174.18 443]

    E: The repository 'hxxps://linux.teamviewer[.]com/deb stable InRelease' is no longer signed.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.


    No better after typing `̀# teamviewer repo default`.


    Manual navigation to hxxps://linux.teamviewer[.]com/deb with my browser leads me to an error XML page stating "AccessDenied".


    NB: I've sanitized the links above because my post is not authorized otherwise...

  • jdrch
    jdrch Posts: 10 ✭✭

    Same problem here on Debian Buster. This is the 2nd major repo issue in 3 months. Not exactly confidence inspiring.

    TeamViewer on 5 Windows PCs, 4 Linux PCs, & 2 Android smartphones

  • Esther
    Esther Posts: 4,052 Former Community Manager

    Hi @robylix @DanielForgie @PaddyLandau @l0f4r0 @jdrch

    Thanks a lot for your reports!

    The Linux Crew worked on this all morning and was able to resolve it 🙌

    Can you try again and provide us feedback here?

    Thanks and best,

    Esther

    Former Community Manager

  • robylix
    robylix Posts: 2 ✭✭
  • Esther
    Esther Posts: 4,052 Former Community Manager

    Thanks for the feedback @robylix ! Glad to hear it is working again 🙌

    Have a great weekend ahead!

    Former Community Manager

  • l0f4r0
    l0f4r0 Posts: 8 ✭✭

    Hi @Esther,

    Indeed, it works now :)

    Thank you!

  • DanielForgie
    DanielForgie Posts: 2 ✭✭

    Yep its working now