[Solved] Installing throws "not signed repository" at apt update

My YunoHost server

Hardware: LXC container in own Proxmox host
YunoHost version: ?
I have access to my server : Through SSH | direct access via konsole
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes - installing it in container

Description of my issue

Hi there! Wanted to give yunohost a try but can’t get far. Tried to install yunohost with

curl https://install.yunohost.org | bash

was fine so far and after I get asked to install postfix and so on and remove root access the installation fails.

See Installation log:

[^[[1m^[[34mINFO^[[0m] Running upgrade_system
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease
Hit:3 http://ftp.debian.org/debian buster-updates InRelease
Err:4 http://forge.yunohost.org/debian buster InRelease
  403  Forbidden [IP: 80.67.172.144 80]
Reading package lists...
E: Failed to fetch http://forge.yunohost.org/debian/dists/buster/InRelease  403  Forbidden [IP: 80.67.172.144 80]
E: The repository 'http://forge.yunohost.org/debian buster InRelease' is not signed.
[^[[1m^[[31mFAIL^[[0m] Unable to update the system
[^[[1m^[[34mINFO^[[0m] Installation logs are available in /var/log/yunohost-installation_20220318_205349.log

apt update

apt update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.debian.org/debian buster InRelease        
Hit:3 http://ftp.debian.org/debian buster-updates InRelease
Err:4 http://forge.yunohost.org/debian buster InRelease
  403  Forbidden [IP: 80.67.172.144 80]
Reading package lists... Done
E: Failed to fetch http://forge.yunohost.org/debian/dists/buster/InRelease  403  Forbidden [IP: 80.67.172.144 80]
E: The repository 'http://forge.yunohost.org/debian buster InRelease' is not 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.

Please tell me its because of install in container or what else. Thanks!

Did the same command again - working now…

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