The Port 6000 Mystery(docs.eventsourcingdb.io)
docs.eventsourcingdb.io
The Port 6000 Mystery
https://docs.eventsourcingdb.io/blog/2025/10/30/the-port-6000-mystery/
8 comments
Hey ChatGPT, please summarize this ChatGPT generated blogpost to quickly reveal the one piece of actionable knowledge without burying it in layers of fake narrative, manufactured drama and internally-inconsistent pretence at self reflection. Thank you. Good bot.
And don't forget to use lots of – em dashes!
Genuinely asking: is it against HN ethos to leave a comment warning that this is LLM slop? If yes I can delete this comment. I just wish I had known before I clicked on the link.
This is one of those things that is much safer than it was before, and can probably be overturned. However nobody will actually do it out of fear, and these ports will be locked up for decades more.
These days, you really don’t need multiple ports, reverse proxies that disambiguate via subdomain or path are incredibly easy to configure.
You've never needed, there's nothing new these days, just as many poorly configured apps that assume they're on a root path.
Reverse proxies are terrible to configure, add processing overhead to every request, violate security boundaries (cookies, localstore, CSP and other security headers are now shared) and introduce new bugs (rewrite didn't know a header, HTML element, JS variable, CSS text should/shouldn't be adjusted).
Reverse proxies are terrible to configure, add processing overhead to every request, violate security boundaries (cookies, localstore, CSP and other security headers are now shared) and introduce new bugs (rewrite didn't know a header, HTML element, JS variable, CSS text should/shouldn't be adjusted).
Yeah but if you have odd security needs and you don't want to terminate TLS in the cloud, you might not want that setup
Sad but true.