Adromir 0 Posted May 28, 2019 Share Posted May 28, 2019 So i am trying to use the Emby App to connect to my Unraidserver running Emby in a Docker Container. While it is possible to use the Server via Browser, I simply can't connect to it through the app. It's neither working while im Inside nor when i'm outside my local Network. No Problems accessing the Server Dashboard in Chrome on my phone Though. App is starting, but when I try to add my server it just simply says connection failed. Double checked everything for spelling mistakes, but everything is correct. Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 28, 2019 Share Posted May 28, 2019 Hi, are you trying to connect over http or https? Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 28, 2019 Author Share Posted May 28, 2019 Over http Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 28, 2019 Share Posted May 28, 2019 What version of Chrome is installed? Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 28, 2019 Author Share Posted May 28, 2019 Its the latest stable 74 from the play store. it also has troubles opening the Emby Forum, after warning about a invalid https certificate it only shows a blank page (if i proceed to webpage nevertheless) Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 28, 2019 Share Posted May 28, 2019 Well I don't see that https warning on Android. It is probably related to the certificate store that Lineage is shipping with. Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 28, 2019 Share Posted May 28, 2019 Can you try this version of the app? https://www.dropbox.com/s/9am2hgfcj403j8d/MediaBrowser.Mobile-googlearmv7-release.apk?dl=0 Â It will produce a log file. Perhaps we'll spot something in there. Thanks. Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 28, 2019 Author Share Posted May 28, 2019 I think i found the problem about this. On my Phone i am Using a different DNS than I am Using in my local Network. Here on my Desktop emby.media is signed by Comodo, while in Chrome it is signed by the Provider of the DNS. Changing the DNS back to Standard made the forum work in Chrome but sadly dient fix the connection Problem to my server Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 28, 2019 Author Share Posted May 28, 2019 Installed this app version, still can't connect. Where do I find the logs of it? Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 28, 2019 Share Posted May 28, 2019 https://emby.media/community/index.php?/topic/15638-how-to-report-an-android-problem/ Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 29, 2019 Author Share Posted May 29, 2019 This is the log it created. What is a bit weird is that the app apparently tries to route something through 192.169.2.255 which isnt existant in my home network Tue May 28 20:15:15 GMT+02:00 2019 External dir: /storage/emulated/0/Android/data/com.mb.android/files isExternalStorageEmulated: true isExternalStorageRemovable: false Tue May 28 20:15:15 GMT+02:00 2019 Environment.getExternalStorageDirectory: /storage/emulated/0 Tue May 28 20:15:15 GMT+02:00 2019 MediaBrowser.connect Tue May 28 20:15:15 GMT+02:00 2019 Refreshing route list Tue May 28 20:15:15 GMT+02:00 2019 MainActivity.onResume Tue May 28 20:15:15 GMT+02:00 2019 Scheduled job 'EmbySync' with id = '11' Tue May 28 20:15:15 GMT+02:00 2019 MediaService.onCreate Tue May 28 20:15:15 GMT+02:00 2019 MediaService starting a new MediaSession Tue May 28 20:15:15 GMT+02:00 2019 MediaService setting up CarHelper and WearHelper Tue May 28 20:15:15 GMT+02:00 2019 MediaService calling updatePlaybackState Tue May 28 20:15:15 GMT+02:00 2019 MediaService creating MediaNotificationManager Tue May 28 20:15:15 GMT+02:00 2019 MediaService getting MediaRouter Tue May 28 20:15:15 GMT+02:00 2019 MediaService.registerCarConnectionReceiver Tue May 28 20:15:15 GMT+02:00 2019 MediaService.onGetRoot Tue May 28 20:15:15 GMT+02:00 2019 MediaBrowserCompat.onConnected Tue May 28 20:15:15 GMT+02:00 2019 MediaSessionCompat.connectToSession Tue May 28 20:15:15 GMT+02:00 2019 onMediaControllerConnected Tue May 28 20:15:15 GMT+02:00 2019 Refreshing route list Tue May 28 20:15:15 GMT+02:00 2019 initStore called Tue May 28 20:15:15 GMT+02:00 2019 IAB helper created. Tue May 28 20:15:15 GMT+02:00 2019 Starting in-app billing setup. Tue May 28 20:15:15 GMT+02:00 2019 Billing service connected. Tue May 28 20:15:15 GMT+02:00 2019 Checking for in-app billing 3 support. Tue May 28 20:15:15 GMT+02:00 2019 In-app billing version 3 supported for com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Subscriptions AVAILABLE. Tue May 28 20:15:15 GMT+02:00 2019 Starting async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: inapp Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: subs Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 Ending async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 Sending url to webView: IapManager.onStoreReady(); Tue May 28 20:15:15 GMT+02:00 2019 getPurchaseInfos Tue May 28 20:15:15 GMT+02:00 2019 Checking purchase status of com.mb.android.playback Tue May 28 20:15:15 GMT+02:00 2019 Starting async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: inapp Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Error sending DatagramPacket: sendto failed: EPERM (Operation not permitted) java.io.IOException libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:576) libcore.io.IoBridge.sendto(IoBridge.java:544) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:44) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) caused by android.system.ErrnoException libcore.io.Linux.sendtoBytes(Native Method) libcore.io.Linux.sendto(Linux.java:227) libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:307) libcore.io.IoBridge.sendto(IoBridge.java:542) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:44) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) Tue May 28 20:15:15 GMT+02:00 2019 Error sending DatagramPacket: sendto failed: EPERM (Operation not permitted) java.io.IOException libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:576) libcore.io.IoBridge.sendto(IoBridge.java:544) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:68) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) caused by android.system.ErrnoException libcore.io.Linux.sendtoBytes(Native Method) libcore.io.Linux.sendto(Linux.java:227) libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:307) libcore.io.IoBridge.sendto(IoBridge.java:542) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:68) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) Tue May 28 20:15:15 GMT+02:00 2019 com.mb.android.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 192.168.2.255; Interface: wlan0 Tue May 28 20:15:15 GMT+02:00 2019 com.mb.android.apiinteraction.discovery.ServerLocator>>> Done looping over all network interfaces. Now waiting for a reply! Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 queryPrices: nothing to do because there are no SKUs. Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: subs Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 queryPrices: nothing to do because there are no SKUs. Tue May 28 20:15:15 GMT+02:00 2019 Ending async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 *** IsPurchased Result: com.mb.android.playback Failure Tue May 28 20:15:15 GMT+02:00 2019 Sending url to webView: window.IapManager.updateProduct("com.mb.android.playback", false, "4,99 €") Tue May 28 20:15:15 GMT+02:00 2019 Checking purchase status of com.mb.android.unlock Tue May 28 20:15:15 GMT+02:00 2019 Starting async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: inapp Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 queryPrices: nothing to do because there are no SKUs. Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: subs Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 queryPrices: nothing to do because there are no SKUs. Tue May 28 20:15:15 GMT+02:00 2019 Ending async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 *** IsPurchased Result: com.mb.android.unlock Failure Tue May 28 20:15:15 GMT+02:00 2019 Checking purchase status of emby.supporter.monthly Tue May 28 20:15:15 GMT+02:00 2019 Starting async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: inapp Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 queryPrices: nothing to do because there are no SKUs. Tue May 28 20:15:15 GMT+02:00 2019 Querying owned items, item type: subs Tue May 28 20:15:15 GMT+02:00 2019 Package name: com.mb.android Tue May 28 20:15:15 GMT+02:00 2019 Querying SKU details. Tue May 28 20:15:15 GMT+02:00 2019 queryPrices: nothing to do because there are no SKUs. Tue May 28 20:15:15 GMT+02:00 2019 Ending async operation: refresh inventory Tue May 28 20:15:15 GMT+02:00 2019 *** IsPurchased Result: emby.supporter.monthly Failure Tue May 28 20:15:15 GMT+02:00 2019 Sending url to webView: window.IapManager.updateProduct("emby.supporter.monthly", false, "6,94 €") Tue May 28 20:15:16 GMT+02:00 2019 Server discovery timed out waiting for response. Tue May 28 20:15:16 GMT+02:00 2019 Found 0 servers Tue May 28 20:15:16 GMT+02:00 2019 file:///android_asset/www/scripts/librarymenu.js?v=28: Line 1 : Uncaught TypeError: appRouter.setDefaultTitle is not a function Tue May 28 20:15:16 GMT+02:00 2019 Setting theme color to #313235 Tue May 28 20:15:16 GMT+02:00 2019 Setting theme color to #313235 Tue May 28 20:15:17 GMT+02:00 2019 file:///android_asset/www/scripts/librarymenu.js?v=28: Line 1 : Uncaught TypeError: appRouter.setDefaultTitle is not a function Tue May 28 20:15:18 GMT+02:00 2019 file:///android_asset/www/scripts/librarymenu.js?v=28: Line 1 : Uncaught TypeError: appRouter.setDefaultTitle is not a function Tue May 28 20:15:18 GMT+02:00 2019 Error sending DatagramPacket: sendto failed: EPERM (Operation not permitted) java.io.IOException libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:576) libcore.io.IoBridge.sendto(IoBridge.java:544) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:44) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) caused by android.system.ErrnoException libcore.io.Linux.sendtoBytes(Native Method) libcore.io.Linux.sendto(Linux.java:227) libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:307) libcore.io.IoBridge.sendto(IoBridge.java:542) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:44) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) Tue May 28 20:15:18 GMT+02:00 2019 Error sending DatagramPacket: sendto failed: EPERM (Operation not permitted) java.io.IOException libcore.io.IoBridge.maybeThrowAfterSendto(IoBridge.java:576) libcore.io.IoBridge.sendto(IoBridge.java:544) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:68) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) caused by android.system.ErrnoException libcore.io.Linux.sendtoBytes(Native Method) libcore.io.Linux.sendto(Linux.java:227) libcore.io.BlockGuardOs.sendto(BlockGuardOs.java:307) libcore.io.IoBridge.sendto(IoBridge.java:542) java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:125) java.net.DatagramSocket.send(DatagramSocket.java:721) com.mb.android.apiinteraction.discovery.ServerLocator.FindServers(ServerLocator.java:68) com.mb.android.MainActivity$10.run(MainActivity.java:1398) java.lang.Thread.run(Thread.java:764) Tue May 28 20:15:18 GMT+02:00 2019 com.mb.android.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 192.168.2.255; Interface: wlan0 Tue May 28 20:15:18 GMT+02:00 2019 com.mb.android.apiinteraction.discovery.ServerLocator>>> Done looping over all network interfaces. Now waiting for a reply! Tue May 28 20:15:19 GMT+02:00 2019 Server discovery timed out waiting for response. Tue May 28 20:15:19 GMT+02:00 2019 Found 0 servers Tue May 28 20:15:20 GMT+02:00 2019 file:///android_asset/www/scripts/librarymenu.js?v=28: Line 1 : Uncaught TypeError: appRouter.setDefaultTitle is not a function Tue May 28 20:15:47 GMT+02:00 2019 file:///android_asset/www/scripts/librarymenu.js?v=28: Line 1 : Uncaught TypeError: appRouter.setDefaultTitle is not a function Tue May 28 20:15:49 GMT+02:00 2019 MainActivity.onPause Tue May 28 20:15:49 GMT+02:00 2019 MediaService.onDestroy Tue May 28 20:15:49 GMT+02:00 2019 MediaService.handleStopRequest Tue May 28 20:15:49 GMT+02:00 2019 LocalPlaybackMpv.giveUpAudioFocus Tue May 28 20:15:49 GMT+02:00 2019 unregisterAudioNoisyReceiver Tue May 28 20:15:49 GMT+02:00 2019 destroying MPV Tue May 28 20:15:49 GMT+02:00 2019 MediaService.onPlaybackStop Tue May 28 20:15:49 GMT+02:00 2019 MediaService.onDestroy complete Wed May 29 06:40:03 GMT+02:00 2019 Billing service disconnected. Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 29, 2019 Share Posted May 29, 2019 Where are you seeing that? Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 29, 2019 Author Share Posted May 29, 2019 I was assuming that from this line: Â Â Tue May 28 20:15:18 GMT+02:00 2019 com.mb.android.apiinteraction.discovery.ServerLocator>>> Request packet sent to: 192.168.2.255; Interface: wlan0 Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 29, 2019 Share Posted May 29, 2019 No that's just the discovery function, not actually connection to a single server. Â Does your server dashboard display the correct local and remote addresses? Link to comment Share on other sites More sharing options...
Adromir 0 Posted May 29, 2019 Author Share Posted May 29, 2019 Yes it does LAN/WAN access Informations are both correct. I know I already had it working a while ago and I didn't change anything on the server since Link to comment Share on other sites More sharing options...
Luke 37007 Posted May 30, 2019 Share Posted May 30, 2019 Did you try entering the address manually into the app? Link to comment Share on other sites More sharing options...
Adromir 0 Posted June 1, 2019 Author Share Posted June 1, 2019 Manually and via copy and paste. Tried it on my home network also using the ip. Nothing works Link to comment Share on other sites More sharing options...
Luke 37007 Posted June 2, 2019 Share Posted June 2, 2019 What address did you enter? Link to comment Share on other sites More sharing options...
Adromir 0 Posted June 2, 2019 Author Share Posted June 2, 2019 A web address for my server that is received through a dyndns service,which is also entered into the emby server for WAN-Access. As I said, opening the server via webinterface through the adresse/ip in Chrome works, but not by using the app Link to comment Share on other sites More sharing options...
Luke 37007 Posted June 9, 2019 Share Posted June 9, 2019 Ok thanks for the info. I'll try to see if I can chase down why this might be happening. Thanks. Link to comment Share on other sites More sharing options...
Luke 37007 Posted June 22, 2019 Share Posted June 22, 2019 Can you try 3.0.51+ and see how that compares: https://emby.media/community/index.php?/topic/74729-emby-for-android-mobile-3051/ Thanks. 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