Selfhosted

40018 readers

575 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:

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.
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.
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).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Articles on self-hosted servers not propagated? (lemmy.world)

submitted 1 year ago by twitterfluechtling@lemmy.world to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

I set up a self-hosted instance yesterday, so far it runs fine. I can subscribe from there to communities hosted on other instances, I can comment from my instance and the comments show up on other instances.

However, I subscribed to https://lemmy.world/c/lemmyworldtest from my own instance to test if my posts will be propagated, and that seems not to work (yet?).

Is this a known problem? Would the upstream instance subscribe to my instance for this to work? Or is this a bug in my configuration?

you are viewing a single comment's thread
view the rest of the comments

[–] twitterfluechtling@lemmy.world 2 points 1 year ago (1 children)

Ok... After changing some settings, I got this log:

2023-06-13T15:16:56.808411Z ERROR HTTP request{http.method=GET http.scheme="http" http.host=lemmy.pathoris.de http.target=/api/v3/ws otel.kind="server" request_id=6603f30f-4523-4548-a82c-f38c22d1889f http.status_code=101 otel.status_code="OK"}: lemmy_server::api_routes_websocket: only_mods_can_post_in_community: only_mods_can_post_in_community

That explains a lot, I think :-)

Apparently my instance does try to push, as I expected, but the community is protected on lemmy.world. That's a bit surprising still, since I thought it is a test group to test federation and such, but since that wasn't specified anywhere, it's fair enough that this could be a test-group by lemmy.world for lemmy.world :-)

[–] twitterfluechtling@lemmy.world 2 points 1 year ago

Btw: The settings I changed on my server were removing all servers from the "allowed" list. It seems I misunderstood the instructions during setup, I thought I had to add some servers quasi as a seed. But actually, by giving permission to certain servers, it is implied that I don't want to allow any other.