Support Staff2 Posted by Pat Allan on 10 Dec, 2011 03:34 AM
From what I can tell from the error reports it seems there were
some DNS glitches (not sure if that was Heroku, Amazon or something
wider), but it's working fine for me now. Can you give it another
shot, let me know how it goes?
Support Staff6 Posted by Pat Allan on 10 Dec, 2011 09:09 AM
Annoyingly, works fine for me (using the Ceramic plan - I'd
tried earlier with Wooden). Is this app on Bamboo, or Cedar? Not
that it should matter, just wondering what other variables could be
causing the issue...
Very weird! The app is running on Cedar. I had one of our other
developers try it and he saw the same result, for whatever that's
worth. If it would help, I'd be happy to screenshare or something
to show you the problem directly. I do wonder though, are there any
other requirements on the Heroku side that may be getting in the
way? Like do I need to enable a background worker?
Support Staff8 Posted by Pat Allan on 10 Dec, 2011 09:19 AM
I don't suppose you're using Sendgrid for email? If you are, can
you let me know what the SENDGRID_USERNAME value from heroku
config --long is? I've found an orphaned record in my
database (no idea how that happened, not seen it before), but
wondering if it's your app.
Heroku provides the unique id for an app as something like
[email blocked] - and
conveniently, that's what Sendgrid uses for their usernames, hence
why this could let us check whether it's the app that's been