Cannot assign null to property Appwrite\Auth\OAuth2\Github::$user of type array
Huh. And docker compose exec appwrite ping api.github.com -c 4?
ping: bad address 'api.github.com'
ya something seems weird with DNS
is there any workaround to rectify this issue, this seams to be out of my knowledge. even i have added DNS is docker engine but no luck 🙂 . here is what i have in docker engine : "dns": [ "1.1.1.1", "1.0.0.1", "10.0.0.2", "8.8.8.8" ],
what is 10.0.0.2?
this was default dns i have added only cloudflare dns
maybe remove it?
can you also try running this:
docker run --rm alpine nslookup api.github.com
@Drake i have done the following changes in docker-compose.yml and successfully configured the Gitapps , appwrite: image: appwrite/appwrite:1.4.13 dns: 8.8.8.8 container_name: appwrite i have added dns
Server: 192.168.65.7 Address: 192.168.65.7:53
Non-authoritative answer: Name: api.github.com Address: 20.207.73.85
*** Can't find api.github.com: No answer
And this?
docker run --rm alpine apk add curl && curl https://api.github.com
if that fails, it's a docker problem and not an appwrite problem. what's your server's OS?
Just Dm you the response as message was long and win is the os
is there any issue if i add dns: 8.8.8.8 in appwrite image like i mentioned above ?
ok the curl works...
without any modifications in the docker-compose.yml, does it still not work?
also, in general, you shouldn't modify the docker-compose.yml file from Appwrite because it will be wiped when you upgrade
nope, is not working without modification
weird....so it works with the modification?
Yes, its working with modification only 🙂
weiiiird. Anyways...if you need to customize the docker-compose.yml file, use a docker-compose.override.yml file so that your changes won't be wiped after an upgrade
But its not over :), now while creating function build is getting fail, here are the logs : Could not resolve host: api.github.com with status code 0
you'll need to add that DNS config to the executor container too
Is it openruntimes-executor. right ?
@Drake here is the last update, my host was obtaining DNS automatically, now i have manually configured the DNS to 1.1.1.1 and 1.0.0.1. Which solved the issue.
