01-30-2025 03:53 AM
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.
01-30-2025 04:01 AM
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" }
01-30-2025 04:16 AM - last edited 2 weeks ago
Ok so here is what I have found:
So it appears to be something related to permissions. The content-app works fines. I tried downgrading share to the older version but still get the error. Anyone know how to reset permissions or to change them?
4 weeks ago
Hmm not luck. There is only 1 user that is experiencing this problem and is the owner of several sites. Other users of the sites can view them just fine.
4 weeks ago
Ok the other users can still login. Its just the 1 user. He is the owner of several sites and it appears he can only see the sites set to "moderated" as opposed to "private". Other users have no problems.
Explore our Alfresco products with the links below. Use labels to filter content by product module.