Level 65
Looks like a network issue. Have you tried pinging/curling the domain?
Mar 18, 2016
8
Level 32
Envoyer Deployment Failing: unable to resolve github
Trying to deploy using Laravel Envoyer, but getting this error.
--2016-03-18 14:10:00-- https://api.github.com/repos/...
Resolving api.github.com (api.github.com)... failed: Name or service not known.
wget: unable to resolve host address ‘api.github.com’
- I've removed the actual github URL as it had my access token and private repo in it
Any ideas?
Level 50
If you're on digital ocean they're having problems with DNS just now : https://status.digitalocean.com/
Level 65
I'd probably add another DNS if that's the case. @ohffs Forgot that they probably use their own DNS for their servers, I always use a proper one.
Level 32
Sorry @bashy, what do you mean by 'add another DNS'? How would you set this up?
Level 50
@bashy I think DO default to using google's two main public dns's - I usually add a third fallback (and a personal peeve is that glibc only supports three, but that's another matter). But I guess forge just uses the defaults which is why so many folk are reporting problems here.
Anyway, it's nearly pub o'clock.... ;-)
Level 50
@domioanna edit the file /etc/resolv.conf and above the current 'nameserver' lines put an extra one like for opendns :
nameserver 208.67.222.222
That's how you'd do it on a server anyway - I don't use forge so not sure how you change the defaults there I'm afraid :-/
Level 65
@ohffs Oh was it an actual issue with DO connecting to Google's DNS? Surprised they don't have their own. Maybe they do for some services/OSs? I know my servers from OVH use OVH DNS.
Level 50
@bashy - yeah, I was a bit surprised that there didn't seem to be a pointer to their own or a fall-back in the default images (I've only used their Ubuntu & CentOS ones mind you). Although maybe after this they will change things a bit ;-)
1 like
Please or to participate in this conversation.