Level 27
What do you mean “do not work”? We can’t help you if we don’t know what’s wrong…
Oct 31, 2022
9
Level 6
Livewire | Filament Headaches on Producton
Anybody successfully launch the Admin-Dash Filament package on a production nginx server? I have been banging my head against the wall for 11 hours and 45 minutes...(no exaggeration)
The assets work perfectly fine locally but do not work on server. I tried everything on this page: https://github.com/livewire/livewire/issues/242#issuecomment-948054946
Does anybody know any solutions or have any experience with Filament of Nginx production? Thanks
*Unfortunately Filament's support group is not a proper forum, rather that chatty gamer's platform "discord" - an unfortunate poor choice for support *
Level 6
The assets (css, js) on the server do no exist in location that the html src is point to.
Level 7
Hi @bionary
I faced the same issue and solved it already, you just need to put additional Nginx configuration lines to make the web server properly handle /filament.
location / {
try_files $uri $uri/ /index.php?$query_string;
}
You can read more about the datil here: How to fix Laravel Filament asset is missing or not found and Nginx Configuration for Laravel Filament
Hope that helps!
1 like
Level 6
@devs-x While I appreciate the help I still cannot get the filament scripts to work on production. (btw I am using runcloud provisioning with linux server) Admittedly I know little about front end bundling and struggle with the concept/technique.
What I do know is that filament works perfectly fine locally.
I have run npm run build and pushed my code to server.
I can see that any filament page is looking for assets in locations like this:
mysite.com/filament/assets/app.css?id=c25517b62a64033c1a45c5brdh
going to that url directly leads to 404. So something in laravel or nginx is definitely not routing correctly.
1 like
Level 1
I faced the same issue on production with nginx web server and solved it as below.
- the asset files (css, js) are working on the local system so i copied the asset code from the browser by entering the asset url. (eg : http://localhost/filament/assets/app.css).
- Then on the server under the 'public' folder of laravel. Mannually create the 'app.css' & 'app.js' files inside the folder name 'filament/assets'. (eg : http://your-domain/filament/assets/app.css)
- Now refresh your web page.
This method worked for me.
Thank you :)
Level 6
@thamnees I'm in the middle of something else..but I will try your suggestions when I have time in about a week or so! Thanks!
Level 3
There appears to be an issue with the nginx configuration on runcloud.io. Despite spending two days trying to resolve the issue, a solution has not been found. However, when the same application was tested on ploi.io, it worked without any problems. This suggests that the issue lies with runcloud.io and not with the code.
1 like
Level 6
Finally, after 6 months I got this headache sorted out. While I didn't work on this for 6 straight months, this annoying issue consumed days of my working existence.
@thamnees , @shubhamchugh , @devs-x
Here is what I did to get filament working on runcloud. By the way here is my setup because I'm sure things could change with different version. The modern web stack has really become a stack of cards. very sensitive and easy to break everything. My stack:
- Laravel 10
- Filament 2
- Runcloud / Vultr / Ubuntu / Nginx
My fix: comment out or remove front assets in main .gitignore
#/public/build
commit and push
On runcloud they disabled ignore_user_abort function by default.
For some reason runcloud disables lots of php functions that are necessary for many php packages. But you can re-enable them by removing them from the textarea list they provide under:
> settings > php settings > disable_functions. - remove "ignore_user_abort" and click "Update PHP Settings"
That's it.
With the front end assets pushed through git and the ignore_user_abort function enabled everything seems to be working fine.
1 like
Level 6
Have same issue on php8.3 with nginx/1.26.2. not yet fixed more than 12 hours LOL
Please or to participate in this conversation.