You are here
For the last few months I've been unable to update my nextcloud LXC containers, I've read and followed 'https://packages.sury.org/php/README.txt' it kinda worked, but it didn't cause I started getting HTTP code 403 errors, (I asked about it last month here #1023) so I just deleted /etc/apt/sources.list.d/php.list to make sure automatic updates wouldn't keep me blacklisted.
I figured a month would be enough for cloudflare to remove me from whatever blacklist they put me in, so today I went ahead and recreated /etc/apt/sources.list.d/php.list, run apt-get update and got:
Err:3 https://packages.sury.org/php stretch/main amd64 Packages
Received HTTP code 403 from proxy after CONNECT
W: The repository 'https://packages.sury.org/php stretch Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://packages.sury.org/php/dists/stretch/main/binary-amd64/Packages Received HTTP code 403 from proxy after CONNECT
So at first looks seems like I'm still somehow banned, I tried with another existing debian stretch container, added the repository as per 'https://packages.sury.org/php/README.txt' and I got the exact same error, so it's not something specific from my container, and my IP changes daily so is not that either, I've tried it on another physical system and a couple existing containers at a remote location with also dynamic IP address and got the exact same result, so I'm wondering if somehow cloudflare blacklisted my entire ISP range which makes no sense so clerly something else is happening.
I've tried to create a new vm with debian stretch and after adding the repo it run apt update without errors, so there must be something either broken, outdated or missing in all my containers, but I don't have the slightest clue what that could be, so I appreciate any ideas or pointers.
To Reproduce
Steps to reproduce the behavior:
- Install fresh Debian stretch vm (or LXC container) from turnkeylinux.org
- Update sury repository as per 'https://packages.sury.org/php/README.txt'
- Run apt update
- See error
Expected behavior
apt update returns no errors.
Distribution (please complete the following information):
- Debian Stretch
- AMD 64
- packages.sury.org
I can't reproduce?!
I just launched a TurnKey v15.0 Core appliance (the only v15.x LXC appliance I have handy - shouldn't matter for the purposes of this test) and couldn't reproduce?! I'm not sure how useful it will be, but here's the process I followed:
I doubt that it will be that useful, but here's the full output of adding the sury.org repo and installing the 'php package (because this wasn't a LAMP-based appliance, it pulled in some Debian dependencies too, such as Apache):
So I'm not convinced that it has anything to do with Debian in general or TurnKey specifically.
Out of interest, have you tested the current TurnKey container? TBH, I doubt it will make any difference, but perhaps?
And regardless of whether it does, another way to go would be to transfer your data to an instance of the newer version. That has a newer PHP by default, so will support Nextcloud updates (you shouldn't need to upgrade PHP via the sury.org repo then).
PS if you do try v16.x, it needs to be unprivileged
In case you aren't aware, TurnKey v16.x containers need to be run as unprivileged. If you really need it to run privileged, be sure to enable nesting for the container or otherwise you will have problems with services not starting.
Thank you, clearly there must
Thank you, clearly there must be something different in my servers/containers, I think I'll have no choice but to migrate everything, but that's a pita...
I'll post if I find a solution before migrating.
same problem here
Are you getting the same error message?
Are you getting the same error message? I mean this one:
(The `stretch` in the path may be 'buster' or 'bullseye' depending on which base OS your system has).
If that's the case, then it's an issue with your proxy config. Please see this thread for more context.
to be honest it might have
Ah ha.
Ah ha. If you were trying to use 'stretch' and that is no longer provided, then a 404 error would be expected. FYI '404' means 'not found' (usually because a URL doesn't exist - or the server isn't serving content); '403' means "forbidden" (meaning that the server found the URL but you don't have permission to access it).
Add new comment