this post was submitted on 13 Jul 2023
17 points (100.0% liked)

Selfhosted

40154 readers
595 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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.

my instance [22 replies, 28/3 votes]

lemmy.world instance [20 replies, 61/3 votes]

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

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:

54.36.178.108 - - [13/Jul/2023:01:10:16 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:16 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:17 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:17 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:18 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:19 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"
54.36.178.108 - - [13/Jul/2023:01:10:19 -0400] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.18.2; +https://lemmy.ml"

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.