Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"We're unable to connect. Please delete your credentials and try again later" #52

Open
nontoxicmaxi opened this issue Feb 6, 2022 · 6 comments

Comments

@nontoxicmaxi
Copy link

Hi Miguel
Thanks so much for what seems to be amazing work!

I've followed your videos in creating the .mez file, and I'm 99% that my issue can't be there.

When opening Power BI, YT Connector appears in the Get Data, and then it prompts me to "sign in".

The message I'm getting is:

billede

When I hit "sign-up" there's a flash but no browser opens.

I've tried:

  • toggle "standard browser" option
  • create new credential and make new .mez file
  • delete credentials (although no YT permission appears)
  • cleared browser cache
  • restarts
  • different PC

What am I missing?

Thanks in advance.

@migueesc123
Copy link
Owner

Hey!

I no longer have a working app so I'm not able to reproduce the behavior.

However, that error and experience overall only happens when your .json file for the webapp isn't correctly defined as in there's something wrong when you zipped the mez or the json file itself isn't in the shape that is expected.

Sorry that I can't be of much help. Usually these sort of issues are related to the application itself and not something with the custom connector or anything that I have control over.

@muhammadh811
Copy link

@migueesc123 I am getting the exact error. Did you able to resolve it?

@prutson
Copy link

prutson commented Apr 4, 2022

I am getting this erro too. Someone resolved?

@Tbohunek
Copy link

For us the solution was use my default browser like here
We suspect it's related to .NET and TLS and we're looking for the right setup.

@migueesc123
Copy link
Owner

thanks for chiming in, @Tbohunek !

@NielsShared
Copy link

The solution suggested by @Tbohunek worked for me. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants