500 error on panel login

[tenmillionteeth]

Bug description

Migrated a client site to v6 via a fresh install. Everything works locally, just got it deployed to staging. The front-end of the site works, but logging into the panel via email and password just says "Whoops! Something went wrong (500)". There's nothing in the logs, the console has a couple 500 errors:

• panel/auth/passkeys/options
• login:1 unspecified

Not sure how to troubleshoot this one without a more useful error message.

How to reproduce

Install v6, migrate client content, views, users, etc. Test locally. Deploy. Fail to login.

Logs

Nothing in the logs

Environment

Environment
Laravel Version: 13.0.0
PHP Version: 8.5.6
Composer Version: 2.9.7
Environment: production
Debug Mode: DISABLED
Maintenance Mode: OFF
Timezone: America/Chicago
Locale: en

Cache
Config: CACHED
Events: NOT CACHED
Routes: CACHED
Views: CACHED

Drivers
Broadcasting: pusher
Cache: file
Database: mysql
Logs: stack / single
Mail: postmark
Queue: sync
Session: file

Storage
public/storage: LINKED

Statamic
Addons: 8
License Key: Set
Sites: 4 (site1, site2, site3, site4)
Stache Watcher: Enabled
Static Caching: Disabled
Version: 6.18.1 PRO

Statamic Addons
4rn0/statamic-image-optimizer: 1.3.0
anakadote/statamic-recaptcha: 3.1
jacksleight/statamic-bard-texstyle: 4.1.0
mitydigital/feedamic: 3.0.13
mitydigital/sitemapamic: 3.5.0
rias/statamic-redirect: 4.1.9
statamic/seo-pro: 7.8.5
stillat/antlers-layouts: 2.1.1

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[duncanmcclean]

I've converted this to a discussion as I believe it's a setup/troubleshooting issue, rather than an actual bug.

How are you hosting your site? Laravel Forge, Ploi, custom VPS?

I'm assuming you haven't changed anything in the .env since the site worked on v5?

[tenmillionteeth]

It's probably something simple I'm overlooking. Hosting is Ploi on Linode.

The only differences in the .env are we generated a new app key, and the APP_URL is different because the staging URL is different.

[edalzell]

Gotta be an error somewhere, check the system logs? the nginx ones?

Clear the route and cache (don't cache them again) and see if that gives you more hints.

Does this run locally?

[tenmillionteeth]

Yes, it runs locally with no issues.

Redeployed to see if there's any errors this time, and here's what we've got:
Laravel logs:

• Path must not be empty
• Rate limiter [statamic.cp.auth] is not defined
• Rate limiter [statamic.cp.passkeys] is not defined.

System and deploy logs have nothing unexpected. NGINX logs just have the usual blocked malicious requests for hidden files.

[edalzell]

Let's see more of the errors, this will likely be a .env difference/issue/configuration