wedgekc 12 Posted March 14, 2018 Share Posted March 14, 2018 (edited) The Android app connected remotely (https) crashes the server after the first song is played with an ssl error. I cannot connect again until the docker container is restarted. Remote streaming (https) on my laptop works fine using firefox. I did try to delete all data on the android app and login again but the result was the same. Sorry forgot to attach the log. I should also note that streaming seemed to work normally once I connected using 4g instead of using the remote wifi connection, although the remote wifi worked using my laptop with the browser. EmbyLog.txt Edited March 14, 2018 by wedgekc Link to comment Share on other sites More sharing options...
Luke 37113 Posted March 14, 2018 Share Posted March 14, 2018 What ssl error? Link to comment Share on other sites More sharing options...
wedgekc 12 Posted March 14, 2018 Author Share Posted March 14, 2018 This is very strange. I have tested using the wifi at work and a coffee shop with the same results (logs in first post): 1. I could login to Emby, browse media and play videos (although I didn't watch an entire video) but when I played music, after the first song is finished Emby server would crash and the container needed to be restarted. I could vpn to my home server and restart Emby server and replicate the problem. Using firefox on my laptop did not cause this problem, only the Android app. 2. Restarting the container and using 4g everything worked well. The only common link that I can think of would be that all locations involved are using the same ISP, that would explain it working on 4g. I have never had this happen before until after the switch over to .net core Emby is running in a docker container (bridged network), ssl with Let's Encrypt and I port forward 8920 only to my server and have "require https for remote connections" selected. Thanks Link to comment Share on other sites More sharing options...
Luke 37113 Posted March 15, 2018 Share Posted March 15, 2018 It's strange because the log seems to suggest that the client tried to connect with sslv3 whereas tls is now required. Link to comment Share on other sites More sharing options...
wedgekc 12 Posted March 15, 2018 Author Share Posted March 15, 2018 Luke, it appears as though I have the same problem mentioned in the post: https://emby.media/community/index.php?/topic/54709-problem-getting-lets-encrypt-ssl-cert-to-work-on-embyserver-dotnetcore/ at least the setup and the errors appear to be the same. Has there been any progress in the January thread? I also suspect .net after googling and finding issues with .net, ssl and Ubuntu http://github.com/dotnet/corefx/issues/21761 ...although I'm just shooting in the dark. Thanks Link to comment Share on other sites More sharing options...
Luke 37113 Posted March 15, 2018 Share Posted March 15, 2018 It's possible but I'm not sure yet. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now