I downloaded the docker compose file from https://www.alfresco.com/thank-you/thank-you-downloading-alfresco-community-edition
It mostly works, but user search doesn't work from the admin panel:
I have tried other users.
I know very little about Tomcat or Solr, but with tcpdump I was able to figure out that when searching from the "People" tab a call is going to Solr. However, when I search from "Admin Tools" -> "Users and Groups" --> "Users" no call actually makes it to Solr.
I noticed in Firefox that people-enterprise is getting blocked.
Then I noticed this 404 (SB is one of the users):
The hint to "useCQ" doesn't help because I don't know what CQ is.
While this happns on a Mac with Firefox, a colleague of mine got the same issue on a Windows version of Chrome (didn't do network inspection, but same symptom). I ran this in a private browsing tab to try to avoid weird caching and plugin issues.
Does people-enterprise mean I have somehow installed the enterprise version when I went to the Community Edition page? What would be useful logs to look at?
This was a known issue with 6.x version.
Check the notes here (known issues) :
Known Issues
A temporary solution has been provided here, see if it works for you: https://github.com/Alfresco/acs-community-packaging/issues/367#issuecomment-664563382
Additionally, this project will build a Docker Compose template for you with the issue fixed:
https://github.com/alfresco/alfresco-docker-installer
I am running into this error using the docker installer on ubuntu 20.04:
root@dwhitfield-ubuntu-alfresco:~/docker-compose# yo alfresco-docker-installer /usr/local/lib/node_modules/yo/node_modules/conf/index.js:128 throw err; ^ Error: EACCES: permission denied, open '/root/.config/insight-nodejs/insight-yo.json' at Object.openSync (fs.js:443:3) at Object.readFileSync (fs.js:343:35) at Conf.get store [as store] (/usr/local/lib/node_modules/yo/node_modules/conf/index.js:108:18) at Conf.get (/usr/local/lib/node_modules/yo/node_modules/conf/index.js:47:27) at Insight.get optOut [as optOut] (/usr/local/lib/node_modules/yo/node_modules/insight/lib/index.js:52:22) at Object.<anonymous> (/usr/local/lib/node_modules/yo/lib/cli.js:205:48) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
apparently root and npm don't get along, but still running into issues using the alfresco-docker-installer:
Error: Timeout
at MergeMapSubscriber.timer.pipe.mergeMap [as project] (/home/dwhitfield/docker-compose/node_modules/wait-on/lib/wait-on.js:128:74)
at MergeMapSubscriber._tryNext (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/operators/mergeMap.js:67:27)
at MergeMapSubscriber._next (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/operators/mergeMap.js:57:18)
at MergeMapSubscriber.Subscriber.next (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/Subscriber.js:66:18)
at AsyncAction.dispatch [as work] (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/observable/timer.js:31:16)
at AsyncAction._execute (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/scheduler/AsyncAction.js:71:18)
at AsyncAction.execute (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/scheduler/AsyncAction.js:59:26)
at AsyncScheduler.flush (/home/dwhitfield/docker-compose/node_modules/rxjs/internal/scheduler/AsyncScheduler.js:52:32)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
Waiting failed -> exit 1
I am able to get to the share page, but then in the UI I get this when I try to log in:
"Your authentication details haven't been recognized or Alfresco Content Services may not be available at this time."
This is the same system where I had the default docker-compose.yml mostly working. I wonder if the old persistent data could be messing this up somehow. I have tried with HTTPS and HTTP. I have tried the machine name as well as localhost.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.