Apache to denying requests to .well-known

[noctiswhole]

Steps To Reproduce

1. Start a laravel project
2. Create the route /.well-known/ in web.php
   Route::get('/.well-known/', function () { return view('welcome'); });
3. Start serversideup php apache docker container and mount laravel directory
4. Go to /.well-known/

Outcome

What did you expect?

Laravel welcome screen

What happened instead?

403 Forbidden
php-1 | [Wed Feb 04 22:58:51.558942 2026] [authz_core:error] [pid 131:tid 196] [client xx:21475] AH01630: client denied by server configuration: /var/www/html/public/.well-known
php-1 | - - [04/Feb/2026:22:58:51 +0000] localhost 192.168.65.1 "GET /.well-known/ HTTP/1.1" 403 239 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:146.0) Gecko/20100101 Firefox/146.0"

Affected Docker Images

serversideup/php:8.2-fpm-apache-v4.3.0

Anything else?

I have an OIDC provider built in Laravel located at /.well-known/openid-configuration. When updating to v4.3.0, the new directives prevented access to that endpoint.

[jaydrogers]

Just curious, why are you trying to get the root of /.well-known/ to return the welcome page?

I believe your goal is to access /.well-known/openid-configuration, which seems to be working for me in my test.

Here is a repo to produce this locally. View the README how to clone it down and run it:

https://github.com/jaydrogers/docker-php-649-apache-well-known

My results

[noctiswhole]

I just gave it as an example of reproducing my issue. Change the paths to /.well-known/openid-configuration and the issue persists.

I cloned your repo and I'm getting the same issue.

[jaydrogers]

Thanks for getting back quickly!

Well that's super weird that I cannot replicate it even through we're running the same version through Docker.

Things I checked:

1. I cleared my local docker cache
2. Checked it in multiple browsers (it worked)
3. Looks like you're running macOS, assuming with Docker Desktop? So am I

Could you potentially clear your cache and try again? This command will clear all local docker cache, networks, etc:

./vendor/bin/spin prune

[noctiswhole]

I tried pruning with ./vendor/bin/spin prune and I'm still getting the same error, regardless of browser or curl.

My dev machine is macOS with Docker Desktop, yes. My build and deployment OS are Linux and it's occurring there too.

[jaydrogers]

Thanks for confirming!

I'm dumbfounded why I'm not able to reproduce the issue since we have almost identical setups.

I totally believe the bug exists on your machine, but unfortunately I won't be able to submit a fix until I can replicate the issue.

I'll leave this open to see if others have any ideas why it can't be replicated.

I'm all ears in the meantime if anyone has and thoughts

[noctiswhole]

If you want, we can give you access to a new VM with the issue reproduced, and you can do whatever you need on it.

[jaydrogers]

I think I fixed it 😅

I got it to work once I created a .well-known folder. I think I had one in there for testing the route. Since I had that testing folder there, my end was resolving.

I noticed I was using DirectoryMatch instead of LocationMatch, so I made a PR to make the change: https://github.com/serversideup/docker-php/pull/652/changes

You can test this by using this image:

serversideup/php-dev:652-8.2-fpm-apache

Try that out and let me know if that worked for you!

[noctiswhole]

Awesome, that fixed it!