Jump to content

Search the Community

Showing results for tags 'ububtu'.

  • 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 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

Blogs

  • Emby Blog

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 3 results

  1. Funkie

    HTTPS 8920 internal not running

    Hi @Luke I am running emby server 4.7.5.0 on Ubuntu 20.04.4 LTS. Not sure when this stopped working as I mainly access my server locally via http but setup HTTPS on port 8920 behind HAProxy and was working fine. I saw an error no backend to emby in HAProxy so investigated and indeed I cannot access the server at all on https. If I curl from the emby server I get this error curl: (7) Failed to connect to localhost port 8920: Connection refused
  2. Hi - I'm experiencing an unusual problem associated with reading Metadata updates. I'm running Emby Server with a PPTP/VPN server and NGINX reverse proxy server. In general Emby works as expected (remote connections to the server and streaming are all possible) but for some reason, when connected to the VPN Metadata updates (and I think EPG updates) cannot be read. I've tested this and the problem is repeatable. When the server is connected to the internet via the VPN connection Metadata updates and searches cannot be read, when connected to the local ISP internet provision then Metadata updates can be read. I've attached the error log which may give some indication as to the source of the problem. I'm confident it isn't a Firewall problem and I've checked routing for both Ports 8096 and 8920. I'm fairly confident the problem is something to do with the interaction between the NGINX server and the VPN connection. I'd welcome any suggestions from folk as to how I might fix this problem . Thank you. embyserver(3).txt
  3. ifti12

    Crashing issue in Ubuntu Linux

    Hello, I've posted earlier here about a crash issue on emby 4.3 Our server has a 24 core processor and 40 GB of ram. So its a moderate server. We've let some of our local internet user use it as a streaming server but its at max 15-20 users at a time. We were running on emby 4.11 for past few months as 4.2 and 4.3 always crashed. So after the recent update which is 4.4 we thought we might give it a try. Result was same, it crashed but the sad part was we were unable to downgrade back to 4.11 life before. So we thought there might be a file issue. So we gave it a clean install. Removed everything and then installed 4.4. Luckily it survived. We set max trasncoding thread to 15 and stopped hardware acceleration. So it ran smoothly for one day. Today it crashed again. On a note, emby still uses almost 90-95% of our cpu all the time doesnt matter if there's 1 transcode running or 20. Load average was almost 70-80 before we limited thread count. Now its 50-70. So what's the issue here? Can anyone help? heres the latest error report: We saw same type of issue, so we stopped real time monitoring but we dont know what else we can do now.
×
×
  • Create New...