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.

  • Jozzo@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 month ago

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

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    1 month ago

    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.worksOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month ago

      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
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month 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
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    1 month ago

    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.