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

[tocashare] (updating) Error: The API key was not accepted by https://tocashare.com/. #15257

Closed
3 tasks done
brkr1 opened this issue Apr 18, 2024 · 4 comments
Closed
3 tasks done

Comments

@brkr1
Copy link

brkr1 commented Apr 18, 2024

Have you checked our Troubleshooting page for your issue?

  • I have checked the Troubleshooting page

Is there already an issue for your problem?

  • I have checked older issues, open and closed

Have you read our Contributing Guidelines?

  • I have read the Contributing Guidelines

Environment

It's now tocashare.biz

Description

It's now tocashare.biz

Logged Error Messages

An error occurred while updating this indexer
Error: The API key was not accepted by https://tocashare.com/.
Click here to open an issue on GitHub for this indexer.

Screenshots

No response

@ilike2burnthing
Copy link
Contributor

tocashare.com is working fine for me, are you sure you have entered the API key correctly?

I don't see any announcement about a change to .biz, and I'm not going to try to sign into it or use my API key with it, if there's nothing official. Can you point to something I have missed?

@garfield69
Copy link
Contributor

The .biz domain is a working alternate domain and I've updated the indexer to make it available again.
FWIW I checked and my existing apikey works for both domains.
So the OPs issue is either a genuine incorrect apikey (perhaps a cut/paste issue to the indexer config) or something else is interfering.

@garfield69
Copy link
Contributor

v0.21.2414

@jackettbot
Copy link

jackettbot bot commented Apr 25, 2024

Hi @brkr1,

No response has been received for 7 days. To prevent issue tracker clutter, this issue will now be closed. To re-open the issue, please provide the information requested and the issue will automatically re-open.

@jackettbot jackettbot bot closed this as completed Apr 25, 2024
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

3 participants