Chip Marshall

These snapshots are created using `pg_dump "${DB}" | restic --quiet backup --stdin --stdin-filename "${DB}.sql"` `restic cat snapshot` output: ``` { "time": "2022-07-18T06:29:46.443661036Z", "tree": "830d3f49b4929dff1ca5d91b92a563959ecddba172e194e32149f4dbf342e0b7", "paths": [ "database.sql" ], "hostname": "db-primary01",...

Seeing the same problem here. It appears vagrant is repeatedly trying to SSH to the droplet, but isn't authenticating. I can run `vagrant ssh` alongside the `vagrant up` after it...

Happened to be running into this again and did a bit more digging. With `vagrant up --debug` I noticed the following message: ``` INFO ssh: SSH not up: #

Just did some quick testing on an 11.0 droplet w/ IPv6, and it all looks good to me.

I asked around a bit internally, and it doesn't look like we have an official policy, but I was pointed at [koalalorenzo/python-digitalocean](https://github.com/koalalorenzo/python-digitalocean) as an example of another 3rd party project...

Yeah, this is still relevant to my interests. I should have some time later this week to look at writing up a port Makefile.

Same issue here, tried doing user:pass@host in the URL, but that didn't work either.