-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Secure connection failed for Waterfox user-agents #2073
Comments
Just found https://quakewiki.org has the same issue and of course https://www.quaddicted.com. |
What's in the server logs when the connection fails? |
All those sites work fine for me in Waterfox. I'd love to see what the logs are. (Edit: I'm not using Linux either.) |
For https://www.quaddicted.com/ : I installed Waterfox 56.0.4.1 (64-bit) and the addon UAControl.
Clicking the cert info thing in the address bar shows the normal cert dialog and all is fine there. I see absolutely nothing about that request in the server logs that are configured as
With If I set the user agent to "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.2" (same but without the Waterfox suffix), it works fine. If I set the user agent to "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0.2 " (trailing space), it breaks in the same way as before. |
Which version of Caddy are you using? And what does the process log say? (You'll have to use |
Oh ouch, it was still on 0.10.4. It seems to work fine with 0.10.11 now. |
There are reports about people using the Waterfox fork of Firefox not being able to access certain websites. They are getting "Secure connection failed" errors. They can change their user-agents to work around this. It seems not to happen for Linux users.
BrowserWorks/Waterfox#178 mentions
That's pretty much the only hint at what be going on, they are all served by Caddy.
I suspect the MITM detection to be the culprit as that is the only place where *fox mentioned in the code. Could someone take a look at this? Thanks! :)
The text was updated successfully, but these errors were encountered: