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

Account lost ability to check discovery after migration #101

Closed
MilanBabuljak opened this issue Oct 21, 2024 · 3 comments
Closed

Account lost ability to check discovery after migration #101

MilanBabuljak opened this issue Oct 21, 2024 · 3 comments

Comments

@MilanBabuljak
Copy link

MilanBabuljak commented Oct 21, 2024

Hello, recently I've migrated one account to my self-hosted PDS. For that, I've used the script you've provided in documentation. Everything moved correctly, but the account lost the ability to see discovery feed. Following feed works as usual. The error message provided is 500 Interial server Error

image

I checked the devtools and I found this:

{
    "error": "checking jwt failed: failed to parse auth header JWT: token signature is invalid: crytographic signature invalid",
    "message": "Internal Server Error"
}

while trying to reach app.bsky.feed.generator/whats-hot. Other accounts on the same server can access discovery normally.

Any ideas how to fix this?

@bnewbold
Copy link
Contributor

we have a known issue around this related to caching of identity metadata which could impact accounts for up to 24 hours after they change atproto signing keys, which happens during account migration.

sorry about that!

@stephankaag
Copy link

@MilanBabuljak Was it indeed solved after 24H? I'm running into the same error.

@MilanBabuljak
Copy link
Author

Yep, can confirm that after all of migrated accounts started working (the most it took was 36h)

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

No branches or pull requests

3 participants