The port of the devil: the nanny state browser protects me!

So I’m trying out ‘zoekt‘, which is a search engine for code, sort of like opengrok etc. I crank it up zoekt-webserver -listen :6666. And then I open a browser to it and, ERR_UNSAFE_PORT?

So I google it, its a thing. Chrome indeed protects you from bad neighbourhoods.

Seems you can add –explicitly-allowed-ports=6666, or, uh, pick a different port.

Happy Canada Day all.