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

Posts didn't show up after changing PDS domain #5446

Open
astrojuanlu opened this issue Sep 21, 2024 · 0 comments
Open

Posts didn't show up after changing PDS domain #5446

astrojuanlu opened this issue Sep 21, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@astrojuanlu
Copy link

Describe the bug

I suspect there's a bug in the Bluesky app when a custom PDS changes its domain name.

I was running a custom PDS on bsky.juanlu.space, everything was working well.

At some point I decided to change the domain name, so I added a DSN A record pds.juanlu.space pointing to the same IP, changed the Caddyfile and pds.env, restarted the service. I was able to log in and browse the network, so for a few days I thought everything had worked fine.

However, at some point I found out that my posts weren't being shown. I would refresh my profile page and see nothing.

I started digging. The POST /xrpc/com.atproto.repo.createRecord was returning a valid record with "validationStatus":"valid". The /xrpc/com.atproto.sync.subscribeRepos WebSocket was showing my new posts. And yet, new posts weren't showing in the app.

I also noticed that the app wasn't able to retrieve my avatar. But the avatar for old posts was showing fine.

I am not a TypeScript coder nor ATProto expert so it would have taken me a while to debug this without assistance. So I decided to revert to the last working configuration hoping that I hadn't broken anything.

I changed the DNS back to bsky.juanlu.space, reverted the configs, restarted the service, and the app caught up with all the posts that I had written. So now everything is back to normal.

To Reproduce

(see above)

Expected behavior

Everything should continue as normal even after changing the domain name.

But maybe this is either (b) an improper expectation because $cryptography or whatever or (c) I did miss some config that I should have changed, so error was between chair and keyboard. Happy to dig a bit more with some assistance (I'm fine using my own account as guinea pig).

Screenshots

Details

  • Platform: Firefox on desktop Linux Mint
  • Platform version: 130.0
  • App version: Build version: 1.91.1; Bundle info: 49ab486 (prod); Bundle date: 24092017; Platform: web

Additional context

@astrojuanlu astrojuanlu added the bug Something isn't working label Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant