Networking is always fun to debug.. haha. I tried to replicate your issue but was unable to. Are you using docker, kubernetes or something else? Would be helpful if you could post your docker-compose.yml, kubernetes object manifests or other relevant config.
this post was submitted on 01 Dec 2024
25 points (90.3% liked)
Selfhosted
40492 readers
727 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 2 years ago
MODERATORS
Found the issue '^-^
UFW also blocks traffic between docker and host.
I had to add these rules
ufw allow proto tcp from 172.16.0.0/12 to 172.16.0.0/12 port 80
ufw allow proto tcp from 172.16.0.0/12 to 172.16.0.0/12 port 443
If you are using openvpn this env may be a good thing to try. It may need adjusted though.
OPENVPN_MSSFIX='1350'
Same problem.
I tried a few values and the same, ping works but curl doesn't.