Solved - Error 500. "PUT" /yunohost/api/update/all - Repository problems in Contabo?

My YunoHost server

Hardware: 6 vCPU Cores
16 GB RAM
200 GB NVMe
or 400 GB SSD
32 TB Traffic
Unlimited Incoming
YunoHost version: 11.2.11.3 (stable).
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Hello!
I have been using Younohost with the same machine and configuration for many months and today when trying to update packages and applications I get the following error:

Imposible actualizar la caché de APT (gestor de paquetes de Debian). Aquí tienes un volcado de las líneas de sources.list que podrían ayudarte a identificar las líneas problemáticas:
sources.list:deb http://asi-fs-u.contabo.net/debian bullseye main non-free contrib
sources.list:deb-src http://asi-fs-u.contabo.net/debian bullseye main non-free contrib
sources.list:deb http://security.debian.org/debian-security bullseye-security main contrib non-free
sources.list:deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
sources.list:deb http://asi-fs-u.contabo.net/debian bullseye-updates main contrib non-free
sources.list:deb-src http://asi-fs-u.contabo.net/debian bullseye-updates main contrib non-free
sources.list.d/yunohost.list:deb [signed-by=/usr/share/keyrings/yunohost-archive-keyring.gpg] http://forge.yunohost.org/debian/ bullseye stable
sources.list.d/extra_php_version.list:deb https://packages.sury.org/php/ bullseye main

Obteniendo las actualizaciones disponibles para los paquetes del sistema…
E: Failed to fetch http://asi-fs-u.contabo.net/debian/dists/bullseye/InRelease 403 Forbidden [IP: 213.136.72.159 80]
E: The repository 'http://asi-fs-u.contabo.net/debian bullseye InRelease' is no longer signed.
E: Failed to fetch http://asi-fs-u.contabo.net/debian/dists/bullseye-updates/InRelease 403 Forbidden [IP: 213.136.72.159 80]
E: The repository 'http://asi-fs-u.contabo.net/debian bullseye-updates InRelease' is no longer signed.

I
nano /etc/apt/sources.list

There I get the following:

deb http://asi-fs-u.contabo.net/debian bullseye main

# deb http://asi-fs-u.contabo.net/debian bullseye main

deb http://asi-fs-u.contabo.net/debian bullseye main non-free contrib
deb-src http://asi-fs-u.contabo.net/debian bullseye main non-free contrib

deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free

# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://asi-fs-u.contabo.net/debian bullseye-updates main contrib non-free
deb-src http://asi-fs-u.contabo.net/debian bullseye-updates main contrib non-free
## These are official Contabo mirrors providing faster updates for your server ##
## (the files from the official servers are synced to it) ##```

 i am very unexpected and that is why I ask for help.
I interpret that this error is that there are some repositories of "contabo" which is the company that hosts the VPS and apparently does not work and is a problem of them.
My question is... what repositories can I put now?
I use debian 11, and doing some google searches, I think the repositories can be changed with:
I don't want to crash the system, I believe that nothing happens by changing to "official" repositories but in that file, what do you recommend me to put there? I have never had to change this until today...
Thanks

Solved.
Apparently this is not the first time this has happened to contabo and a few years ago I found a message on this forum.

Apparently the mirrors don’t keep them up to date, and someone with little experience like me can have a hard time.

The solution is to edit the file: /etc/apt/sources.list
Delete everything else related to contabo and add the “official” sources:

deb http://deb.debian.org/debian bullseye main contrib non-free
deb-src http://deb.debian.org/debian bullseye main contrib non-free

deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-free
deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib non-free

deb http://deb.debian.org/debian bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free

Anyway I will send a ticket to contabo to get it fixed.
Have a nice day

1 Like

It seems I’ve also (and again) the same problem.

Récupération des mises à jour disponibles pour les paquets du système…
W: Failed to fetch http://forge.yunohost.org/debian/dists/bullseye/InRelease Could not connect to forge.yunohost.org:80 (80.67.172.144), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.
Des erreurs se sont produites lors de la mise à jour du cache APT (gestionnaire de paquets Debian). Voici un extrait des lignes du fichier sources.list qui pourrait vous aider à identifier les lignes problématiques :
sources.list:deb http://asi-fs-d.contabo.net/debian bullseye main non-free contrib
sources.list:deb-src http://asi-fs-d.contabo.net/debian bullseye main non-free contrib
sources.list:deb http://security.debian.org/debian-security bullseye-security main contrib non-free
sources.list:deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
sources.list:deb http://asi-fs-d.contabo.net/debian bullseye-updates main contrib non-free
sources.list:deb-src http://asi-fs-d.contabo.net/debian bullseye-updates main contrib non-free
sources.list.d/yunohost.list:deb http://forge.yunohost.org/debian/ bullseye stable
sources.list.d/extra_php_version.list:deb https://packages.sury.org/php/ bullseye main

But I have access to my server only through the webadmin.
When I try to make the update, I’ve errors messages and after that the webadmin say that everything is OK 11.2.11.3 (stable)
I don’t feel enough expert to edit the file: /etc/apt/sources.l…

What’s the best idea? Whaiting Contabo answer your ticket?
Do an other ticket?

Hello,
I already knew that more people have this problem… and the truth spoils a lot because it is a very big wall to people like me inexperienced because it does not let you update anything from webadmin.

Yesterday just after writing here, I sent them a ticket, for the moment I have not had any answer… I would say that if you want, write to them so that we are more people and they will listen to us. If they fix the problem on their side, you won’t need to edit any file.

Anyway if you don’t want to wait, exactly what is your problem? you don’t have access to putty and login as ssh to edit the file? If it is a lack of knowledge, I can try to help you, within my limits because I am not an expert but I can more or less tell you the steps I have followed.

Thanks @leuros88 I’ve also create a ticket but they seems not understand the problem…and probably I don’t explain it correctly
They are talking about “a misconfiguration of the firewall could be the problem or that the port was changed”.

@Veehem
My opinion is that I think they don’t know how to “fix” the problem because by submitting the ticket it is probably a low level support until the “experts” or the contabo sysadmin look at it because they think it is a blockage by our machine.

In addition to that I looked yesterday to see if in failtoban there was any jail where I had any blocked ip, and I had nothing blocked.

So it brings here:

They even asked another customer 2 years ago to give them the credentials to fix the problem, when it is a full contabo problem.

Since yesterday with the change I made I have not had any more problems.

Maybe it’s too early to get an answer to yesterday’s ticket, if they say something, I’ll let you know here.

And as bad as it is, I would recommend you to take the step to change the repository yourself.

Make a backup of your entire server, in case you have any problems later.

Make a backup file cp .

Edit the file I put above and add those repositories.

Then restart the server from the webadmin or from the account panel.

I would also offer to help you by discord and remote desktop but, I am a “random” person you don’t know me and I will have to see your machine ip and credentials… it would not be a good option for security reasons, but if you look too desperate I would help you with good intentions, but if you don’t know me, I would be happy to help you.

Thank you @leuros88 After some mails & misunderstanding , I got just now this answer:

I’m forwarding your email to our technical department for further processing. You will receive an answer as quickly as possible, but in the meantime we kindly ask for your patience.

So, your “opinion” seems right :slight_smile:
I’ll wait because I’m not expert enough to edit the file. I’m only working with the Admin Panel

Finally they listen to us :smiley:
Let us know if they tell you anything or solve the problem. We can’t be the only ones who have this problem :rofl:, we will help more people.

I don’t know if they 're listening to us, but it seems the are reading you :rofl:
Contabo answer:

The solution is to edit the file: /etc/apt/sources.list
Delete everything else related to contabo and add the “official” sources:
deb Index of /debian bullseye main contrib non-free
deb-src Index of /debian bullseye main contrib non-free
deb Index of /debian-security bullseye-security main contrib non-free
deb-src Index of /debian-security bullseye-security main contrib non-free
deb Index of /debian bullseye-updates main contrib non-free
deb-src Index of /debian bullseye-updates main contrib non-free
please provide this step and it will fix the issue.

My answer

1/ I’m not use and comfortable to edit this file and change Contabo’s setting
And 2/ More important why don’t you install the “official” sources by standard settings.
An other YunoHost’s user also on Contabo meet the same problems and I guess some other people could also be in trouble.

Wait and see… as the saying goes Lao Tseu (or Karl Marx?) :wink:

@Veehem
A couple of days ago I received a reply:

I’m forwarding your email to our technical department for further review. You will receive an answer as quickly as possible, but in the meantime we kindly ask for your patience.

I have put them just what is explained in this post.
I think they should fix it, that’s why they offer this service and if not, they should edit the file with your root password.

It doesn’t seem right to me, they have to solve the problem for everyone without modifying anything. Because… imagine that you do a formatting with their s.o. image, they will put the same file again.

Update:
I just heard back from them again:

Thank you for contacting us and letting us know.

Our team is currently working on fixing this issue.

If you have any further questions or need help, please do not hesitate to contact us.

Best regards,