1

I'm trying to use the Chainlink External Adapter to connect my contract to Twitter but my node I'm running is seemingly not able to connect to the adapter at localhost:8080 even though the adapter says that's the port it's listening on. Specifically I'm getting the error, ExternalBridge post to external adapter: connection refused. Thoughts?

chainlink external adapter not connecting

3
  • 1
    Is your chainlink node and database also running locally? Can you call the EA from a curl command? Nov 3 '20 at 13:38
  • 1
    Yes, node, database, and adapter are currently all on the same machine. As I'm typing this though I'm realizing the node and database are each in their own docker container with their own IP which might be the issue. EA is running natively, no container. Localhost in the node container is not localhost of my native OS. When I run your example curl command, it works and the test Tweet is posted.
    – gmondok
    Nov 3 '20 at 16:01
  • 1
    Changed the Bridge spec in my Chainlink node from localhost to my machine's 192.168.1.X local IP and that fixed it. Thanks for the assist :)
    – gmondok
    Nov 3 '20 at 16:45
1

Changed the Bridge spec in my Chainlink node from localhost to my machine's 192.168.1.X local IP and that fixed it. Issue was my node was running in a docker container but the adapter was running on my native OS. So localhost from my node's perspective is not localhost from the adapter's perspective.

FYI: Can find your specific local IP by running "ip addr" on Linux and it will be the IP of your main interface, such as eth0. Can also see the docker IP this way.

2
  • This is great! How did you find that 192.168.1.X? Could you update your answer with that? Nov 3 '20 at 17:59
  • Sure, adding that to the answer now.
    – gmondok
    Nov 3 '20 at 18:07

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.