Glad you got something working. It’s best to run everything with the same provider so all parts of the system have less latency and network issues.
I’m still curious what is causing you to not successfully upload to DO. My initial guess is a firewall setting on your local machine or at DO.
Still could be, for sure. However, DO I updated iptables, ufw, etc. My windows machine I confirmed every port Wappler and Docker were seeking - and the strange 2575 port error (screenshot above) were open and or I opened them in/out.
Here is what I do know: It is very hard for me to be faced with a simple task that creates feelings of frustration even after tens of hours of efforts to no avail.
Nonetheless, I do appreciate your thoughts and efforts in this thread.
~Elle
@kfawcett Agreed, in most circumstances. I will certainly circle back to what the Heroku db offerings are; I have never used the platform.
I like DO since I already understand clusters, back up, high availability, distributed read only, etc. More than anything I just wanted to get something up and going. I'm a long way away from load and latency A/B testing. Yet, however, your point is quite valid and is appreciated.
~Elle
Hi Elle,
Glad you got it working on more easy way!
We’re you able to use SSH terminal to the DO server?
You could open the SSH terminal from the context menu in the Resource Manager when you have your DO server selected
Docker also uses SSH for deploys to cloud servers defined in Resource Manager and SSH uses port 22 on the remote servers, so this port should be open
This is why I asked about your firewall. You must have ports 22 and 2376 open.
Digital Ocean Firewall:
UFW (run sudo ufw status in the SSH Console to see output):
Glad you have sorted it, although not on DO, still a step forward!
@Cheese Yes; 2376, 8080, 3001, and a few others, yes. 
Yes. Everything was proper according to instruct in Resource Manager + SSH success.
*shrug
~Elle
