adammerkley

Suddenly getting "Conversion failed. A required codec could not be found or failed to install." when trying to play media. This warning appears in the plex console when playing fails: [Transcode] HTTP error requesting GET https://plex.tv/api/codecs/h264_decoder?build=linux-x86_64-standard&deviceId=cfb78a4e-ef5f-4d89-8c6c-ecb622afcfa9&oldestPreviousVersion=1%2E2%2E7%2E2987-1bef33a&version=fa235d6-3855 (6, Couldn't resolve host name) (Could not resolve host: plex.tv) I've tried deleting the codecs folder, and also chmod'ing it to 777 but still get the error. Edit: Changing VERSION from plexpass to public has resolved this behavior.

Upgraded just fine from 6.7.2. Now to look into replacing OpenVPN with WireGuard... Thanks for all your hard work.

Can someone walk me through how to get this running behind an NGINX reverse proxy? I'm using the linuxserver.io LetsEncrypt container.

I do use DDNS. OpenDNS DNS-o-matic blasting out my home IP to several sources, including CloudFlare. I have no reason to use DNS-o-matic above anything else other than I've been using it for a long time and it was a simple 2 click step for me to add CloudFlare to it, any other DDNS would have worked including the CloudFlare DDNS docker.

Port 80 is blocked by my ISP too, but Letsencrypt still works fine. Just use DNS verification instead of port 80 verification.

I'm so curious about trying this. I have done the first few steps and rclone is working great to my Google Drive. I just can't bring myself to fully rely on Drive in case something goes wrong!

Upgraded from 6.6.5 to 6.6.6 without issue.

Another thank you. The tape trick worked perfectly on my eBay 310. Now I don't have the Marvell warning from Fix Common Problems anymore

Well now I see that the update from limetech says that the update was taken down 5 hours ago. I updated about 1 hour ago. I wonder what my server downloaded? I'm thinking I'll reboot and it will still be on 6.6.3.

Damn, I ran the update but haven't yet rebooted. What should I do?

Upgraded from 6.6.2 without issue.

The fact that Amazon and Apple have come out with strong denials, and have even said that they are under no gag order, tells me that Bloomberg's report is wrong. Publicly traded companies can be compelled to not comment. They cannot be compelled to lie.

Ah, thank you. I will plug it into one of my open drive caddies. Edit: Plugged a single drive into one of my caddies and it worked right away. Thanks so much!

Trying to get some data off of my old Unraid server. The hardware no longer boots so I have pulled the drives and plugged them into an external USB enclosure. I've plugged the drives into my current Unraid server, but I'm unable to mount any of them so far in UD. The drives are formatted in ReiserFS. I get these messages in the log when trying to mount: Oct 14 11:12:35 Tower unassigned.devices: Adding disk '/dev/sda1'... Oct 14 11:12:35 Tower unassigned.devices: Mount drive command: /sbin/mount -t reiserfs -o auto,async,noatime,nodiratime '/dev/sda1' '/mnt/disks/old1' Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): found reiserfs format "3.6" with standard journal Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): using ordered data mode Oct 14 11:12:35 Tower kernel: reiserfs: using flush barriers Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Oct 14 11:12:35 Tower kernel: REISERFS (device sda1): checking transaction log (sda1) Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current] Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0 Oct 14 11:12:35 Tower kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 01 00 cf 00 00 08 00 Oct 14 11:12:35 Tower kernel: print_req_error: critical target error, dev sda, sector 65743 Oct 14 11:12:35 Tower kernel: print_req_error: critical target error, dev sda, sector 65743 Oct 14 11:12:35 Tower kernel: Buffer I/O error on dev sda1, logical block 8210, lost sync page write Oct 14 11:12:35 Tower kernel: REISERFS warning (device sda1): journal-837 _update_journal_header_block: IO error during journal replay Oct 14 11:12:35 Tower kernel: REISERFS warning (device sda1): reiserfs-2006 journal_init: Replay Failure, unable to mount Oct 14 11:12:35 Tower kernel: REISERFS warning (device sda1): sh-2022 reiserfs_fill_super: unable to initialize journal space Oct 14 11:12:35 Tower unassigned.devices: Mount of '/dev/sda1' failed. Error message: mount: /mnt/disks/old1: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. Oct 14 11:12:35 Tower unassigned.devices: Partition 'ST315003 41AS' could not be mounted...

Can't think of much benefit to doing that. I'm relying on CA Backup for this. But if you do backup using Github and you use DNS verification, you'll want to exclude the file with your DNS provider API key.