-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
https requests from chrome cause radarr to crash with mono System.IO.IOException #6680
Comments
Could you provide more details how we can reproduce the issue |
If there's an easy way for me to just test the mono https server implementation, I can do that too. |
@baulig @brendanzagaeski @marek-safar |
It is very likely related to installing the custom certificates. |
But why would that cause it to fail on some browsers and not others? There must be something different in the ssl request or response... |
Oh, I may have been confused - are you using Mono no the server-side and then connect with these browsers? |
Correct. radarr uses the mono https server. I can connect to it with firefox, but connecting to it with chrome and internet explorer causes a fatal exception |
Very interesting. I'll have a look at this next week. |
FYI: This issue still exists as of 5.8.0.127. Tried checking 5.10, but it breaks radarr in a different way that has yet to be resolved, so I had to roll back. |
@kaysond could you include the description how it breaks with 5.10 |
@marek-safar It was an issue with a particular version of NLog, apparently. It's been fixed: Radarr/Radarr#2585 |
Haven't gotten around to checking the ssl issue on 5.10 yet |
Issue seems to be resolved with 5.10. Tested on chrome 64 on android and ie on win10 |
I'm running radarr 0.2.0.910 on Ubuntu 17.10 with mono 5.4.1.7. Connecting to the https server using chrome or internet explorer causes a fatal error. No issue with firefox, though.
See: Radarr/Radarr#2443
The text was updated successfully, but these errors were encountered: