Summary
With MULTISITE enabled, the login page renders normally but the response carries a 404 status code.
$ curl -s -o /dev/null -w '%{http_code}\n' https://example.ddev.site/cms/wp-login.php
404The body is the real login page:
<title>Log In ‹ My Site — WordPress</title>
Logging in works, so this is a status-code issue rather than a functional one.
Scope
Only wp-login.php is affected. Other admin entry points behave correctly:
| URL |
Status |
/cms/wp-login.php |
404 |
/cms/wp-admin/ |
302 (redirect to login — expected) |
/cms/wp-admin/index.php |
302 |
/cms/wp-admin/post.php?post=4&action=edit |
302 |
/ (Blade front) |
200 |
/subsite/ |
200 |
Note it returns 302 from inside the container over plain HTTP and 404 over HTTPS through the router, which suggests the status is set by the Laravel side rather than by WordPress.
Single-site installs return 200 on the same URL. The 404 appears only after wp core multisite-convert.
Why it matters
Beyond looking wrong in devtools, a 404 on the login page misleads uptime monitoring and crawlers, and any tooling that checks status codes before following a redirect will treat the admin as broken.
Environment
Pollora v13.4.3 · WordPress 6.9.4 · PHP 8.4.20 · Laravel 13.8.0 · subdirectory multisite · DDEV, nginx-fpm
Reproduced with the fix from #296 applied (that one is a separate, blocking fatal).
https://claude.ai/code/session_01CtKVtFGujknnYGtcEEJD3x
Summary
With
MULTISITEenabled, the login page renders normally but the response carries a 404 status code.The body is the real login page:
Logging in works, so this is a status-code issue rather than a functional one.
Scope
Only
wp-login.phpis affected. Other admin entry points behave correctly:/cms/wp-login.php/cms/wp-admin//cms/wp-admin/index.php/cms/wp-admin/post.php?post=4&action=edit/(Blade front)/subsite/Note it returns 302 from inside the container over plain HTTP and 404 over HTTPS through the router, which suggests the status is set by the Laravel side rather than by WordPress.
Single-site installs return 200 on the same URL. The 404 appears only after
wp core multisite-convert.Why it matters
Beyond looking wrong in devtools, a 404 on the login page misleads uptime monitoring and crawlers, and any tooling that checks status codes before following a redirect will treat the admin as broken.
Environment
Pollora v13.4.3 · WordPress 6.9.4 · PHP 8.4.20 · Laravel 13.8.0 · subdirectory multisite · DDEV, nginx-fpm
Reproduced with the fix from #296 applied (that one is a separate, blocking fatal).
https://claude.ai/code/session_01CtKVtFGujknnYGtcEEJD3x