error proxy when start docker-compose up about bitwarden_gcloud HOT 4 CLOSED

Hello - looks like you have an error with your Caddyfile:

proxy | Error: adapting config using caddyfile: parsing caddyfile tokens for 'tls': wrong argument count or unexpected line ending after 'tls', at /etc/caddy/Caddyfile:15

If you're using the Caddyfile from the repo, you need to set your .env variables.

from bitwarden_gcloud.

im still confuse... i have already set my .env variables and im using duckdns.org, what else that i need to change?

from bitwarden_gcloud.

okay, i have been setting the proxy .env variables to my email but still stuck in here

proxy | {"level":"error","ts":1716457609.313677,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"vault-vj.duckdns.org","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:connection - 202.80.214.226: Fetching http://vault-vj.duckdns.org/.well-known/acme-challenge/wK2BieepLtBS-X91euit8AUZyAIqe1gpXwmKCn9c1I0: Timeout during connect (likely firewall problem)"}
proxy | {"level":"info","ts":1716457610.5490131,"logger":"tls.issuance.zerossl","msg":"generated EAB credentials","key_id":"UY8PG4enQ79LsygX8bGrnA"}
proxy | {"level":"info","ts":1716457612.2108157,"logger":"tls.issuance.zerossl","msg":"waiting on internal rate limiter","identifiers":["vault-vj.duckdns.org"],"ca":"https://acme.zerossl.com/v2/DV90","account":"[email protected]"}
proxy | {"level":"info","ts":1716457612.210923,"logger":"tls.issuance.zerossl","msg":"done waiting on internal rate limiter","identifiers":["vault-vj.duckdns.org"],"ca":"https://acme.zerossl.com/v2/DV90","account":"[email protected]"}
proxy | {"level":"info","ts":1716457612.7836976,"logger":"tls.issuance.zerossl.acme_client","msg":"trying to solve challenge","identifier":"vault-vj.duckdns.org","challenge_type":"http-01","ca":"https://acme.zerossl.com/v2/DV90"}

from bitwarden_gcloud.

Are you following the instructions here: https://github.com/dadatuputi/bitwarden_gcloud/wiki/DDNS ?

Does your provided ddns resolve to your gcloud IP address right now? The WHOIS for the domain in your paste above does not show Google as the owner. Are you hosting this on gcloud? It will work on other providers, but the instructions will be different and you'll have to do some investigating on your own.

from bitwarden_gcloud.