85
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Oct 2023
85 points (84.6% liked)
Selfhosted
40153 readers
372 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:
-
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!
founded 1 year ago
MODERATORS
The static address should be assigned from the dhcp server.
Assigning a static address on the nic is a recipe for issues.
Set up a static assignment in your dhcp server.
I’m not able to log into my router in order to edit any of my dhcp settings 😭 little caveat there.
Then that’s likely your issue.
Your router occasionally gives out the ip of your pihole to someone else, and everything shuts the bed.
Try picking x.x.x.254 as the pihole address or x.x.x.2
Often routers won’t use either the top end or low end of the available addresses.
The machines on your network that are dhcp, do they go below 100? Do they go above 200?
You’re going to be guessing a little here.
What is your “net mask”
Ya I’m pretty sure you’re correct here and this is my issue. Since I’m not able to log into my router and define my dhcp range, I’ve picked an IP near the end of the range (254).
All my other devices are assigned .23, .25, etc.
Fun learning experience haha
Your ip-mask will tell you what IPs are accessible on the network
Likely goes nowhere because it’s probably 255.255.255.0 but it’s possible to be something else.
Ya it’s the 255 one. Thanks to all the help on the thread I’ve managed to set my server IP outside of the DHCP range (I think) so in theory my issue should be fixed. I’ll know in 90 days when the IP addresses are renewed.
Np, pay it forward to the next person that needs your help.
Are you on the same subnet as your router or are you on the subnet that your custom dhcp server is handing out? If your router is 192.168.1.1 and your ip is on the 192.168.2.x range, they aren't going to be able to communicate.
Ya I’m on the same subnet
Are you using https?
Nah http://. Tried both but none worked. Probably going to need to factory reset my router to ensure there aren’t any unlisted networks that may be the admin one. I have a sneaking suspicion my current network setup is actually on a secondary network (which could be why I can’t log into it)
Isolate a pc with the router and download advanced ip scanner. It will list all active ips and there should only be 2
That sucks, it’s be good if you could disable DHCP overall and do it on the PiHole.