yes
docker: 'compose' is not a docker command.
Try docker-compose exec appwrite vars instead
The same 😦
That's weird, is your docker running?
Make sure you use docker-compose and not docker compose
Suppose so because I can enter Appwrite console on my VPS :0
Sure, double checked
Same exact error?
But I can check it via .env file itself
Yes
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
Oh my, I had to install docker-compose package separately
ok, I'll check it
You have here more information about how to update env vars: https://appwrite.io/docs/environment-variables
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
So in my case the _APP_DOMAI and _APP_DOMAIN_TARGET should be the same and equal api.[my-domain-name], correct?
yes
Finally it verified but the connection it still unsecure (http against https). Should I make additional steps to make it work?
Nevermind, should add https before domain 🙂 thanks a lot @Eldad
🥳
You welcome! Please add [SOLVED] to the title of this thread
[SOLVED] Issue verifying custom domain
Recommended threads
- Realtime for files() works almost well, ...
I have been trying to make use of realtime, today (14.03.26) I have pulled all the latest versions of docker images, and sdk available. Whats working: - Conn...
- Function issue
Hi,idk whats wrong with my function but i made some changes to the env var and made sure they saved then i redeployed it,but then after it redeeployed it asked ...
- Function issue
Hi,idk whats wrong with my function but i made some changes to the env var and made sure they saved then i redeployed it,but then after it redeeployed it asked ...