Hi, so I launched my very own instance. I’m posting from here, and hopefully this post makes it there. I subscribed to a few coms, but I’m getting outdated posts and the votes don’t line up, also the comments do not all load. So I’m able to federate, but for some reason only some of the data is coming over to my server… Has anyone here been experiencing the same thing?
UI is 0.18.2 and BE is 0.18.1
I just wanna be able to browse other coms without having to constantly switch domain names and log in with another account just to participate.
edit: Here’s pics for comparison for a post on selfhosted.
How long has it been? If you just spun it up, what you’ve seen is just the initial pull of the content. As you subscribe, all new content will get pushed to you, but the old content never backfills.
Check your NGINX logs, you should see a bunch of POST requests to /inbox and status of 200 that looks like this:
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
How long has it been? If you just spun it up, what you’ve seen is just the initial pull of the content. As you subscribe, all new content will get pushed to you, but the old content never backfills.
Check your NGINX logs, you should see a bunch of POST requests to
/inboxand status of 200 that looks like this:Included a bunch, as you can see they should be coming in quite frequently, basically everytime someone does something on the remote instance.
Make sure you’re subscribed to the community as well
Basic curl testing seems to rule out common routing problems, so check the lemmy logs as well just in case.