There aren’t any posts on any communities on my instance yet which might be an issue, sure.
What error are you getting when trying to post?
I do see that there is a post from you around half an hour ago. Something that is odd to me is that rDataHoarder shows rDataHoarder@geekroom.tech where as rhomelab just shows rhomelab lol
I’m guessing that it’s because a federated post was made to it? A local post made to it didn’t change how it shows in rhomelab
can your instance still see mine and post to it? Asking because I haven’t gotten any new posts in 24 hours when I know those same remote communities have newer content than that. Additionally, I can’t see any comments that have previously been made…and my comments still don’t sync and show up in the original posts feed.
can your instance still see mine and post to it? Asking because I haven’t gotten any new posts in 24 hours when I know those same remote communities have newer content than that. Additionally, I can’t see any comments that have previously been made…and my comments still don’t sync and show up in the original posts feed.
I had to set it as this because if I used port 1234 for lemmy-ui then it would give me 502 bad gateway errors.
set $proxpass "http://127.0.0.1:10633/";
if ($http_accept = "application/activity+json") {
set $proxpass "http://127.0.0.1:8536/";
}
if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") {
set $proxpass "http://127.0.0.1:8536/";
}
But this works.
So when I look at the docker-compose file, the only exposures are 10633 on nginx-proxy which routes to 8536. Docker ps -a is showing lemmy-ui as 1234/tcp and lemmy as 8536.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
530dd3852e24 nginx:1-alpine "/docker-entrypoint.…" 15 hours ago Up 15 hours 80/tcp, 127.0.0.1:10633->8536/tcp geekroomtech-proxy-1
e5976396c4f2 dessalines/lemmy-ui:0.19.9 "docker-entrypoint.s…" 15 hours ago Up 15 hours (healthy) 1234/tcp geekroomtech-lemmy-ui-1
a91f86523a95 dessalines/lemmy:0.19.9 "lemmy_server" 15 hours ago Up 15 hours 8536/tcp geekroomtech-lemmy-1
15c8a65b2e02 asonix/pictrs:0.5.16 "/sbin/tini -- /usr/…" 15 hours ago Up 15 hours 6669/tcp, 8080/tcp geekroomtech-pictrs-1
135f75ceccf4 pgautoupgrade/pgautoupgrade:17-alpine "/usr/local/bin/dock…" 15 hours ago Up 15 hours (healthy) 5432/tcp geekroomtech-postgres-1
So you’re saying it should look like this instead?
set $proxpass "http://0.0.0.0/:1234";
if ($http_accept = "application/activity+json") {
set $proxpass "http://0.0.0.0/:8536";
}
if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") {
set $proxpass "http://0.0.0.0/:8536";
}
proxy_pass $proxpass;
is that right?
hmm… ok. I’m guessing it’s maybe the instances that i’ve tried searching on that aren’t picking it up yet or something. Because here on lemmy.world and also sh.itjust.works neither are picking up my instance.
Yes, set it up today. Was having issues with sending emails only to find out I had to just specify a different “hostname” in the lemmy.hjson file other than GeekRoom.Tech… so www.geekroom.tech got that working.
I enabled the lemmy_federation trace settings and am seeing that it is finally federating and trying to send updates. Being that no one but myself is on it currently, I’m not terribly surprised by the instances being “behind”.
Example:
2025-02-28T00:32:14.394971Z DEBUG lemmy_federate::stats: lemmy.nz: Ok. 1 activities behind
2025-02-28T00:32:14.394974Z DEBUG lemmy_federate::stats: lemmy.blahaj.zone: Ok. 1 activities behind
2025-02-28T00:32:14.394976Z DEBUG lemmy_federate::stats: lemmy.cafe: Ok. 1 activities behind
2025-02-28T00:32:14.394979Z DEBUG lemmy_federate::stats: libranet.de: Ok. 1 activities behind
2025-02-28T00:32:14.394982Z DEBUG lemmy_federate::stats: theprancingpony.in: Ok. 1 activities behind
2025-02-28T00:32:14.394984Z DEBUG lemmy_federate::stats: lemmy.cloudhub.social: Ok. 1 activities behind
2025-02-28T00:32:14.394987Z DEBUG lemmy_federate::stats: lemmy.dbzer0.com: Ok. 1 activities behind
2025-02-28T00:32:14.394990Z DEBUG lemmy_federate::stats: monero.town: Ok. 1 activities behind
2025-02-28T00:32:14.394992Z DEBUG lemmy_federate::stats: lemmy.hybridsarcasm.xyz: Ok. 1 activities behind
2025-02-28T00:32:14.394995Z DEBUG lemmy_federate::stats: 1337lemmy.com: Ok. 1 activities behind
2025-02-28T00:32:14.394998Z DEBUG lemmy_federate::stats: palaver.p3x.de: Ok. 1 activities behind
2025-02-28T00:32:14.395001Z DEBUG lemmy_federate::stats: jlai.lu: Ok. 1 activities behind
2025-02-28T00:32:14.395003Z DEBUG lemmy_federate::stats: lemmy.toldi.eu: Ok. 1 activities behind
2025-02-28T00:32:14.395006Z DEBUG lemmy_federate::stats: discuss.online: Ok. 1 activities behind
2025-02-28T00:32:14.395013Z DEBUG lemmy_federate::stats: lemmy.crimedad.work: Ok. 1 activities behind
2025-02-28T00:32:14.395016Z DEBUG lemmy_federate::stats: mander.xyz: Ok. 1 activities behind
2025-02-28T00:32:14.395018Z DEBUG lemmy_federate::stats: programming.dev: Ok. 1 activities behind
2025-02-28T00:32:14.395021Z DEBUG lemmy_federate::stats: fedia.io: Ok. 1 activities behind
2025-02-28T00:32:14.395024Z DEBUG lemmy_federate::stats: pawb.social: Ok. 1 activities behind
2025-02-28T00:32:14.395027Z DEBUG lemmy_federate::stats: feddit.it: Ok. 1 activities behind
2025-02-28T00:32:14.395030Z DEBUG lemmy_federate::stats: lemmy.blackeco.com: Ok. 1 activities behind
2025-02-28T00:32:14.395032Z DEBUG lemmy_federate::stats: www.foxyhole.io: Ok. 1 activities behind
2025-02-28T00:32:14.395035Z DEBUG lemmy_federate::stats: lemmy.world: Ok. 1 activities behind
2025-02-28T00:32:14.395038Z DEBUG lemmy_federate::stats: sopuli.xyz: Ok. 1 activities behind
2025-02-28T00:32:14.395041Z DEBUG lemmy_federate::stats: lemmy.nowsci.com: Ok. 1 activities behind
2025-02-28T00:32:14.395043Z DEBUG lemmy_federate::stats: lemmy.thewooskeys.com: Ok. 1 activities behind
2025-02-28T00:32:14.395046Z DEBUG lemmy_federate::stats: startrek.website: Ok. 1 activities behind
2025-02-28T00:32:14.395058Z DEBUG lemmy_federate::stats: lemmy.zip: Ok. 1 activities behind
2025-02-28T00:32:14.395061Z DEBUG lemmy_federate::stats: hackertalks.com: Ok. 1 activities behind
2025-02-28T00:32:14.395064Z DEBUG lemmy_federate::stats: feddit.online: Ok. 1 activities behind
2025-02-28T00:32:14.395067Z DEBUG lemmy_federate::stats: midwest.social: Ok. 1 activities behind
2025-02-28T00:32:14.395070Z DEBUG lemmy_federate::stats: kbin.earth: Ok. 1 activities behind
2025-02-28T00:32:14.395072Z DEBUG lemmy_federate::stats: feddit.rocks: Ok. 1 activities behind
2025-02-28T00:32:14.395076Z INFO lemmy_federate::stats: 0 others up to date. 61 instances behind.
2025-02-28T00:32:14.662688Z INFO lemmy_federate: Federating to 61/61 instances (0 dead, 0 disallowed)
It appears that adding the below code has seemingly resolved the not receiving inbox messages part, but has not resolved anything else.
First, I disabled the Cloudflare proxying because I saw the troubleshooting guide mentions that Cloudflare proxy may cause issues.
Second, added the following:
# Attempting to resolve federation
set $proxpass "http://127.0.0.1:10633/:";
if ($http_accept = "application/activity+json") {
set $proxpass "http://127.0.0.1:8536/";
}
if ($http_accept = "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams/"") {
set $proxpass "http://127.0.0.1:8536/";
Originally, I had set the “hostname” in lemmy.hjson as just “geekroom.tech” but that was causing issues with trying to send email. So I changed it to the hostname of the server prd-pub-pod11.geekroom.tech" … then found out that when it sends emails, it uses that hostname as where to send people to in order to verify and login… no bueno.
So then I changed it to www.geekroom.tech and now just have a redirect at cloudflare for www to naked domain
It sounds like I need to reinit the entire install …