sleepybear

joined 1 year ago

I worked out this was odd behavior on my OPNSense firewall NAT rules.

For some reason some syncing worked (eg. beehaw.org) but new connections failed. I'm not sure why. Maybe established sessions were kept alive.

Those rules haven't changed in months and months, so I'll chalk that up to "weirdness".

Yeah, I’ve tried that a couple of times too.

And run through all the federation troubleshooting steps in the docs.

[–] sleepybear@lemmy.myspamtrap.com 1 points 6 months ago (2 children)

I thought that, and in the past I’ve been off for a day or two and always caught up.

This time I haven’t and it’s been a week or two since coming back online.

 

Hey all,

My personal home-hosted server ran out of disk space and so went offline while I was away and I didn't notice it for a week or two.

This meant that federation requests (or subscriptions requests) went offline and now most of the servers I'm federated with are lagging. I'm only getting updates from a couple.

Is there a way to trigger federated servers back to life so I get the subscription updates? Federation does seem to be working, given some servers seem to federate fine and this post was via federation and has worked.

8
submitted 1 year ago* (last edited 1 year ago) by sleepybear@lemmy.myspamtrap.com to c/lemmy_support@lemmy.ml
 

Hey,

On my local lemmy I noticed that after trying out Tailscale I borked my federation connectivity (at least I think that was it).

I've rolled back changes, but noticed that most of my federation updates aren't flowing, and I can't even subscribe to a local community.

However, I can subscribe to a remote one, but only one of quite a few I was previously connected to.

No errors in the logs, and everything seems to be working otherwise.

Any ideas of where to search?

Activity updates from logs:

lemmy_1     | 2023-09-11T22:07:35.820559Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 41, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820579Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 42, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820602Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 43, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820622Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 44, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820653Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 45, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820674Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 46, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820696Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 47, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820717Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 48, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:07:35.820738Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 49, running: 0, retries: 0, dead: 0, complete: 0
lemmy_1     | 2023-09-11T22:09:26.317267Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 1, running: 0, retries: 14, dead: 0, complete: 35
lemmy_1     | 2023-09-11T22:09:27.658199Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 1, running: 0, retries: 14, dead: 0, complete: 36
lemmy_1     | 2023-09-11T22:09:29.009600Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 1, running: 0, retries: 14, dead: 0, complete: 37
lemmy_1     | 2023-09-11T22:09:29.899976Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 1, running: 0, retries: 14, dead: 0, complete: 38
lemmy_1     | 2023-09-11T22:10:00.253091Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 1, running: 0, retries: 14, dead: 0, complete: 39
lemmy_1     | 2023-09-11T22:10:02.139038Z  INFO send:send_lemmy_activity: activitypub_federation::activity_queue: Activity queue stats: pending: 1, running: 0, retries: 14, dead: 0, complete: 40

That pending: 1 never clears. Not sure how to identify it.

This was posted through federation, from my local instance - so, obviously bits and pieces are working just fine.

[–] sleepybear@lemmy.myspamtrap.com 2 points 1 year ago (1 children)

Given this is !privacy and the advertise as front page features both “works will all your messaging apps” and “end to end encryption”, it seems important to flag currently those aren’t mutually compatible.

It’s not their fault the apps don’t have e2e APIs, it’s a tough problem, but the secrecy and privacy guarantee is just “trust us to stick to our policy”. And they’re a start-up, tooling isn’t perfect (or even exist), mistakes happen, etc

Their self-hosting looks interesting, but then it said to use your own clients too, which took the fun out of that.

[–] sleepybear@lemmy.myspamtrap.com 11 points 1 year ago* (last edited 1 year ago) (4 children)

For example, if you send a message from Beeper to a friend on WhatsApp, the message is encrypted on your Beeper client, sent to the Beeper web service, which decrypts and re-encrypts the message with WhatsApp's proprietary encryption protocol.

So, not really end to end for most common use-cases.

I agree, that would be more authentic. Or rig up an actual line printer.

But I think the fuzzy old terminal emulator at full screen gives you a more accurate view of an old curved, flickery, low-res screen.

Event a TTY on a modern screen is going to be higher res (far more than 80x24), nice crisp fonts, colors, etc.

[–] sleepybear@lemmy.myspamtrap.com 2 points 1 year ago (2 children)

Should have used https://github.com/Swordfish90/cool-retro-term instead of gterm for the real flickery tiny terminal experience

I really don’t like the “but otherwise we’d need a warrant” approach.

Yes, of course you should need a warrant. That’s the bit that’s the safeguard and actually is the checks and balance against abuse. It’s not a problem to be optimized away.