Our work is stopped: we can’t open our images, attached to issues…
Link to missing image:
Group ID: 5913539 (-X GET https://gitlab.com/api/v4/groups)
Project ID: 14010990 (-X GET https://gitlab.com/api/v4/groups/5913539/projects)
See screenshots for details:
If I will add new image to issue, it is successfully uploads to server:
(and server gives us correct JSON response)
Also, all uploaded files I can get, if will make backup of project:
Same bug not reproducing in
– images working correctly
UPDATE 3: SOLUTION
Found way to make image attachments work again:
- Export project to archive
- Rename project (and it’s path)
- Create new project by restoring from archive.
Unfortunately - this will restore all images but not new attached
We have the same problem!
Please increase priority of this issue!
@login.hedin has anything changed for you?
Hi, my company is facing this issue too. Is anyone at GitLab looking into this? It’s hard to work with my remote team when I cannot communicate using attachments.
I confirm the issue, on gitlab-ee, Debian Stretch, updated last saturday, and since, the uploaded images are emitting a 404 error. The image file is well uploaded on the system (/var/opt/gitlab/gitlab-rails/uploads/@hashed/ directory) but the production log contains a “route not found” error :
Started GET “/uploads/2b57c4c45b61441f9ea40813d7115cba/Fail.PNG” for my.ip.xx.xx at 2019-09-02 12:22
Processing by ApplicationController#route_not_found as
Thanks everyone for the feedback. This bug should be fixed in the release 12.2.4, here’s the issue with more details
Hi, when will this be released/patched on gitlab.com?
Here’s the patch for the self hosted versions https://about.gitlab.com/2019/09/02/gitlab-12-2-4-released/. The GitLab.com should receive the update soon (today or tomorrow).