Linux

13082 readers

919 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

Weird networking issue, seeking help (piefed.ca)

submitted 3 days ago by iamthetot@piefed.ca to c/linux@programming.dev

21 comments fedilink hide all child comments

I run CachyOS on my desktop. I host Homepage for myself on a home server. This is reached at home.mydomain.tld. Pihole on my local network catches that request and points it at my local nginx, which reverse proxies me to the homepage.

Now, I set this all up a while back and it all worked totally fine for several weeks. Then, about a week or so ago, for some reason almost every, but not every time I boot my PC, home.mydomain.tld gives me a "cannot be reached" error in my browser... until I run systemctl restart NetworkManager and then it works completely normally.

Can anyone help me troubleshoot why oh why that would suddenly be a thing? Does anyone have suggestions of a way I can troubleshoot a permanent fix to this so that I don't have to restart NetworkManager almost every boot?

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

[–] ligma_centauri@lemmy.world 2 points 2 days ago

Do you have multiple NIC? I sporadically run into issues where traffic will try to route itself via a secondary network which has limited external access and it is resolved in a similar manner, by bringing down all networks, then re-starting them in a specific order.

Realistically I should probably define some static routes, but it works automatically 99% of the time so I never bother.

If this sounds like a possible cause, check your routes while in failed, and functional states, and set static routes as needed to resolve.