...

1. Do not follow the above "SSL Configuration in the delivered nginx proxy" instructions! Keep the ordinary HTTP setup!

2. Add in your docker-compose.production.yml file a new environment variable HTTPS=on to the php container

   Code Block
   php: restart: unless-stopped volumes: - translate5-data:/var/www/translate5:cached # just start the apache, if no updates on restart are desired # DO THAT AFTER NOT BEFORE THE DEFAULT ENTRYPOINT WAS USED ONCE! # entrypoint: apache2-foreground environment: -HTTPS=on

   This is needed in order that translate5 recognizes that the application is running under https.

3. Configure Translate5 as it would have SSL (runtimeOptions.server.protocol = https://) and run autodiscovery to configure messagebus correctly.
   Jump into the php container and call the autoconfiguration:

   Code Block
   docker-compose exec php bash t5 config runtimeOptions.server.protocol = "https://" t5 service:auto -a -s frontendmessagebus

   
   

Common problems

DNS resolution in docker container to other docker containers fail

If you experience problems, that the used service names (like termtagger) are not correctly resolving to the correct IP, then follow

https://github.com/moby/moby/issues/41766#issuecomment-884111508

PDFConverter

If the pdfconverter container is always dying immediately after start-up with message "[WARNING] The local web server is already running".

...