Jellyfin Will Not Start, Getting: Failed to create CoreCLR, HRESULT: 0x80004005

[Alcatraz077]

Describe the bug
Jellyfin will not start, logs just show Failed to create CoreCLR, HRESULT: 0x80004005 over and over again.

System (please complete the following information):

• OS: Unraid
• Virtualization: Docker
• Clients: N/A
• Browser: N/A
• Jellyfin Version: 10.5.1
• Playback: N/A
• Installed Plugins: None
• Reverse Proxy: Let's Encrypt/Nginx
• Base URL: none
• Networking: Docker - MacVLAN
• Storage: local

To Reproduce

1. Install Jellyfin 10.5 via linuxserver docker repo.
2. Check Logs
3. Logs show "Failed to create CoreCLR, HRESULT: 0x80004005"

Expected behavior
Jellyfin to start

Logs
Failed to create CoreCLR, HRESULT: 0x80004005

Screenshots

Additional context
I've completely removed the jellyfin image, wiped my jellyfin app data folder, disabled/enabled docker, no dice.

[Bond-009]

Looks like a dotnet or linuxserver issue

[Alcatraz077]

My apologies, I'll reach out to LinuxServer people and go from there.

…

On Mon, Mar 16, 2020, 4:04 PM Bond-009 ***@***.***> wrote: Looks like a dotnet or linuxserver issue — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFB2YXR5QCBQONFEDTVRXETRH2H5XANCNFSM4LMR2TIA> .

[Alcatraz077]

This seemed to be an issue with the container, not Jellyfin itself. Closing. Thanks for your insight Bond.

[gr33k]

I reverted to 10.8.8-1-ls191 and the error went away

[paulgear]

I encountered this error today and found that it was due to /tmp being missing entirely from the official Jellyfin Docker image. I'm not sure how this happened, but just building a new one with /tmp in place fixed the problem for me. I've written about it in more detail here: https://www.libertysys.com.au/2023/03/a-tale-of-two-tmp-bugs/

[shazahm1]

@Alcatraz077 I'm not sure, but this might need to be reopened based on @paulgear response. I had the same issue. I tried the instructions, but I had no luck ... not experienced enough to know for sure if I was following them correctly. I managed by sheer luck to get 10.8.8-1-ls191 installed, and it worked perfectly without the error in the initial bug report.