dudepron Posted July 28, 2021 Share Posted July 28, 2021 I've tried without and with --no-allow-insecure-repositories and --allow-unauthenticated Cert issue on the remote? ns1@ns1:~$ sudo apt-get update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Ign:4 https://apt.armbian.com buster InRelease Err:5 https://apt.armbian.com buster Release Redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden [IP: 173.45.128.12 443] Reading package lists... Done E: The repository 'https://apt.armbian.com buster Release' no longer has a Release file. 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. ns1@ns1:~$ sudo apt-get update --no-allow-insecure-repositories Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Ign:4 https://apt.armbian.com buster InRelease Err:5 https://apt.armbian.com buster Release Redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden [IP: 173.45.128.12 443] Reading package lists... Done E: The repository 'https://apt.armbian.com buster Release' no longer has a Release file. 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. ns1@ns1:~$ sudo apt-get update --allow-unauthenticated Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://httpredir.debian.org/debian buster InRelease Hit:3 http://httpredir.debian.org/debian buster-updates InRelease Ign:4 https://apt.armbian.com buster InRelease Err:5 https://apt.armbian.com buster Release Redirection from https to 'http://armbian.tnahosting.net/apt/dists/buster/Release' is forbidden [IP: 173.45.128.12 443] Reading package lists... Done E: The repository 'https://apt.armbian.com buster Release' no longer has a Release file. 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. ns1@ns1:~$ 0 Quote Link to comment Share on other sites More sharing options...
Solution lanefu Posted July 29, 2021 Solution Share Posted July 29, 2021 Change https://apt.armbian.com to http and see if that helps 0 Quote Link to comment Share on other sites More sharing options...
dudepron Posted July 29, 2021 Author Share Posted July 29, 2021 It did. Not sure why I didn't think of that. 0 Quote Link to comment Share on other sites More sharing options...
lanefu Posted July 29, 2021 Share Posted July 29, 2021 yeah sorry about the trouble.. I/we had some bad defaults with that, and I had changed them on the direct server, and I think your older install at the apt setup that way. 0 Quote Link to comment Share on other sites More sharing options...
MichaIng Posted July 30, 2021 Share Posted July 30, 2021 But IMO connecting via HTTPS is preferred, while in this case a redirection to plain HTTP should simply not be done? The targets are available via HTTPS as well (https://armbian.systemonachip.net/apt/, https://armbian.tnahosting.net/apt/ etc.), some mirrors even enforce it (http://imola.armbian.com/), so wouldn't it be best to redirect without scheme to preserve HTTP or HTTPS depending on the initial client connection? 0 Quote Link to comment Share on other sites More sharing options...
lanefu Posted July 30, 2021 Share Posted July 30, 2021 Lol i got a lot of feedback about https being an undesirable default. Major reason being those on small connections heavilly rely on caching proxies to make life better. And yes persisting protocol based on request would be ideal. How are you at python? https://github.com/armbian/dl-router/issues/2 0 Quote Link to comment Share on other sites More sharing options...
xwiggen Posted August 2, 2021 Share Posted August 2, 2021 On 7/30/2021 at 11:52 PM, lanefu said: Lol i got a lot of feedback about https being an undesirable default. Major reason being those on small connections heavilly rely on caching proxies to make life better. And yes persisting protocol based on request would be ideal. How are you at python? https://github.com/armbian/dl-router/issues/2 Same script, one for http mirrors (port 80) and one for https mirrors (port 443). 0 Quote Link to comment Share on other sites More sharing options...
MichaIng Posted August 3, 2021 Share Posted August 3, 2021 I would say same script, but changing the list to not include scheme, and then prepend scheme of client request to target mirror: https://github.com/armbian/dl-router/blob/master/app/mirrors.yaml I also see that mirrors.netix.net entry is with HTTP, but it has forced redirect to HTTPS, at least after receiving the HSTS header once. I'm learning Python by doing little contributions here and there, so I'll have a look if I can add this feature :). 1 Quote Link to comment Share on other sites More sharing options...
MichaIng Posted August 3, 2021 Share Posted August 3, 2021 I created a pull request: https://github.com/armbian/dl-router/pull/14 1 Quote Link to comment Share on other sites More sharing options...
lanefu Posted August 4, 2021 Share Posted August 4, 2021 7 hours ago, MichaIng said: I created a pull request: https://github.com/armbian/dl-router/pull/14 Great fixes @MichaIng code is deployed. Thank you so much! 1 Quote Link to comment Share on other sites More sharing options...
Swastik verma Posted May 20, 2022 Share Posted May 20, 2022 (edited) On 7/29/2021 at 9:02 PM, lanefu said: Change https://apt.armbian.com to http and see if that helps What do you mean by change to?, and what do i change and from where do i change? Please explain 🙏 Edited May 20, 2022 by Swastik verma 0 Quote Link to comment Share on other sites More sharing options...
dudepron Posted May 22, 2022 Author Share Posted May 22, 2022 @Swastik verma the apt sources config file... /etc/apt/sources.list By default it uses https. The fix for me was to change it to http. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.