/entrypoint.sh: 279: exec: --env: not found about acme-companion HOT 2 CLOSED

Hi.

This is not acme-companion issue but a Docker CLI usage issue.

--env arguments must be passed before the name of the docker image you want to run, so before nextcloud. If you pass it after the image name it will be passed as CMD to the container, which is why you get this error from nextcloud (you are passing those --env arguments to the nextcloud process running in the container, and he does not understand them).

You should not have nginx at the end, that make no sense.

$ docker run --detach \
    --name nextcloud \
    -p 8080:80 \
    -v /home/user/nextcloud:/var/www/html \
    --network nextcloud-net \
    --env "VIRTUAL_HOST=subdomain.domain.tld" \
    --env "LETSENCRYPT_HOST=subdomain.domain.tld" \
    nextcloud

https://docs.docker.com/engine/reference/commandline/run/

from acme-companion.

Hi, thanks for your reply. I can confirm that acme-companion is running as it should and I had a Docker CLI usage issue. However I've been playing with arguments and It didn't work either, after a bit of trying I found that I also had NordVPN mesh net issue that is blocking the connection, which I already fixed by restarting the service. Again huge thanks for helping me solving the issue, I really appreciate it.

from acme-companion.