PHPBB package downloads fail

[Beenhakker]

Hi,

First of all: great contribution. We really needed a replacement, and you built it - fantastic.

So I was giving this a try, but the setup immediately fails when it tries to fetch the phpbb package from the internet. You get a 403. And this just not happens in your container, also at home when I try to download the same package with wget, I get the same 403 back.

So FYI: this setup no longer works :(

Downloading the same file via a browser simply works. They must have had some kind of detection mechanism installed. I also tried setting the user-agent header to something real, but still a 403.

[Beenhakker]

Hi,

Me again. I made a fork to be able to dig some further, since I really wanted to get things going, and your container is the best way to go, thus I made a PR for you to see what I did, not to merge anything.

The mysql database checks are failing, even though they are using the correct connection strings (what I printed to console) but still failing, even after altering it in the most simple way possible after testing it from the CLI myself. Anyway, I knew it way wrong altogether, since other containers I run use the same connection settings. And indeed, the container started working. I am using the internal docker host gateway to reach my database. Works fine in other setups, and even after the container runs, I tried it from the CLI, and even then it works, but for some reason your checks keep failing, thus commented them out as well.

My PR can be seen at: https://github.com/EvanDarwin/phpbb-docker/pull/2/files

The other fix for the 403 problem, since I got bored with it, is to use an artefact and copy that into the docker, thus creating fixed versions.

I also edited the build script, to do multi arch builds with buildx, since I needed an ARM based version to run.

So, to sum things up:

1. Package download 403 error on official packages? Forbidden? Seems like they restricted how packages are downloaded or from where.
2. mysql database checks are failing, incorrectly, for some reason. I am using the ip address of the docker host, which works fine in the rest of the setup. Removing the checks simply made my container run and work.
3. Am I wrong if I say that when upgrading phpbb versions, the (possible) migrations are not ran, since configure_phpbb() is skipped? Shouldn't this be automated? For example by explicitly running migrations during container startup.
4. support for multi-arch builds? Seems logical, but just a nice-to-have.

[EvanDarwin]

Hi @Beenhakker,

Thanks for bringing the 403 and health checks to my attention, I assume it's because that build has a CVE, so the archive probably got pulled. That's why I attempted to rebuild it in the first place. I'll look into this later today to fix the 403, and also to switch to buildx for ARM builds.

[Beenhakker]

Hi @EvanDarwin,

Thanks for the quick reply. If you need any help, let me know, even if it's just to work through some ideas.

Yeah, that might be it. But we're still able to download it via the browser, strangely enough, and even with user agent spoofing I failed, thus thought of another solution to get it to work today.