11 hours ago
Hi all,
I recently upgrade our Alfresco Community install via our modified docker-compose file. Straight after the upgrade I could login to share and see all my sites. I even uploaded some documents to the one site. When I log in this morning I get most of the site returning the "something's wrong with this page..." screen.
The share starts to load and then is replaced with the error page. From the javascript console I get see it is getting a 410 response to the following:
[HTTP/2 410 187ms]
Status
410
It seems like the cache is failing to create the response? Any ides where to look for the issue? Is it Solr6? I assume it some process that ran and delete the old file but didn't create the new one? Any assistance appreciated.
10 hours ago
Here is the json response:
{ "status" : { "code" : 410, "name" : "Gone", "description" : "Resource is no longer available at the server and no forwarding address is known." }, "message" : "Site not found: 'abc'", "exception" : "", "callstack" : [ ], "server" : "", "time" : "30 Jan 2025, 08:58:59" }
10 hours ago
OK its weird because other users aren't affected. Maybe they will stop working in the next day or two. Will monitor and continue to troubleshoot.
Explore our Alfresco products with the links below. Use labels to filter content by product module.