SSL Errors on newest version with Docker-compose.yml + .env combination

[jxs714]

📜 Description

When updating/installing the latest version with docker-compose.yml and .env file method, I am getting an SSL error / warning. The only way I could get things to work again was using the docker-compose.yml method and setting up all my configuration there instead of using the .env.

👟 Reproduction steps

• Setup your docker-compose.yml with basic options like below:

services:
  postiz:
    image: ghcr.io/gitroomhq/postiz-app:latest
    container_name: postiz
    ports:
      - "4900:5000"
#      - "4901:4200"
    volumes:
      - postiz-config:/config
      - postiz-uploads:/uploads
    env_file:
      - /opt/dockerapps/postiz/.env
    restart: unless-stopped

volumes:
  postiz-config:
    external: true
  postiz-uploads:
    external: true

• setup our .env file configuration for your server with the correct configuration • docker compose up -d

You will get an SSL error in logs

👍 Expected behavior

It would run the software without an issue prior to updating.

👎 Actual Behavior with Screenshots

N/A - I fixed it and didnt get a chance to screenshot

💻 Operating system

Linux

🤖 Node Version

1.22.22

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• [x] I checked and didn't find similar issue

Are you willing to submit PR?

None

[egelhaus]

Hey, this isn't an problem with us but your settings of your env file. You're more than welcome to include in the docs on how to actually use an env or na proper format of env templated in the docs

[jxs714]

Hey, this isn't an problem with us but your settings of your env file. You're more than welcome to include in the docs on how to actually use an env or na proper format of env templated in the docs

Are you directing this to me or the support team? If its to me, My .env and docker compose configuration was working completely fine until I upgraded to the latest version. It was only then that the issues began. I resolved it by using their first option for configuration, which is by putting everything in the docker-compose.yml file. From my understanding, this should not be a normal practice for security reasons.

[nevo-david]

Please try the new docker, if that doesn't work, please join our Discord.