Unable to add a new server and database using Heroku Integration

[julisbf]

Hi there,

Background

A couple days I was able to create a new server and database using Prisma Cloud UI, and worked perfectly.

Problem

Yesterday, I decided to delete everything and tried again for my current project but it didn't work as before.

When I try to create the database container in Heroku through Prisma, am getting GraphQL Error: Invalid Credentials Provided and it stays creating the db.

I also tried to create the db directly in Heroku, then added in Prisma successfully but when I tried to add a new server, showed the same GraphQL Error.

Thanks!

[ArnieGA]

I'm having this exact same issue

[siddhant1]

Having the same exact issue !

[man-vu]

Having struggled with this problem for hours from creating new accounts to faking my IP to other countries, I finally managed to fix it by using Incognito Browser (Ctrl + Shift + N)

[ArnieGA]

@crystal-rhodes : I'm sorry to have to report that your solution did not work on my end. I tried your approach on different browsers and it didn't work on any of them.

[man-vu]

@ArnieGA : It sounds weird. When I deleted all of my cookies from Prisma and Heroku in my Chrome, it worked even when I ran it in browser's normal mode.

[siddhant1]

@crystal-rhodes I will try it in incognito mode and update here!

[jameschetwood]

Im having the same issue. Trying it in incognito didnt fix it.

Update: I created a new Prisma and Heroku account with a new email address and it worked.

[i8ramin]

I'm getting a few different errors in my web console

Mixed Content: The page at 'https://app.prisma.io/ramin/servers/create-heroku-db' was loaded over HTTPS, but requested an insecure resource 'http://dynamodb.us-east-1.amazonaws.com/ping?x=9CxObkMjauCTB7iNdWVBDiGw'. This content should also be served over HTTPS.

and also

GET http://dynamodb.us-east-1.amazonaws.com/ping?x=t7q5UlF5bikJhZEInoW3jn4C 404 (Not Found)

Possibly related

[ArnieGA]

Have you guys tried unlinking the heroku account with the new feature added a couple of days ago, and then re-adding it? (https://github.com/prisma/prisma-cloud-feedback/issues/200#issuecomment-438677302)

[i8ramin]

This is also happening to me. A few related issues: https://github.com/prisma/prisma-cloud-feedback/issues/200 https://github.com/prisma/prisma-cloud-feedback/issues/201

I've tried many things, including:

• incognito window
• deleting workspace and creating new one
• unlinking Prisma Cloud from Heroku
• unlinking Heroku from Workspace settings (which fails)
• etc etc

Nothing seems to work. Here are a few screenshots of errors I am seeing:

[ArnieGA]

@i8ramin: the incognito and cookie deletion solution really doesn't work. I believe that part of the issue that was causing this situation before was the fact that prisma.io's system had no way to unlink/re-link from/to the heroku account we used. And that's why we were always encouraged to create new heroku accounts and use those (which was honestly very unpractical).

However, when I tried removing the heroku account for the first time, after the new feature implementation, I checked the option to "Delete the listed servers and dynos from Heroku" unnecessarily because I had already removed them manually over at heroku. By doing so, when I clicked the Remove Account button afterwards, I got an endless process, just like the one you show on your first image (with the red button's label reading "...removing account"). After hitting the back button and trying again without checking that option, everything worked fine.

So I'm inclined to ask: Have you made sure that the server and dyno related to your project exist at heroku.com, and, did you check the option to delete them while removing the server at prisma.io?

[i8ramin]

I've deleted the old Heroku app and trying to go through the flow from scratch, but to no avail. I'm unable to unlink Heroku from my main Prisma account. Im able to link and unlink it to new workspaces, but then I can't add any heroku services (I get different errors, highlighted above). I'm in touch with the Prisma support team and they're looking into it. I'll update this thread if/when I have more details.

Meanwhile, Im going down the AWS Fargate route -- https://www.prisma.io/tutorials/deploy-prisma-to-aws-fargate-ct14 ..

[Nedomas]

Hey @i8ramin - I've also been stuck in the "Invalid credentials" situation for a few months.

Was happy for a potential fix, but this update did not fix it for me. I am able to remove/add Heroku accounts, but cannot create Postgres database (I still get "Invalid credentials"). The only thing that has always been working is just creating a new Heroku account and linking it to the same Prisma cloud account (not practical, but what can we do).

Ping me if the dev team need any logs, etc.

[bryanburkeone]

I've just got it to work. Its about 1 am and I was just brainlessly toying with it but these are the steps I remeber doing.

1. tried to create a server...failed
2. went to heroku>account setting>applications and took prisma off Authorized Applications
3. then went to heroku account tab and set up Two-factor Authentication...which gives me a new token
4. went back to prisma and deleted heroku connection
5. logged off and back on to prisma
6. set back up heroku connection tried to create another server...success

[Nedomas]

@bryanburkeone Tried the same exact steps, but I still get Invalid credentials when creating a server on Prisma Cloud. Maybe it's stuck at different parts of the process.

[ArnieGA]

Happy to report that apparently the fix on #200 resolved this issue for me.

https://github.com/prisma/prisma-cloud-feedback/issues/200#issuecomment-438677302

[marcjulian]

I'm having the same problem. I removed the Heroku connection and added it again but it still doesn't let me create a Prisma Server on Heroku.

[mjd]

Also Having this same problem.

Tried removing and adding heroku account. Tried switching to firefox (from chrome). Still broken.

[pulpopurpura]

Has there been any resolution to this? I'm encountering the same problems, trying the same solutions, and getting nowhere? The original problem surfaced because I had two many apps in Heroku, so the process of adding one in the Prisma flow got interrupted. Now, no matter what I do (deleting Heroku from Prisma, deleting Prisma from Heroku, using private browser) I keep getting the GraphQL error regarding wrong credentials.

[msmedes]

I second what @pulpopurpura (and many others) said, I haven't had much luck in the past few weeks either.

[Code178]

My solution to this problem was:

I went to https://app.prisma.io/MY_PRISMA_USERNAME(HERE COMES YOURS)/settings and then I scrolled down and hovered over the account that is connected to Heroku. Then, I clicked on "REMOVE" and clicked on remove the associated links on Heroku.

Finally, I tried again to add a new server via prisma and it worked.

Best Regards

[kemaldotearth]

Experiencing this problem right now, if I am to delete my Heroku user, do I also lose the server on Prisma end? I ask because it's being used by a live project.

[Hemistone]

I think this maybe happens if you change password or something of your heroku account, which means the solution is to remove your heroku accont configuration(account only, not the whole other heroku servers you deployed all together) and re-login again heroku in the making server step.

I also got "GraphQL error: Invalid credentials provided." but after removing account info on the user settings and re-login it during the server/database creation step, it solved. Maybe this comes in error because prisma admin does not update your heroku account info by real time (ex. prisma admin does not know whether you changed your something in heroku). Just my assumption, not fact. thanks.