yes
[SOLVED] Issue verifying custom domain
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
docker: 'compose' is not a docker command.
Try docker-compose exec appwrite vars instead
Rank 2: Process
The same 😦
That's weird, is your docker running?
Make sure you use docker-compose and not docker compose
Rank 2: Process
Suppose so because I can enter Appwrite console on my VPS :0
Rank 2: Process
Sure, double checked
Same exact error?
Rank 2: Process
But I can check it via .env file itself
Rank 2: Process
Yes
Rank 2: Process
And in .env file there is my main domain, without api. prefix
In .env, in 99% of the cases, you probably want _APP_DOMAIN_TARGET to be the same as _APP_DOMAIN, most likely this is why verification fails
Rank 2: Process
Oh my, I had to install docker-compose package separately
Rank 2: Process
ok, I'll check it
You have here more information about how to update env vars: https://appwrite.io/docs/environment-variables
Rank 2: Process
Should I restart docker after updating my env file?
Restart is not enough, you need to recreate containers. docker-compose up -d should do the trick
Rank 2: Process
So in my case the _APP_DOMAI and _APP_DOMAIN_TARGET should be the same and equal api.[my-domain-name], correct?
yes
Rank 2: Process
Finally it verified but the connection it still unsecure (http against https). Should I make additional steps to make it work?
Rank 2: Process
Nevermind, should add https before domain 🙂 thanks a lot @Eldad
🥳
You welcome! Please add [SOLVED] to the title of this thread
Rank 2: Process
[SOLVED] Issue verifying custom domain