-
Notifications
You must be signed in to change notification settings - Fork 481
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
1.5.0 Upgrade 404 to Attachments #522
Comments
Can you provide full nginx config. |
NGINX Config currently Active: https://dev.mgz.de/paste/?1c49ba8acbe7319e#7N1hccuKefa64Y3yfwzmgEA2rMHiGiqVRve6zY5wq7jF |
Nginx config if fine.
This is not required. Better remove it from .env until you get attachments working. |
Make sure that new code actually has been pulled and clear the cache. |
Removed APP_DOWNLOAD_ATTACHMENTS_VIA from .env >Cleared the Cache again. Unfortunately same 404. Currently it's working but only because I added the symbolic link. If I remove it 404 is back. |
Make sure that |
I had a similar problem where all attachments were empty (0 bytes). On the shell I ran |
Problem is that in Nginx the file as attachment at the end of the conversation seems not to get rewritten and so the webserver tries to open it from the Filesystem instead of passing it though php. Currently with the symlink it'S working but of course not intended to stay like that, I will have a deeper look into the problem latest wednesday, today I was just to busy. |
After updating to 1.5.0 if you are using Nginx make sure to replace
with
|
Can Confirm, thanks. Indeed the present rules in the NGINX vhost were overwriting the systems php handler. Changed to the suggested one and it works. -closed |
With For us it works better with |
Opening for others to see this issue. |
I done the things listed above but it still isn't working. |
Are you updating FreeScout or installing? |
We have updated freeScout to 1.5.2. |
Have you updated Nginx config? #522 (comment) |
yes |
Does it work with the symlink?
|
no unfortunately it doesn't. |
What error are you receiving? Do you actually have files in /var/www/html/storage/app/attachment/ ? |
aha i found it, the docker uses '/data/storage/app/attachment' instead of /var/www/html |
Well our ngnix conf was also wrong. Were the location is defined. fixed that and now it works again. |
Hi,
after Upgrading to 1.5 all Attachments only give 404 Errors.
Directory was moved correctly by the upgrade and the corresponding jpg file is in the Directory structure:
/var/www/html/storage/app/attachment
Running Nginx, tried after the upgrade, got 404 Error. Tried to Apply the Changes as mentioned in the changelog;
APP_DOWNLOAD_ATTACHMENTS_VIA=nginx >> .env
Unfortunately still 404.
Nginx Error Log:
2020/03/09 09:02:25 [error] 112250#112250: *5 open() "/var/www/html/public/storage/attachment/5/7/1/game_Grafik-Vier-von-zehn-Deutschen-kennen-Augmented-Reality.jpg" failed (2: No such file or directory), client: ########, , server: ########, request: "GET /storage/attachment/5/7/1/game_Grafik-Vier-von-zehn-Deutschen-kennen-Augmented-Reality.jpg?id=1842&token=984a1bbcc43ce7935bfab427da8eb060 HTTP/2.0", host: "inbox.planetlan.work", referrer: "https://inbox.planetlan.work/"
It still tries to read from:
/var/www/html/public/storage/attachment
where /attachment is not existing.
A Quick Workaround to make it read the Attachements via Nginx again is:
ln -sd /var/www/html/storage/app/attachment/ /var/www/html/public/storage
The text was updated successfully, but these errors were encountered: