view the rest of the comments
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!
~~Routing to me has been solved, my router was incorrectly dropping pings on WAN because I messed up the firewall configs.~~ The trouble users still can't reach my website.
Any chance your firewall is dropping the packets for some reason?
Your ISP may block 80 / 443. Try moving your webserver to an alternate high port and ask the users to test with that.
But it's only very few people. If my ISP blocks these ports, why 99% of people have no issues?
At this point I'd install wireshark and see if I'm getting their TCP connections at all.
Given your other routing issues though, I would guess you have another config issue on your firewall.
Packet capture from the router for 4 pings from him to me. ~~2 of 8 packets expected were captured and~~ have bad checksums. Disregard, all 8 expected packets do show up