This kind of arbitrary rejection seems to be part of the learning curve of Rails applications, so I apologize for such a simple question, but: " heroku pgbackups:capture " is just ... unsuccessful. That is, I grabbed the URL of my Postgresql database onto the hero, then pasted it into:
% heroku pgbackups: capture postgres: // <secret rest of db URL>
... and get the following answer:
Database on ec2-50-19-215-116.compute-1.amazonaws.com ---- backup ---> b003
Awaiting ... \
! An error occurred and your backup did not complete.
Useful, huh? Any tips on how I can discuss this? Thanks for the help with the naive question.
Steve upstill
source share