You must log in or register to comment.
go2rtc, a camera streaming tool that’s useful for security cameras, at least has some humor in their choice — port 1984, of course.
Okay, that’s pretty good.
Unix sockets all the way. The only open ports for web traffic should be the reverse proxy (so nginx).
Or Caddy (simpler than and imho spiritual successor to nginx).
Or Traefik (has loads of convenient middlewares for reverse proxy stuff).
Or Apache (if it is somehow better suited to your use case).
Is haproxy okay?
haproxy is awesome
Haproxy is great, but setup is hard. It’s more for load balancing than being an easy reverse proxy.
I use docker ports but only allow the loopback like this:
127.0.0.1:11551:80And then serve that app with the reverse proxy.
Doesn’t matter; we’ll map it to whatever the environment needs in the docker-compose.yaml.
All my homies use :3000
:3
adds a one to it
next app…
ports: - 8081:8081Ughhhhh
Psh, we choose 443 and you know it! Just don’t ask me if we correctly enabled HTTPS…
Back in the day I home hosted shit using http over 443 because my ISP blocked 80 inbound but not 443. It was a little weird but it worked lmao.
I run ssh over 443 because every network out there seems to block non-http ports.
I mean, if you’re serving over http, that is the port for it
Isn’t it port 80?
It’s both
We apparently could have been using 8008 this entire time for the same thing and we haven’t and I’m a little sour now.
Me & the boys serving http on the boob port
I’d suckle that server
I prefer the secure version, boobs.
Imagine using 8081 while 8080 is free. Truly criminal
You also see a fair bit of 8001 iirc
9090
8888
I like 6969
4200 or 10420 too
Nice
That’s because 8080 is the official unprivileged alternative port for 80, the HTTP port. Web developers are usually using HTTP, so this makes perfect sense. If it supports HTTPS, then 8443, though that one isn’t official.
I run a few open source server projects, and they usually default to 8080 for this reason. I have one that uses 8888, and that’s only because it’s meant for temporary ad-hoc servers.
I’m working on an SFTP server, and it will use 2222, because that’s the most common unprivileged alternative port. There is no official alternative for SSH.
Me: 5000 it is.
Arg, my Synology servers are down. Thanks.
Hehe.
Everyone out here acting like they don’t use 9001
50501?
