页面 · Laravilt
Troubleshooting
Fixes for the most common installation and setup problems.
Start with storage/logs/laravel.log and the browser console. Most problems show up in one of them.
Blank page or missing styles
The frontend isn't built, or you're running a stale build.
bash
Check that APP_URL matches the URL you open.
"Page not found" for a Laravilt page / Inertia can't resolve a component
- Vue: the panel pages must be published. Re-run
php artisan vendor:publish --tag=laravilt-panel-views --force, then rebuild. - React: pages resolve from
vendor/. Runcomposer install, then rebuild. - Make sure
LARAVILT_FRONTENDin.envmatches your starter kit (vueorreact), then runphp artisan config:clear.
The installer ran with the wrong stack
Set LARAVILT_FRONTEND correctly and re-run the installer with an explicit stack on a starter kit of that stack:
bash
/admin returns 404
- The panel provider must be listed in
bootstrap/providers.php(the installer addsApp\Providers\Laravilt\AdminPanelProvider::class). - Run
php artisan route:clearandphp artisan optimize:clear. - The panel
->path()sets the URL prefix.
Login loops or "CSRF token mismatch"
APP_URL,SESSION_DOMAINand the browser URL must agree (same host and scheme).- With
SESSION_DRIVER=database, thesessionstable must exist (php artisan migrate).
A resource doesn't appear in the navigation
- It must live under
app/Laravilt/{Panel}/Resources/{Name}/{Name}Resource.phpfor auto-discovery. - Check
canViewAny()/ policies. See Authorization.
npm install or the build fails
bash
Use Node.js 20 or newer.
Class "Laravilt..." not found
bash
Still stuck?
- Compare with the live demo (
[email protected]/password). - Ask your AI assistant through the Laravilt MCP server.
- Search or open an issue on GitHub.
- See the FAQ.