Jump to content

Search the Community

Showing results for tags 'local network'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support


  • Emby Blog


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 3 results

  1. I cant access Emby anymore on my local ip. This happend after a update. I used to access Emby locally with http://embyserver:port or http<embyserverip>:port. Both don't work anymore. I can't edit these settings because I don't have a SSL certrificate and I still like to use a SSL connection with external clients. To make things more complicated, my server has multiple internal ip's. Since last (forced*) update Emby bind to the wrong internal ip. Is this a bug or a feature? Can I get 'the old' situation back? (with out a manual downgrade) Happy to read any comment! *forced because after an update the 'update automatically' option switches back on!? I try to be at least 2 beta builds behind but sometimes I forget this bug? and voila, I'm on the latest build.
  2. I'd like to redefine the meaning of local network to include one remote location/ip address so that the Roku at my cabin won't need to login with a password, but from other external locations a user/password would be necessary. How is the local network defined? Can I add the static ip of my cabin router somewhere in a config file? I understand how to set up a password for users not on the local network, and I'd like to apply that security, but I (and other users) really don't want to have to enter in a password every time I start up the Roku at the cabin/the channel updates... I suppose there are a couple of other options. but redefining local network to also include the remote ip is the best solution I can think of. I have set up a VPN from router to router, but then the big drawback all my non Media Browser traffic takes a performance hit going through the VPN. I suppose an equally satisfactory alternative would be to authenticate by device so the cabin Roku would not need to use a password. My network topology is roughly the following: Home router/local network --Living room: WMC main HTPC --Bedroom 1: Xbox running WMC/MB3 --Bedroom 2: Roku running MB3 channel Cabin router/static ip --Living room: Roku running MB3 channel I don't mind typing a password in on computers/tablets with good keyboards, but the Roku leaves much to be desired in that respect.
  3. We've been using MB Classic for years now (probably since your first launch) - it's great and I can't thank you enough!! But... our little girl is growing up - and now frequently using the computer. So I'd like to protect her from accessing age-inappropriate films/tv. User control is "ok" and very beneficial for access from remote computers - I often stream on my Windows Phone on the train, or to my laptop when away. On a local network you know who will be using the machines and so can now allow local access without a password (great addition, with caveats...). However, what many parents (I'm sure?) will want/use users for is to prevent their kids (of whatever age) accessing age-inappropriate material, therefore disabling passwords is not very helpful as they could simply select a different user. Would it be possible to add a basic, optional, "PIN entry" feature for content that is above an age-rating that you specify in the configuration? There could be a toggle for this in the top "options" (?) menu (that is shown in the top-right corner of all front-end pages)... e.g. by default a specified PIN must be entered to view any content rated above the set age rating. You can enter the PIN and enable all media until you then toggle the "parental access" back off again. Ideally, a time-out could be attached to this - so, once the kids have gone to bed, you enter the PIN once and have access to all content for the rest of the evening - but, after say 3 hours/overnight, the PIN times out and content is limited again. This would just be a much simpler (and much faster) option than logging out and in as a different user. It also means that you can simply leave your HTPC on and everything works - with no fear that your children can access 24, True Blood or a violent film for example.
  • Create New...