Hey,
When I try to add Flying Sphinx to my Heroku app, I get this message: "Could not create resource with vendor, please try again later"
Any help would be greatly appreciated! :)
Can't add Flying Sphinx add-on to Heroku
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by Pat Allan Support staff on 10 Dec, 2011 03:34 AM
Hi David
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?
Cheers
Pat
#2 Posted by David Gorman on 10 Dec, 2011 07:17 AM
Hey Pat,
Unfortunately, it looks likes it's still happening =/ Is there anything I can do on my end to help debug it?
#3 Posted by Pat Allan Support staff on 10 Dec, 2011 09:05 AM
Hi David
How are you adding it? Via the command line, or the web interface? If the former, can you show me the command you're using? In particular, knowing which plan will help... also, what's your app's name?
#4 Posted by David Gorman on 10 Dec, 2011 09:07 AM
I've tried both and receive the same error. Here's the exact command:
$ heroku addons:add flying_sphinx:ceramic -----> Adding flying_sphinx:ceramic to opal... failed ! ! Could not create resource with vendor, please try again later
That's when trying to add the ceramic plan. The app's name is opal. Hopefully this helps :)
#5 Posted by Pat Allan Support staff 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...
#6 Posted by David Gorman on 10 Dec, 2011 09:13 AM
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?
#7 Posted by Pat Allan Support staff 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 --longis? 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 orphaned.
#8 Posted by David Gorman on 10 Dec, 2011 09:24 AM
Hmm, no, it doesn't look like we've added Sendgrid. These are our add ons:
logging:basic
releases:basic
shared-database:5mb
ssl:piggyback
Is there any other way to get at that unique app ID? I'm wondering if this is it: jpjbkidhqg
#9 Posted by David Gorman on 10 Dec, 2011 09:28 AM
Scratch that, here it is: app1962227
#10 Posted by Pat Allan Support staff on 10 Dec, 2011 09:30 AM
Perfect - and it is the orphaned app, which I've just removed. Try adding the plan now!
#11 Posted by David Gorman on 10 Dec, 2011 09:32 AM
Yay! It worked! Thanks very much for the help. Sorry to be a pain :)
#12 Posted by Pat Allan Support staff on 10 Dec, 2011 09:35 AM
No worries, wasn't your fault... I just wonder why it got halfway through adding it the first time around. I'll have to keep an eye out for any further apps reaching that situation.