Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
deployed onto a debian 11 server with terminal interface - no GUI
but getting 500 errors when I try to access site from a browser.
laravel.log says Vite manifest not found But if I run npm run build (or npm run dev) I get an error qt.qpa.xcb: could not connect to display ....plugin could not load....
No idea where the setting for this is, or what needs to be installed here.
Or what needs doing to remove or sort this Any ideas?
The simplest solution might be to build the assets with npm run build locally and deploy them with the rest of the code. Otherwise google that error (qt.qpa.xcb: could not connect to display) and see if you can fix it. npm run build is needed
I see the exact same issue @ihill2. Not sure of resolution, but it seems clunky to build locally to get around this!
@kayaker323 the clean solution is to set up zero downtime deployment. I personally use ploi for this, but you can write the deploy script yourself (I used to)
@Sinnbeck yeah - I encounter the issue in envoyer actually so the zero downtime deploy still has the issue. Maybe I'll just replace forge and envoyer with ploi! Trying that now
@kayaker323 it works for me at least. I deploy with no downtime at all. Inertia does a full page refresh on next ajax request but that's it
@Sinnbeck Maybe it's related to the packages forge installs for us? Gotta admit forge and envoyer offer precious little in convenience compared to the alternatives!
Update: looks like @ihill2 had this on a vanilla deploy to debian 11
@kayaker323 haven't tried either but I really love ploi. Offers a ton of features and it just works
Please or to participate in this conversation.