starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Emby Quicksync transcoding not working due to permissions issue #1305

New Issue
Closed
opened 2026-02-05 00:14:25 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-05 00:14:25 +03:00
Owner
Copy Link

Originally created by @andrewdavidson64 on GitHub (Jul 18, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

emby

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/emby.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📝 Provide a clear and concise description of the issue.

Emby install script doesn't give sufficient priveleges for hardware transcoding to work. If I do a 'chmod 666 /dev/dri/* ' in the LXC console, it works. It looks like the emby script gives 660 permission, which doesn't work.

🔄 Steps to reproduce the issue.

Install Emby LXC, sad trombone noise.

❌ Paste the full error output (if available).

.

🖼️ Additional context (optional).

No response

Originally created by @andrewdavidson64 on GitHub (Jul 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? emby ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/emby.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📝 Provide a clear and concise description of the issue. Emby install script doesn't give sufficient priveleges for hardware transcoding to work. If I do a 'chmod 666 /dev/dri/* ' in the LXC console, it works. It looks like the emby script gives 660 permission, which doesn't work. ### 🔄 Steps to reproduce the issue. Install Emby LXC, sad trombone noise. ### ❌ Paste the full error output (if available). . ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 00:14:25 +03:00
OVERLORD commented 2026-02-05 00:14:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 18, 2025):

Have you say y into Installer?

@MickLesk commented on GitHub (Jul 18, 2025): Have you say y into Installer?
OVERLORD commented 2026-02-05 00:14:36 +03:00
Author
Owner
Copy Link

@andrewdavidson64 commented on GitHub (Jul 18, 2025):

Have you say y into Installer?

I did, yes. Also, as stated, if I manually fix the permissions, it works.

@andrewdavidson64 commented on GitHub (Jul 18, 2025): > Have you say y into Installer? I did, yes. Also, as stated, if I manually fix the permissions, it works.
OVERLORD commented 2026-02-05 00:14:42 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 18, 2025):

how you see the incorrect permissions? We need more Feedback, Screenshots or something.

@MickLesk commented on GitHub (Jul 18, 2025): how you see the incorrect permissions? We need more Feedback, Screenshots or something.
OVERLORD commented 2026-02-05 00:14:48 +03:00
Author
Owner
Copy Link

@andrewdavidson64 commented on GitHub (Jul 18, 2025):

how you see the incorrect permissions? We need more Feedback, Screenshots or something.

If you look at the permissions being set in the script, you can see it's setting 660, linked below:

2600e84a14/install/emby-install.sh (L21)

This needs to be 666.

@andrewdavidson64 commented on GitHub (Jul 18, 2025): > how you see the incorrect permissions? We need more Feedback, Screenshots or something. If you look at the permissions being set in the script, you can see it's setting 660, linked below: https://github.com/community-scripts/ProxmoxVE/blob/2600e84a1493c79ae87a20cc3eee5295366f03c0/install/emby-install.sh#L21 This needs to be 666.
OVERLORD commented 2026-02-05 00:14:55 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jul 18, 2025):

and why? where you see the issue? I'm not going to blindly “fix” something in a script that has been running for over 1.5 years or longer without any issue? The script is almost untouched since tteck.

bafd32f777 (diff-415e976cb82c34319069d1b8bf84ebf844caf8b79f9fa6431abb4dadbbec6806)

@MickLesk commented on GitHub (Jul 18, 2025): and why? where you see the issue? I'm not going to blindly “fix” something in a script that has been running for over 1.5 years or longer without any issue? The script is almost untouched since tteck. https://github.com/community-scripts/ProxmoxVE/commit/bafd32f777b97526a592e0dffa8837faf9127ccf#diff-415e976cb82c34319069d1b8bf84ebf844caf8b79f9fa6431abb4dadbbec6806
OVERLORD commented 2026-02-05 00:14:58 +03:00
Author
Owner
Copy Link

@andrewdavidson64 commented on GitHub (Jul 18, 2025):

Well, hardware transcoding doesn't work as the script stands. Typing "chmod 666 /dev/dri/* " in to the LXC's console fixes the issue. I'm not sure what I'm saying that is so difficult to understand.

I'm also not the only person to have this issue - see this thread (incidentally this is where I found the solution):

https://emby.media/community/index.php?/topic/113382-hw-acceleration-in-lxc-on-proxmox/

Edit: I'm appreciative that you're looking at this so promptly. I know it's weird, I've used this script before in the past on the same machine, and it worked OK. It's just not working with this install of proxmox. I've tried reinstalling the LXC with both priv and non-priv, with no difference - no hardware transcoding working, and errors similar to the ones listed in the linked emby community thread.

@andrewdavidson64 commented on GitHub (Jul 18, 2025): Well, hardware transcoding doesn't work as the script stands. Typing "chmod 666 /dev/dri/* " in to the LXC's console fixes the issue. I'm not sure what I'm saying that is so difficult to understand. I'm also not the only person to have this issue - see this thread (incidentally this is where I found the solution): https://emby.media/community/index.php?/topic/113382-hw-acceleration-in-lxc-on-proxmox/ Edit: I'm appreciative that you're looking at this so promptly. I know it's weird, I've used this script before in the past on the same machine, and it worked OK. It's just not working with this install of proxmox. I've tried reinstalling the LXC with both priv and non-priv, with no difference - no hardware transcoding working, and errors similar to the ones listed in the linked emby community thread.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1305
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?