-
-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firefox bans "unsafe" ports by default #1061
Comments
Ok, I thought Firefox would filter all ports >= some arbitrary value, but it's actually a discrete list, with 10080 happening to be some antique backup software. I suppose the simplest fix would be to just use a different default port :-D |
Can u sénd a pull réquest sir ¿ |
This is great, thank you |
This should help with brndnmtthws#1061. Also added a warning about the default port being blocked by browsers.
This should help with brndnmtthws#1061. Also added a warning about the default port being blocked by browsers.
This should help with #1061. Also added a warning about the default port being blocked by browsers.
This issue is resolved as the config option was added, as well as a warning about the port being blocked. |
Firefox started to restrict which ports it can connect to. A Firefox user trying to connect to the Conky by HTTP on the default port would get this message:
With the only option to "Try Again" which wouldn't work.
The workaround is to create a
network.security.ports.banned.override
key inabout:config
to list the ports to allow.We should at least mention this in the documentation.
The text was updated successfully, but these errors were encountered: