EliteCube 6 Posted July 17, 2018 Share Posted July 17, 2018 (edited) Today i update to Emby-Server 3.5.0.0 Ubuntu x64 and i cant connect to the Web Interface after this Update Bad Request (Invalid url: http://[fda1:8096/web/index.html) Now i need to connect with IPv4What is wrong?and this is not the URL in BRowser the real URL is "fda1::XX" Edited July 17, 2018 by Seimann Link to comment Share on other sites More sharing options...
Luke 37248 Posted July 17, 2018 Share Posted July 17, 2018 Please attach the emby server log. You can learn how to do that here: https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/ Thanks. Link to comment Share on other sites More sharing options...
Happy2Play 8356 Posted July 17, 2018 Share Posted July 17, 2018 Does adding the /index.html#!/ work? ipv6:8096/web/index.html#!/index.html Link to comment Share on other sites More sharing options...
EliteCube 6 Posted July 17, 2018 Author Share Posted July 17, 2018 (edited) Nothing work with IPv6 URL now an this UpdateAnd i see also a problem on my Dashboard: ^ Wrong Icon for Kodi Plugin deviceWithout /web/index ... also: Bad Request (Invalid url: http://[fda1:8096/) Log1 is Emby 3.4.1.0 (before update, you can see i use IPv6 normal)Log2-5 is after the normal Update to 3.5 Log1-before.txt Log2.txt Log3.txt Log4.txt Log5.txt Edited July 17, 2018 by Seimann Link to comment Share on other sites More sharing options...
Luke 37248 Posted July 18, 2018 Share Posted July 18, 2018 Are you sure your ipv6 url is valid? you need a closing brace at the end ] So instead of: http://[fda1:8096 it should be http://[fda1]:8096 Link to comment Share on other sites More sharing options...
EliteCube 6 Posted July 18, 2018 Author Share Posted July 18, 2018 (edited) Are you sure your ipv6 url is valid? you need a closing brace at the end ] So instead of: http://[fda1:8096 it should be http://[fda1]:8096 No this is a Bug on my Emby-Server. I give you a screenshot: You see in my logs i use IPv6 befor this update. This return text "bad request" is not from firefox Edited July 18, 2018 by Seimann Link to comment Share on other sites More sharing options...
Luke 37248 Posted July 18, 2018 Share Posted July 18, 2018 We'll do some additional ipv6 testing and then report back. Thanks. Link to comment Share on other sites More sharing options...
Solution Luke 37248 Posted July 19, 2018 Solution Share Posted July 19, 2018 Ok I've got this resolved, thanks. 1 Link to comment Share on other sites More sharing options...
EliteCube 6 Posted July 19, 2018 Author Share Posted July 19, 2018 Ok I've got this resolved, thanks. Thanks for your feedback Link to comment Share on other sites More sharing options...
Luke 37248 Posted July 20, 2018 Share Posted July 20, 2018 This is fixed in 3.6.0.1 beta. We might do a 3.5.1 bug fix release. I'm currently undecided if this fix will go in that release or not, just on account of possible risk. Thanks. 1 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