Search the Community
Showing results for tags 'localhost'.
Found 4 results
firstname.lastname@example.org posted a topic in General/WindowsTeam, Need Help. Windows 10. Dell 8910. Used Emby Theater last night fine watched my recorded shows etc... no issues. Went to open Emby Theater this morning and I get a "connection failure". So I go to the server machine and discover 2 things I have not had issue with before 1. Emby all the sudden can't connect to localhost and wont open the Emby dashboard (on the server machine) 2. There were 6 or 7 instance of Emby Server showing up in the system tray for some reason I have since tried everything in my limited repertoire to troubleshoot the problem Restarting Reinstalling Emby Checked firewall Ports open Flushed DNS Checked the hosts folder seems fine Can someone please help me out on this as I have not made any changes that should have caused this to happen
I used MB2 until a few days ago which worked flawlessly. Now I upgraded to MB3 and installed server and client on the same machine. Most of the time when I try to connect to the dashboard by http://localhost:8096/mediabrowser/dashboard/index.html I get an error message saying connection is not possible. I opened all ports for the media browser in my windows firewall and I even tried to connect to the dashboard with the firewall switched off. I used google chrome, firefox and internet explorer. Nothing helped.
Florux posted a topic in MacOSHi, There are differences in the Media Browser Server depending on it being addressed through app.mediabrowser.tv or locally on localhost:8096/web. OSX version: 10.9.5 Media Browser Server: 3.0.5518.7 (and previous version(s)) Web Browser: Google Chrome, Safari and Firefox. No difference. It is very easily reproduced as simply using the different addresses to access it gives the different behaviour. So far I have found three differences: The settings menu has icons when accessing locally, no icons via app.mediabrowser.tv The setting menu has sync option when accessed locally, not via cloud The setting menu->Plugins does not work for launching plugins when addressed from cloud, but works fine when addressed locally Here's a picture of items 1 & 2. Item 3 is addressed separately. Viewed from localhost: Viewed from app.mediaserver.tv: I have extracted logs but cannot find any difference anywhere that could be useful. And since it's so super easy to reproduce I have for now not added logs. Please advise if that is needed anyway, and if so what exactly I should do. -Florux
Please use this at your own discretion. I would suggest creating a copy of the mentioned file in this help document prior to making any changes. I accept no responsibility for any issues with your system after follow this guide. One very good point regarding UAC and users that choose to leave this on, that was brought up by @ was the following So Basically, if you cannot connect to mediabrowser dashboard through the icon in the system tray or you have to physically type your address and port into your browser to access the dashboard (such as http://192.168.1.79:8096/mediabrowser/dashboard/dashboard.html). You probably have the localhost address missing or invalid in your system32 directory. Here is how to fix it basically Navigate to the "hosts" file located here C:\Windows\System32\drivers\etc Open "hosts" file and select Notepad to view the contents (My hosts file is one below) locate the line that says localhost at the bottom of the document. Change the address from whatever it is to 127.0.0.1 (in my case from 0.0.0.0) Save the document (CTRL+S or File->Save) You should be good to go # Copyright (c) 1993-2009 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 126.96.36.199 rhino.acme.com # source server # 188.8.131.52 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost # 0.0.0.0 localhost