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

"jwt expired" Error when attempting to move PDS to another machine #153

Open
hugeblank opened this issue Nov 22, 2024 · 5 comments
Open

Comments

@hugeblank
Copy link

I set my PDS up temporarily on my PC, with the intent of reconfiguring the network ahead of it to point to a server that it would run on. I finally got around to that, and moved the PDS. Everything seems to work fine, like I can log into it through other apps (pdsls), but bsky.app refuses to work, emitting "jwt expired" when I log in and go to my profile. This is also confirmed by the majority of responses coming from my server returning an error 401 in the network tab.

To reproduce the issue:

  1. Set up an instance on machine A, and create an account.
  2. Shut down the instance, and sftp into machine B from machine A.
  3. Copy all the files from A to B.
  4. Reconfigure the network ahead of the machines to point the domain that was pointing at machine A to now point at machine B.
  5. Launch the instance on machine B
  6. Log out and log back in on bsky.app. Going to the profile tab should show "jwt expired" after a bit, along with a slew of 401 errors.
@pfaffman
Copy link

I've been wondering how hard it was to move to a new server.

Can you confirm that your new server is indeed responding as expected on the same URL as before?

Does https://YOURHOST/xrpc/_health give the version? Does https://YOURHOST give you the "This is an AT Protocol Personal Data Server (PDS): https://github.com/bluesky-social/atproto" message?

@hugeblank
Copy link
Author

Everything looks completely normal, feel free to see for yourself. It's hosted at pds.atproto.hugeblank.dev

@pfaffman
Copy link

I was afraid of that.

It could still be DNS lag, though. When I move Discourse sites to a new server, it often takes a browser that's connected to the old server to be convinced that it needs to drop the connection, get a new IP, and try again.

Oh, but maybe it's YOUR browser. Have you tried an incognito window? I just tried to create a handle on your domain and it correctly said that the invite code was bogus.

@hugeblank
Copy link
Author

hugeblank commented Nov 22, 2024

It's not DNS, it's been pointing to the right place properly for hours now, and it's not cache, I've cleared it for bsky.app and it still does not work
Edit: and just to entertain the thought I tried logging in through a browser I never use, and got the same error:
image

@hugeblank
Copy link
Author

I'll be keeping an eye on the atproto issue and close this one when that one is closed.

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

2 participants