Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Emby
  3. Error : server error - (HTTP code 500) server error

Error : server error - (HTTP code 500) server error

Scheduled Pinned Locked Moved Solved Emby
transcodingembydri
5 Posts 3 Posters 829 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      P Offline
      p44
      translator
      wrote on last edited by girish
      #1

      Dear,

      from today I've this error:

      «Error : server error - (HTTP code 500) server error - linux runtime spec devices: error gathering device information while adding custom device "/dev/dri": no such file or directory»

      I also rebooted but nothing happened...

      1 Reply Last reply
      0
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @p44 Looks like this is related to the change that enabled hardware transcoding in Emby in 5.6. Can you give me the following info:

        • ls -l /dev/dri on the server
        • Ubuntu version. You can get this using cat /etc/lsb-release
        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          Debugging this a bit further, I managed to reproduce this on Ubuntu 16. It seems that /dev/dri is missing on Ubuntu 16 but it's present on Ubuntu 18. It is something related to the lower kernel version in Ubuntu 16. Some posts on the internet suggest adding i915.alpha_support=1 to GRUB_CMDLINE_LINUX_DEFAULT="" in /etc/default/grub and then running sudo update-grub. However, I cannot get it to work despite this. Admittedly, I have not looked much into it.

          I have made a fix in our code in the meantime.

          @p44 You can try this one liner change in /home/yellowtent/box/src/docker.js and then systemctl restart box. After that go to the Dashboard and Repair the app.

          P 1 Reply Last reply
          0
          • girishG girish

            Debugging this a bit further, I managed to reproduce this on Ubuntu 16. It seems that /dev/dri is missing on Ubuntu 16 but it's present on Ubuntu 18. It is something related to the lower kernel version in Ubuntu 16. Some posts on the internet suggest adding i915.alpha_support=1 to GRUB_CMDLINE_LINUX_DEFAULT="" in /etc/default/grub and then running sudo update-grub. However, I cannot get it to work despite this. Admittedly, I have not looked much into it.

            I have made a fix in our code in the meantime.

            @p44 You can try this one liner change in /home/yellowtent/box/src/docker.js and then systemctl restart box. After that go to the Dashboard and Repair the app.

            P Offline
            P Offline
            p44
            translator
            wrote on last edited by
            #4

            @girish said in Error : server error - (HTTP code 500) server error:

            You can try this one liner change in /home/yellowtent/box/src/docker.js and then systemctl restart box. After that go to the Dashboard and Repair the app.

            @girish Dear Girish, I applied this fix and now works again! Many thank's for patience!

            1 Reply Last reply
            0
            • L Offline
              L Offline
              LoudLemur
              wrote on last edited by LoudLemur
              #5

              I have that error too, 4 years later. It appears on the pixeldroid application on the device.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search