I am running Alfresco community edition V7.1.0 in Docker containers running on Ubuntu 20.04.3 LTS.
Everything is working as it should except for workflow e-mails, which have the incorrect URL, they all start with http://127.0.0.1. I am fairly new to Docker containers and have tried editing the docker-compose.yml file as suggested in other posts but to no avail. The URL's should start with http://10.4.0.200.
I would appreciate if someone with some more experience could take a look at the docker-compose file below and let me know what I am missing (there are so many different docker-compose files in the installation but I think I am editing the correct one (Alfresco/app/acs-deployment/docker-compose/docker-compose.yml))
Thanks in advance
Nick
JAVA_OPTS: " -Ddb.driver=org.postgresql.Driver -Ddb.username=alfresco -Ddb.password=alfresco -Ddb.url=jdbc:postgresql://postgres:5432/alfresco -Dsolr.host=solr6 -Dsolr.port=8983 -Dsolr.secureComms=none -Dsolr.base.url=/solr -Dindex.subsystem.name=solr6 -Daos.baseUrlOverwrite=http://10.4.0.200:8080/alfresco/aos -Dmessaging.broker.url=\"failover:(nio://activemq:61616)?timeout=3000&jms.useCompression=true\" -Ddeployment.method=DOCKER_COMPOSE -Dtransform.service.enabled=true -Dtransform.service.url=http://transform-router:8095 -Dsfs.url=http://shared-file-store:8099/ -DlocalTransform.core-aio.url=http://transform-core-aio:8090/ -Dcsrf.filter.enabled=false -Ddsync.service.uris=http://localhost:9090/alfresco -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80 " transform-router: mem_limit: 512m image: quay.io/alfresco/alfresco-transform-router:1.4.1-A3 environment: JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80" ACTIVEMQ_URL: "nio://activemq:61616" CORE_AIO_URL : "http://transform-core-aio:8090" FILE_STORE_URL: "http://shared-file-store:8099/alfresco/api/-default-/private/sfs/versions/1/file" ports: - 8095:8095 links: - activemq transform-core-aio: image: alfresco/alfresco-transform-core-aio:2.5.3 mem_limit: 1536m environment: JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80" ACTIVEMQ_URL: "nio://activemq:61616" FILE_STORE_URL: "http://shared-file-store:8099/alfresco/api/-default-/private/sfs/versions/1/file" ports: - 8090:8090 links: - activemq shared-file-store: image: quay.io/alfresco/alfresco-shared-file-store:0.15.0 mem_limit: 512m environment: JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80" scheduler.content.age.millis: 86400000 scheduler.cleanup.interval: 86400000 ports: - 8099:8099 volumes: - shared-file-store-volume:/tmp/Alfresco/sfs share: image: quay.io/alfresco/alfresco-share:7.1.0-M2 mem_limit: 1g environment: REPO_HOST: "alfresco" REPO_PORT: "8080" JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80 -Dalfresco.host=10.4.0.200 -Dalfresco.port=8080 -Dalfresco.context=alfresco -Dalfresco.protocol=http " postgres: image: postgres:13.1 mem_limit: 512m environment: - POSTGRES_PASSWORD=alfresco - POSTGRES_USER=alfresco - POSTGRES_DB=alfresco command: postgres -c max_connections=300 -c log_min_messages=LOG ports: - 5432:5432 solr6: image: alfresco/alfresco-search-services:2.0.2 mem_limit: 2g environment: #Solr needs to know how to register itself with Alfresco - SOLR_ALFRESCO_HOST=alfresco - SOLR_ALFRESCO_PORT=8080 #Alfresco needs to know how to call solr - SOLR_SOLR_HOST=solr6 - SOLR_SOLR_PORT=8983 #Create the default alfresco and archive cores - SOLR_CREATE_ALFRESCO_DEFAULTS=alfresco,archive #HTTP by default - ALFRESCO_SECURE_COMMS=none ports: - 8083:8983 #Browser port activemq: image: alfresco/alfresco-activemq:5.16.1 mem_limit: 1g ports: - 8161:8161 # Web Console - 5672:5672 # AMQP - 61616:61616 # OpenWire - 61613:61613 # STOMP digital-workspace: image: quay.io/alfresco/alfresco-digital-workspace:2.3.0-adw mem_limit: 128m environment: APP_CONFIG_AUTH_TYPE: "BASIC" BASE_PATH: ./ proxy: image: alfresco/alfresco-acs-nginx:3.1.1 mem_limit: 128m depends_on: - alfresco - digital-workspace ports: - 8080:8080 links: - digital-workspace - alfresco - share sync-service: image: quay.io/alfresco/service-sync:3.4.1-M1 mem_limit: 1g environment: JAVA_OPTS : " -Dsql.db.driver=org.postgresql.Driver -Dsql.db.url=jdbc:postgresql://postgres:5432/alfresco -Dsql.db.username=alfresco -Dsql.db.password=alfresco -Dmessaging.broker.host=activemq -Drepo.hostname=alfresco -Drepo.port=8080 -Ddw.server.applicationConnectors[0].type=http -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80 " ports: - 9090:9090 volumes: shared-file-store-volume: driver_opts: type: tmpfs device: tmpfs
You need to set the SysAdminParams subsystem config properties via JAVA_OPTS to "tell" ACS which URLs to construct for emails. Specifically you want to set alfresco.host / alfresco.protocol / alfresco.port in accordance with your user-facing proxy / loadbalancer / gateway.
Thank you for this information. is the notation correct below, as I thought I had already done this? Please forgive my ignorance on this.
JAVA_OPTS: " -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80 -Dalfresco.host=10.4.0.200 -Dalfresco.port=8080 -Dalfresco.context=alfresco -Dalfresco.protocol=http "
You need to include those properties also in "alfresco" service.
Please could you give me some guidance as to how I achieve this?
alfresco: image: alfresco/alfresco-content-repository-community:7.1.0 environment: JAVA_OPTS: " -Dalfresco.host=10.4.0.200 -Dalfresco.port=8080 -Dalfresco.context=alfresco -Dalfresco.protocol=http "
Thank you for the clarification but I must be missing a step. I have added this configuration to every compose file I can find on the system in question but the links in the e-mails are still coming up with http://127.0.0.1. am I missing a step to have this configuration applied (I have stopped and restarted all of the containers after the configuration change)?
Some workflows - such as site invites - may be taking the host / URL from the browser context in which the user initiated them, and use those in emails. Make sure that you are also accessing Alfresco using the same public DNS name / URL as other users would need to use.
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.