Search the Community

Hello. A very satisfied user of Emby. Thank you to those that put a lot of hard work into a beautifully crafted app. My issue started 3 days ago. No remote access. Troubleshooting: In-Home access is visible. Static route is still in place. Port forwarding confirmed. VPN is used when testing Remote access. I have reviewed and followed the MediaBrowser Connectivity article. Firewall is not blocking anything related to Media Server nor the serverapp.exe I have troubleshot with the previous install, and with a fresh install. No luck It would appear there is no route to host Anyone have any suggestions as to what the next step would be? Thank you in advance.

Hi, I'm having some problems to maintain sync between Kodi and Emby in my RPI3 (OSMC distribution) with Emby for Kodi plugin. I'm using Samba, so I could use "localhost" or "osmc" as a host, as both Emby and Kodi are running in the same machine, but for some reason it resets the host to an 192.168.1.x IP (not necessarily the current one) everytime I restart the server. That's happening with both "emby connect" and "manual" options. I've found something similar in these posts: https://emby.media/community/index.php?/topic/57270-emby-for-kodi-doesnt-find-my-server-after-kodi-restart/ https://emby.media/community/index.php?/topic/57243-kodi-keep-lan-address/ But I don't know where should I configure the host that Emby is sending to the plugin. In the dashboard is showing the internal IP address, but it has been always the same when using Raspbian or Retropie, and host settings were never lost. My environment: Hardware: Rapsberry PI 3, model B (UK Version) OS: OSMC 2018.08-2 Kodi: 17.6 Emby: 3.5.2.0 Emby for Kodi: 3.0.34 I don't know if I'm missing any configuration option in OSMC. I've read about option "cleanonupdate" that should be turned off in the advancedsettings.xml, but in fact this option doesn't exist in the (quite brief) advancedsettings.xml from OSMC. My last try was: Searching files with the IP address shown in the configuration. Found "data.txt" and "settings.xml" in /home/osmc/.kodi/userdata/addon_data/plugin.video.emby. Edited those files, replacing the IP by localhost, and save the changes. Set readonly permissions for these files (sudo chmod 0444) so they could be read, but couldn't be modified anymore. After restarting the server it's showing the host http://localhost:8096 in the configuration (what should really be) but a pop-up message appears with an emby error.

One of the great features of MBS is the ability to manage the server from a browser and therefor not have to work on the host directly (anyone have a mouse, keyboard and monitor handy?). One feature that would be useful would be the ability to shutdown/restart the host itself. I don't have the server powered on 247, so the ability to shutdown the host from the dashboard with be advantageous. Another helpful feature would be to have an integrated VNC client (or similar) so you could launch a remote desktop session straight from the dashboard. This would go far in being able to manage the host itself from the one location. BTW, the progress made the server and the various clients is greatly appreciated round these parts. Thanks, Andy