Jump to content

Search the Community

Showing results for tags 'connection refused'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • 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
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 2 results

  1. I'm running into an issue getting metadata and images for content being added to my library. The short-short is that it works fine when I first start emby but at some point, the indexer (such as Fanart.tv, TMDB, etc.) starts blocking ("connection refused") the requests. Most of the time, powering off the box for a couple minutes and then bringing it back up clears the problem for a time. Sometimes connections are still refused and the restart process has to be repeated. The frequency in which this happens ranges from hours to days and I'm struggling to catch a correlation between the incidents and library change volume. This seems like a threshold issue in that my configuration is generating too many requests, but I'm not seeing it. Libraries are configured for real time monitoring with advance pulls. Looking at scheduled tasks status' I see they are only firing when content is added. In reviewing my configuration it also raised a question or two. So, here I am, asking for advice from those who love and know emby on what I'm missing and how to correct this. For the questions, the 2 biggest are; 1) How does emby generate/maintain API keys for the various indexers? In looking at several generations of the server logs I see that the key is consistent for each indexer. Is the key unique to each emby installation or shared by all installations? The latter could be significant in my configuration as I route most all of my internet traffic, emby and otherwise, through a commercial VPN. My ISP knows enough about me and my family. They don't need to know more. 2) Is it possible to use my own api keys for the indexers? If so, how? NOTE: I'd really rather not have to go this route. SERVER INFO: NOTE: All external requests do go through a VPN Thanks in advance for any assistance you all can offer.
  2. I cannot get Emby to continue to run. Shortly after install Emby will run and stop. Connection refused on port 8096. When initially installed it started to scan but after about 10 minutes it stopped. I have attached the log file. Please advise. emby log.txt
×
×
  • Create New...