Cannot Update System: Error: "500" - Action: "PUT" /yunohost/api/update/all

I have searched the forum for similar issues

on

This category is for general issues(=something is broken) regarding YunoHost, NOT apps.

on

This form is written in English but feel free to write in French if you’re more comfortable!

on

What type of hardware are you using

VPS bought online

What YunoHost version are you running

YunoHost 12.1.41.2 (stable)

How are you able to access your server

The webadmin
SSH

Are you in a special context or did you perform specific tweaking on your YunoHost instance ?

I have CrowdSec and Tailscale installed but I do not believe these are interfering. My apps can access the internet fine, and CrowdSec is not blocking any Yunohost IPs.

Describe your issue

Hi. As of roughly 12 hours ago, I am suddenly unable to update my Yunohost apps and system packages from the Admin Web GUI.

When I tried to run ‘Fetch available updates’, I received the following saying I should post this on the forum. I cannot find anything specifically in the way of previous posts addressing this issue specifically.

Please let me know if it would be helpful for me to share additional information.

Thank you in advance.

Share relevant logs or error messages

Error: “500”

Action: “PUT” /yunohost/api/update/all

Error message:
Unable to update the cache of APT (Debian’s package manager). Here is a dump of the sources.list lines, which might help identify problematic lines:
sources.list:deb Index of /debian bookworm main non-free-firmware
sources.list:deb-src Index of /debian bookworm main non-free-firmware
sources.list:deb Index of /debian-security bookworm-security main non-free-firmware
sources.list:deb-src Index of /debian-security bookworm-security main non-free-firmware
sources.list:deb Index of /debian bookworm-updates main non-free-firmware
sources.list:deb-src Index of /debian bookworm-updates main non-free-firmware
sources.list.d/extra_php_version.list:deb [signed-by=/etc/apt/trusted.gpg.d/extra_php_version.gpg] Index of /php/ bookworm main
sources.list.d/yarn.list:deb [signed-by=/etc/apt/trusted.gpg.d/yarn.gpg] https://dl.yarnpkg.com/debian/ stable main
sources.list.d/tailscale.list:deb [signed-by=/usr/share/keyrings/tailscale-archive-keyring.gpg] https://pkgs.tailscale.com/stable/debian bookworm main
sources.list.d/docker.list:deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.asc] Index of linux/debian/ bookworm stable
sources.list.d/yunohost.list:deb [signed-by=/usr/share/keyrings/yunohost-bookworm.gpg] Index of /debian/ bookworm stable
sources.list.d/crowdsec_crowdsec.list:deb [signed-by=/etc/apt/keyrings/crowdsec_crowdsec-archive-keyring.gpg] https://packagecloud.io/crowdsec/crowdsec/any/ any main
sources.list.d/crowdsec_crowdsec.list:deb-src [signed-by=/etc/apt/keyrings/crowdsec_crowdsec-archive-keyring.gpg] https://packagecloud.io/crowdsec/crowdsec/any/ any main

While processing the action the server said:
Fetching available upgrades for system packages…
E: Failed to fetch http://forge.yunohost.org/debian/dists/bookworm/InRelease Could not connect to forge.yunohost.org:443 (80.67.164.12), connection timed out
E: Some index files failed to download. They have been ignored, or old ones used instead.

Can you ping forge.yunohost.org from your server? Traceroute?

Trying to curl with ipv4 and IPv6 with verbose can also be helpful:

curl -4 -Iv https://forge.yunohost.org/debian/
curl -6 -Iv https://forge.yunohost.org/debian/

Yes, ping gets a response.

I have also included the ‘traceroute’ below.

$ ping forge.yunohost.org
PING forge.yunohost.org (80.67.164.12) 56(84) bytes of data.
64 bytes from yunohost.org (80.67.164.12): icmp_seq=1 ttl=52 time=72.6 ms
64 bytes from yunohost.org (80.67.164.12): icmp_seq=2 ttl=52 time=72.9 ms
64 bytes from yunohost.org (80.67.164.12): icmp_seq=3 ttl=52 time=72.8 ms
64 bytes from yunohost.org (80.67.164.12): icmp_seq=4 ttl=52 time=72.7 ms
64 bytes from yunohost.org (80.67.164.12): icmp_seq=5 ttl=52 time=72.8 ms
^C
— forge.yunohost.org ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 72.602/72.734/72.889/0.098 ms

$ traceroute forge.yunohost.org
traceroute to forge.yunohost.org (80.67.164.12), 30 hops max, 60 byte packets
1 * * *
2 169.197.81.194 (169.197.81.194) 2.614 ms 2.599 ms 2.705 ms
3 hundredgige0-0-0-1.core2.nyc9.he.net (216.66.37.22) 1.480 ms 1.481 ms 1.494 ms
4 400ge0-0-0-14.core1.nyc5.he.net (184.104.194.249) 3.181 ms * 3.153 ms
5 * * *
6 * port-channel13.core3.nyc4.he.net (184.105.64.141) 1.054 ms *
7 * * *
8 * be7.core3.par2.he.net (184.104.194.213) 75.251 ms *
9 * be1.core3.par3.he.net (184.104.196.231) 73.478 ms *
10 gitoyen.par.franceix.net (37.49.236.190) 71.321 ms * tango.gitoyen.net (80.67.168.3) 72.337 ms
11 * * vodka.gitoyen.net (80.67.168.7) 71.487 ms
12 globenet-gw2.gitoyen.net (80.67.168.180) 72.543 ms 71.665 ms *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 port-channel5.core1.nyc9.he.net (216.66.37.20) 0.871 ms * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

curl did not succeed:

$ curl -4 -Iv Index of /debian/
curl -6 -Iv Index of /debian/

  • Trying 80.67.164.12:443…
  • connect to 80.67.164.12 port 443 failed: No route to host
  • Failed to connect to forge.yunohost.org port 443 after 31450 ms: Couldn’t connect to server
  • Closing connection 0
    curl: (7) Failed to connect to forge.yunohost.org port 443 after 31450 ms: Couldn’t connect to server
  • Trying [2001:910:1400:115::30]:443…
  • Immediate connect fail for 2001:910:1400:115::30: Network is unreachable
  • Failed to connect to forge.yunohost.org port 443 after 16 ms: Couldn’t connect to server
  • Closing connection 0
    curl: (7) Failed to connect to forge.yunohost.org port 443 after 16 ms: Couldn’t connect to server

Hmm. I would retry disabling tailscale if you can.

I will give this a shot… do you mean disabling Tailscale itself, as well as the apt repo? What leads you to believe Tailscale is interfering? Does either curl or traceroute allude to something I may be missing? Thanks again. Will report back.

Can you try

ip route get 80.67.164.12

Yes:

$ ip route get 80.67.164.12
80.67.164.12 via 144.XXX.XXX.1 dev ens3 src 144.XXX.XXX.86 uid 4286
cache

Indeed, the issue doesn’t seem related to tailscale…
Same route for

ip route get 8.8.8.8

Yes, same route:

$ ip route get 8.8.8.8
8.8.8.8 via 144.XXX.XXX.1 dev ens3 src 144.XXX.XXX.86 uid 4286
cache

I am on a VPS. I wonder if there is a provider level issue between my hosting provider and the Yunohost hosting provider?

To follow up, disabling Tailscale did not do anything to fix it.

I am sort of at a loss myself. And now with these critical vulnerabilities requiring updates, I find myself stuck and unable to upgrade.

Should I just nuke my entire server and try starting over from scratch?

Really hoping I do not have to do that but I cannot for the life of me figure out why I cannot upgrade app or system packages.

Thanks again.

I have done nothing since my last post a little while ago, however, I just logged in to check the web GUI on the administration interface… updates were available and everything ran without error. As if it was back to normal.

It is relieving, but at the same time, puzzling how I was presented with this impediment over the past few days.

I will continue to monitor this as I am unsure what other additional information I can provide that may be useful to further diagnosing this odd issue.

thanks

I have exactly the same issue: running on a VPS, getting a 500 error as well. Curl to yunohost works fine, but given the statement I would suspect there is an issue with yarnpkg. However, this gives a HTTP/2 200 as well, so connectivity is not the issue.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https:// dl. yarnpkg. com/debian stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 62D*****

E: Failed to fetch https:// dl. http:// yarnpkg. com/debian/dists/stable/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 62D*****

E: Some index files failed to download. They have been ignored, or old ones used instead.

@krispek
Your issue is different: see