-
-
Notifications
You must be signed in to change notification settings - Fork 540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gilde assets returning 400 after upgrading site on forge #11089
Comments
This looks like a web server error page, rather than a Laravel/Statamic one. What does your Nginx config look like? |
Thanks for the quick reply! This is my nginx:
|
i also have this problem, the 400 is gone when setting secure to false in assets.php. Some deeper debugging makes me think that the problem is the generated Url from GlideUrlBuilder, when line 59 "$path .= Str::ensureLeft(URL::encode($filename), '/');" is removed, everythings works fine. |
Bug description
Hey all, any help is appreciated.
I had upgraded a site from v4 to v5, I did this by setting up a new site with the upgrade on forge and then switching the domain to the current live site.
All images were working prior to switching. I have ran the following commands to clear caches, regenerate presets and meta etc but still no luck.
I have found that changing secure setting in the config to false allows the images to work but obviously this isn't recommended on production.
this is my config otherwise:
I have found a similar post #10053 which suggest amending nginx config, however I do not have any configuration regarding images.
The only other consideration is I am using spatie responsive image, however images were working prior to changing domains so am sure this isnt the issue.
The images return 400 in the network tab
How to reproduce
Upgrade existing site on forge to V5
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: