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
TCP is the way that you send information, HTTP is what it means.
The difference, in your case, is the port. You ~~can't~~ CAN have TCP and UDP on the same port, but you can't have the same protocol on the same port.
edit: I didn't knew you could have different transfer protocols on the same port, ty!
Why not? They are 2 completely separated set of ports. You can have a service listening on port 88 TCP while having another listening on port 88 UDP and they never know about each other.
You can’t have UDP and TCP on the same port? I don’t think that makes sense, I have DNS listening on UDP and TCP both on port 53.
For what
DNS
You have DNS listening on UDP and TCP... for DNS?
Iol, lol.
What's there to laugh about? DNS protocol uses both ports: TCP for zone transfer and UDP for queries.
Yes I have a DNS service listening on both UDP and TCP to respond to DNS queries from clients using the standard DNS port; crazy me. 🤪