this post was submitted on 15 Nov 2024
19 points (100.0% liked)

Selfhosted

40198 readers
507 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
19
Raspberry pi 5 sometimes loses wireless connection (sh.itjust.works)
submitted 1 day ago* (last edited 1 day ago) by arudesalad@sh.itjust.works to c/selfhosted@lemmy.world
8 comments fedilink hide all child comments
 

This is a problem I have been having for a while and I thought I had fixed it but it has recently returned.

Sometimes my raspberry pi will lose connection on a random device. Sometimes it's tailscale, sometimes it's wlan, sometimes it's both. It still shows as connected in my router even when it is unreachable. When I can access it through one device while the other is down I check for errors but can't see any. If left alone for long enough it will fix itself (today it fixed itself after 6 hours) or I can reboot if I still have access to ssh through a working device.

To fix it last time I fixed wireless localisation settings (it was set to us instead of gb) but it being fixed after that change might have been a coincidence.

My only idea for why it doesn't always work is because of a range extender I have upstairs (where the pi is) which is connected to the network using fritz! mesh. I think it's a bad idea since it is placed very close to the main router (almost directly above) but my dad insists on having it.

top 8 comments
sorted by: hot top controversial new old
[–] Jozzo@lemmy.world 3 points 1 day ago (1 children)

I had a similar problem, it was caused by undervoltage. Are you using the official power supply?

[–] arudesalad@sh.itjust.works 1 points 1 day ago (1 children)

Yes

[–] HurlingDurling@lemmy.world 2 points 1 day ago

How many and what kind of accesories do you have plugged into it?

[–] just_another_person@lemmy.world 5 points 1 day ago (1 children)

Need logs to be able to tell you much. Get some output from dmesg after it happens, but before a reboot. Syslogs couldn't hurt. Maybe setting up a metrics exporter to another machine could give you a peek into what is happening with resources.

Also give some details about OS and what you're running on it.

[–] arudesalad@sh.itjust.works 1 points 2 hours ago (1 children)

Just happened again, no errors in the network manager log. I am running an up to date version of raspberry pi os. The only bare metal program I am running is pihole, the rest are in docker. I'll send a list of the containers when I can.

[–] just_another_person@lemmy.world 2 points 39 minutes ago

It's more important to get that dmesg output AFTER an event happens, but before a reboot. What you're running doesn't matter much unless you have live metrics of their behavior or resources.

[–] BrianTheeBiscuiteer@lemmy.world 2 points 1 day ago (1 children)

Maybe a dumb question but what kind of case do you have? Hopefully not metal because I had some crazy wifi behavior before I realized the case was either dampening the signal or capturing too much noise.