Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Is there a DHCP server at play? Is the static IP outside of the DHCP range? This does sound like a typical IP collision.
DHCP is enabled on the router, but I believe the IP address is outside the designated DHCP range.
I'll double check when I'm home!
Edit: I will also say that this modem/router is dedicated only for the server, so there shouldnt be any other clients on it at all.
This might not be applicable to your use case, but maybe it helps.
Couple of years ago I had a problem where ONE windows laptop was unable to access the internet. Sometimes it would work right away, sometimes it took 1 or 2 reboots, sometimes the damn thing wouldn't budge.
lo and behold, it turns out the windows laptop was assigned a DHCP address that one linksys router had as a static ip. Why that resulted in a sporadic error and not a constant one I'll never know.
So next time you have this issue, rip out the network cable from the server and try to ping the ip the server is supposed to have.
Other than that, check the journal if something start to pop up around the time you experience the problem.
Thanks for the suggestion. So I have the static IP assigned with DHCP disabled both through Netplan, not through the router.
I'll remember to check the Netplann (?) journal/logs around that time, or are you referring to dmesg?
Since you're not really sure what the issue is, check all the logfiles around the time the problem starts. maybe you'll see a service stopping or starting.
Thank you I'll do that! It's hard to catch exactly when it happens. I think I need to get some monitoring and alert services up and running
Changedetection.io it can send you an email or message when your server fails to ping it.you will then have the times. Its a 5 minute job to set it up. Make an account and your email or number or whatever and make a curl request to the specific endpoint in a cronjob
Thanks I'll give that a shot! I was thinking about using a solution with my VPS, but I may go this route.
Easiest route you could go is setup a systemd timer which runs every 5 mins, pings an ip and write the result into a logfile. that way you have a timestamp for the problem start without going all out with monitoring.
Good luck!
You don't need to catch that moment live, it was already recorded.
Take a look at
journalctl -b -1(previous boot).Thank you for this sweet tip! I'll definitely be using this.