#Appwrite 1.7.4 " Utopia\Domains\Domain::__construct(): Argument #1 ($domain) must be of type string
20 messages ยท Page 1 of 1 (latest)
docker-compose.yml
/console/onboarding/create-project
This is a fresh installation.
@sly nimbus Have you solved it?
No
here could be https://discord.com/channels/564160730845151244/1384143419357659206 i'll test it.. right now i updated from 1.6.0 to 1.6.2-RC1 and is working.. trying as they said... to update to last version of the main release first BEFORE updating to a new main release ... so .. after this i'll update to 1.7.0... then to 1.7.4 ... and of course, use migrate...
I will try
Bro, regarding this: Appwrite 1.7.4 " Utopia\Domains\Domain::__construct(): Argument #1 ($domain) must be of type string
You need to check their .env and the composer file...
I managed to solve it by adding in my Composer File and Env (using coolify) this:
Main Appwrite API Domain
_APP_DOMAIN=yourdomain.com # Use your main Appwrite API domain (e.g., appwrite.yourdomain.com or api.yourdomain.com)
Functions Domain (must be a unique subdomain)
_APP_DOMAIN_FUNCTIONS=**functions.**yourdomain.com
Appwrite Sites Domain (must be a unique subdomain for hosting web apps)
_APP_DOMAIN_SITES=**sites.**yourdomain.com
Target for AAAA record (IPv6). Use ::1 for localhost if you don't have a public IPv6.
_APP_DOMAIN_TARGET_AAAA=::1
Target for CNAME record. This typically points to your main Appwrite API domain.
_APP_DOMAIN_TARGET_CNAME=yourdomain.com
now i need to solve this other problem appeared, searching ๐ "Route not found. Please ensure the endpoint is configured correctly and that the API route is valid for this SDK version. Refer to the API docs for more details." so need to check ๐
Can you send me the docker-compose.yml and the .env file (excluding any secret credentials)?
when i"m back home, anyway i need to test it more because i did something and was fked up again.. so even if i will send you the compose (again, i'm using coolify..) we better will wait an official support for it... ๐
I am using dokploy same as coolify
dockploy is using the docker-compose file that is nearly identical as the original... but coolify is structured something else.. i installed dockploy too to check.. i didn't manage it but!! Be aware... what i'm telling you is that in the github.. you have their .env and their docker-composer... get those too.. open aistudio.google.com... ask the ai to check and complete the old version... simple as that.. or to check the differences.. etc and in the coolify env.. the only thing that was changed was what i gave you up... _APP_DOMAIN_FUNCTIONS=functions.yourdomain.com , _APP_DOMAIN_SITES=sites.yourdomain.com , _APP_DOMAIN_TARGET_AAAA=::1 , _APP_DOMAIN_TARGET_CNAME=yourdomain.com
Ok
and that for a fresh instalation... for a migration.. i'm not sure xD
i know that we need to use migration command if from an old version... but for a fresh 1.7.4 i don't think is neccesary.. anyway.. i was happy that was working .. today :)) made something there.. and fked up again.. so.. i'll do a fresh install when i'm back home
@sly nimbus https://docs.google.com/document/d/1vaUpDpCLf02-PPmInL5dAEmIpglXnOWB9-V6sPw-t8Y/edit?usp=sharing this is all that you need.. i tried with this simple composer and keep in mind to add data for this APP_DOMAIN_FUNCTIONS=**functions.**yourdomain.com , _APP_DOMAIN_SITES=sites.yourdomain.com , _APP_DOMAIN_TARGET_AAAA=::1 , _APP_DOMAIN_TARGET_CNAME=yourdomain.com
Ok
But too bad that they paywalled the database backup... even if we can backup it mannualy.. why to paywall it... they have an amazing product, i will want maybe if i have success with my project to move to the cloud... right.. so.. eh.. anyway.. ๐ hope you will solve it bro... overall the problem was this: _APP_DOMAIN_FUNCTIONS=functions.yourdomain.com , _APP_DOMAIN_SITES=sites.yourdomain.com , _APP_DOMAIN_TARGET_AAAA=::1 , _APP_DOMAIN_TARGET_CNAME=yourdomain.com
@sly nimbus i updated the composer with a proper working solution where the routing error ""Route not found. Please ensure the endpoint is configured correctly and that the API route is valid for this SDK version. Refer to the API docs for more details." was solved by downgrading the console to 6.0.41 ๐ and also updated as per original composer from the repo