Blank page after refresh

[mateusz-peczkowski]

• Laravel Version: 11.36.1
• Nova Version: 5.0.2
• PHP Version: 8.3.7

Description:

A fresh installation of Laravel 11 and Laravel Nova 5 was performed. Upon visiting the Nova URL, a login page is displayed. Successful login allows access to any page without encountering any issues. However, refreshing a page results in a blank page with an error message, as depicted in the screenshot.

Detailed steps to reproduce the issue on a fresh Nova installation:

1. Install Laravel 11
2. Install Nova 5 via composer (Everything as on the Installation guide upon Nova user create)
3. (optional) Change config.nova.path to / and remove the body of routes/web.php
4. Setup domain in ENV
5. Go to your domain
6. Login to user created in point 2
7. Go to for example users
8. Refresh page

Using php artisan serve everything is working, so it can be tested only on Apache projects. Laravel Nova 4 is working normally.

[mateusz-peczkowski]

I've added a console log in compiled code

And it is shown as "undefined". So something is not loading properly.

It only works if I go to:
https://nova-5.peczis.priv/nova

then it redirects me to https://nova-5.peczis.priv/nova/dashboards/main and I can go through panel UNTIL next refresh

[crynobone]

Unable to replicate the issue with http and https:

[crynobone]

Also, lockdown-install.js isn't part of Laravel Nova. Could that be the cause of your problem?

[crynobone]

I found the issue, on certain browsers the sequence of loading (by Inertia 2) is slightly different (on refresh) as illustrated on screenshot above (left using Firefox and right using Chrome).

Firefox consistently runs createInertiaApp.setup() before DOMContentLoaded while Chrome might run DOMContentLoaded before Inertia could execute createInertiaApp.setup().

[anditsung]

i have tested it on safari, chrome, firefox and brave

only firefox is working

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.