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.
All my homies use :3000
:3
Doesn’t matter; we’ll map it to whatever the environment needs in the docker-compose.yaml.
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.
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.
9090
8888
Imagine using 8081 while 8080 is free. Truly criminal
I like 6969
4200 or 10420 too
Nice
