I have a droplet running Tornadoweb to serve some sweet REST apis and another droplet that hosts couchdb.
I have enabled private networking on both droplets however I am struggling to ping one from the other let alone
I want to block all public access to the droplet running couchdb, only the droplet running tornado should be able to read/write said couchdb droplet.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
And for the couchdb issue:
I change the bind_address in /etc/couchdb/default.ini to the droplets private IP address, so now I can access couch from the other droplet. I tried to curl the droplet from my local computer and could not access couch as desired.
To answer the ping part of my question. One of the droplets was made before I selected enable private networking and as such I hadn’t followed the guide properly to set up the interfaces.
I can now ping the droplets via their private ip addresses. Still no luck on access to couchdb, though. https://www.digitalocean.com/community/tutorials/how-to-enable-digitalocean-private-networking-on-existing-droplets