#techsheepdog_error

1 messages ¡ Page 1 of 1 (latest)

viscid furnaceBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1218053101873791076

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

oblique vectorBOT
arctic iron
#

dj-stripe is a community library that isn't supported by Stripe officially. We don't how it is implemented. I'd recommend reaching out the library developers or Support on why the error was thrown.

lofty hawk
#

The developer acts like he's got official stripe support and has even tried to hire me to work on that library under the idea that stripe is funding him and says I would be working for stripe indirectly. Are you saying that's not the case?

#

I'm astounded by the poor quality of the library in my attempts to use it so far.

#

But I'm under the impression that it's officially supported by stripe.

arctic iron
#

dj-stripe is not a Stripe official library. It's a community library sponsored by Stripe, but not maintaining by Stripe

lofty hawk
#

Please let me know if there is an official connection between stripe and that library or not. I'm worried because I've had zoom conversations with the maintainer and he's made it sound like there's an official connection and is getting funding from stripe. As part of this, he actually offered to hire me part time to work on the library and ship a version 3 of that library, Saying that he had stripes monetary support and could fund that through that connection.

#

But there's a larger issue here in that. multiple software projects are expecting a specific format for the keys generated by the dashboard, and the dashboard is not giving me keys in that format.

oblique vectorBOT
lofty hawk
#

If I add the prefix that the code is expecting, I just get authentication errors so it doesn't even look like the dashboard is giving me correct keys.

#

I don't think the guy would release code that didn't work. So in my mind, I was worried that stripe is updated something on the dashboard or changed the format of the keys.

flint canyon
#

As river has mentioned, dj-stripe is a community library sponsored by Stripe. I'm not too sure what you're expecting when you say official connection

with regards to the keys - in most cases, your secret key will have the prefix sk_test_ or sk_live, and the publishable key pk_test or pk_live. If you have a key that is really old, it's possible that it may not follow the above format

lofty hawk
#

That's just it. The secret key generated by the dashboard does not have any kind of prefix, starting with SK or have any kind of word test or live in it at all.

flint canyon
lofty hawk
#

And it's modern. It was provided recently

#

req_LiwRNsxWaOPAGK is a delete i made earlier

#

it shows up in the request logs for that key in the dashboard

#

I go to the secret key, click the triple dot menu. select view request logs and that particular request is at the top of the list.

#

But DJ stripe itself is bombing out anytime. It tries to be used because it's not using a prefix.

#

The publishable keys on the dashboard that it shows me all have the PK test prefix.

#

But the secret key has no prefix at all

#

And when I check the code for dj stripe, that's why it's choking, because that code is expecting it to have a prefix.

flint canyon
#

it's fine that the secret key has no prefix, this Stripe account is just really old and predates before we started following that format for secret keys

lofty hawk
#

My problem is I can't use any of the publicly available tools or libraries because they all expect the prefix.

#

And I'm sure I'm not the only one

flint canyon
lofty hawk
#

That wasn't valid traffic. That was debugging traffic from a test run that failed because the customer object was passed to an argument and not the customer ID

#

I'm honestly not sure how that got sent because it wasn't working either way

#

Also keep in mind that that was a raw stripe call, not using DJ stripe

flint canyon
#

but okay, if you need the secret key to start with sk_, you can create a new secret key

#

the new secret key should follow the format

lofty hawk
#

So you're telling me that I can fix this by rotating the key?

flint canyon
#

i wouldn't recommend rolling the old key immediately. I would create a new secret key first (the new key should have the format of sk_, replace the old key whereever necessary first, make sure there are no new requests coming in with the old key, then delete the old key

lofty hawk
#

Yeah, I think my biggest issue right now is that every time I try to work on an integration with stripe it's either the documentation and the fact that it's not very blind accessible that gets in the way. Or I have issues like this. I'm at the point now where I'm struggling to get web API callbacks to work. so this is a new problem for me because I've never been at this far into it before.

#

I don't have a way to add another secret key

#

The only option I'm given is to rotate it

#

Is that also something that I should have in your accounts that I don't have on this account? How do I make sure the account is updated and correct and allows me to do the modern things because I don't seem to be able to do everything and I've noticed that even getting to the page where my keys are doesn't seem to fit the documentation.

flint canyon
#

I don't have a way to add another secret key. The only option I'm given is to rotate it

You might need to check with the owner if they can see any option to add a new secret key. It could be an option that only the owner or administrator of the account has access to

lofty hawk
#

I am the owner

#

I should be the only person on the account

#

No other people should have owner or admin access

flint canyon
#

hrm, well, i guess the only option is to roll the key then. I don't think you have any active payments on this account at the moment so it should be fine to go ahead

lofty hawk
#

Are you saying other people have access?

flint canyon
#

i don't know. Most folks who join the channel are the developer and are not necessary the owner

#

that's why i phrased it the way i did

lofty hawk
#

oh ok understood

#

Ok, then I will rotate all the keys tomorrow, but it's after 10 here, so not doing it tonight. Thank you for everything.

#

It just sucks to know that my account is so old it's. age is actively getting in the way of getting stuff done and that's why things have been so hard.

#

I do notice that I have multiple public keys on the account. Is that normal?

flint canyon
#

it could be that a long time ago, you created another public key

lofty hawk
#

I can't seem to delete either one of them.

#

OK, so I refreshed the page and now I can delete that. That's very odd, but thank you.

flint canyon
#

great! feel free to reach out again if you're still having trouble tomorrow

lofty hawk
#

I just looked at the dates on the keys, and, yeah, its been a minute.