# Invalid 'X-Plex-Device' header value in Plex Media Server.log **URL:** \ **Category:** Plex Media Server\ **Tags:** server-linux-arm\ **Created:** [February 9, 2025, 3:36am UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015 "2025-02-09T03:36:53Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mikelfinch\_yahoo\_com](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@mikelfinch\_yahoo\_com](https://forums.plex.tv/u/mikelfinch_yahoo_com)\ **Post date:** [February 9, 2025, 3:36am UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015/1 "2025-02-09T03:36:53Z")
Server Version#: 1.41.3.9314 Player Version#: 4.145.0 PMS is being setup on an Armbian Odroid C2. ```auto cat /etc/os-release PRETTY_NAME="Armbian 24.11.3 bookworm" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 24.11.3 bookworm" ``` After building a new server for a friend, I noticed a lot of `invalid '-Plex-Device' header value` in the Plex Media Server.log file. I first thought it was because the server was configured incorrectly, specifically a device name mismatch. However maybe this is an issue with how aarch64 systems add a hex 00 (null) to the end of “device”? Here is what I am seeing in the Plex Media Server.log. First lets look at the output of Plex Media Server.log using xxd: ```auto 00000050: 342d 6130 6266 6238 3337 3020 2d20 4465 4-a0bfb8370 - De 00000060: 6269 616e 2047 4e55 2f4c 696e 7578 2048 bian GNU/Linux H 00000070: 6172 646b 6572 6e65 6c20 4f44 524f 4944 ardkernel ODROID 00000080: 2d43 3200 2061 6172 6368 3634 202d 2062 -C2. aarch64 - b. ``` forth character of the last line is hex 00. Next using VI there is a “^@” (hex 00) in a couple of lines. See the following: ```auto Feb 08, 2025 16:45:02.455 [281473128534240] INFO - Plex Media Server v1.41.3.9314-a0bfb8370 - Debian GNU/Linux Hardkernel ODROID-C2^@ aarch64 - build: linux-aarch64 debian - GMT -06:00 Feb 08, 2025 16:45:03.044 [281473124315360] ERROR - [MediaProviderManager] [HttpHeader] invalid '-Plex-Device' header value (Hardkernel ODROID-C2^@) Feb 08, 2025 16:45:04.452 [281473089233120] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader "--directory=/mnt/hdd/plex/Plex Media Server/Crash Reports/1.41.3.9314-a0bfb8370" --version=1.41.3.9314-a0bfb8370 --platform=Linux "--platformVersion=12 (bookworm)" --serverUuid=7213d1cee25d96ec20c4e99adae04b0eb0c7a49e --userId=kylef557@gmail.com --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "--vendor=Debian GNU/Linux" --model=aarch64 '--device=Hardkernel ODROID-C2^@' ``` I have attached Plex Media Server.log file for ODROID-C2 here: [Plex Media Server.log](https://forums.plex.tv/uploads/short-url/tvrdDveX46UXiNncDMkANhcBk1H.log) (133.5 KB) I am not sure how this all gets into PMS, but I feel like this issue might originate as follows. xxd /sys/firmware/devicetree/base/model ```auto 00000000: 4861 7264 6b65 726e 656c 204f 4452 4f49 Hardkernel ODROI 00000010: 442d 4332 00 D-C2. ``` Last character is hex 00. It feels like this extra “00” value is being read in by PMS and cause device setting issues. On an x86\_64 machine the otput is different as product\_name has hex 0a which is line feed, I guess. ```auto xxd /sys/devices/virtual/dmi/id/product_name 00000000: 4f44 524f 4944 2d48 340a ODROID-H4. ``` PMS on ODROID-H4 doesn’t seem to have any issue with ‘X-Plex-Device’. Repeating the steps above and using VI to output the first line of Plex Media Server.log, notice that it doesn’t contain a “^@” character ```auto Feb 08, 2025 17:05:08.781 [140195255012152] INFO - Plex Media Server v1.41.3.9314-a0bfb8370 - Debian GNU/Linux HARDKERNEL ODROID-H4 x86_64 - build: linux-x86_64 debian - GMT -06:00 ``` Here is the full log for ODROID-H4: [ODROID-H4 Plex Media Server.log](https://forums.plex.tv/uploads/short-url/aEviBJ5ZaDy0PBbeu4FPI8CDrXj.log) (120.5 KB) ---
**Author:** ![pshanew](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/pshanew/32/160555_2.png) [@pshanew](https://forums.plex.tv/u/pshanew)\ **Post date:** [February 9, 2025, 3:59am UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015/2 "2025-02-09T03:59:45Z")
What is the problem you’re trying to solve? Have you experienced any real issues? Streaming buffering, server crashing, anything like that? Or are you just trying to rationalize error/warning messages from the logging? ---
**Author:** ![mikelfinch\_yahoo\_com](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@mikelfinch\_yahoo\_com](https://forums.plex.tv/u/mikelfinch_yahoo_com)\ **Post date:** [February 10, 2025, 2:50pm UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015/3 "2025-02-10T14:50:23Z")
@pshanew, here are my thoughts to your prior post. 1.) What is the problem? My server is not experiencing any problems and I am just trying to rationalize error/warning messages from the logging. I am experiencing an ERROR that seems fixable. 2.) Should I be concerned with this error? It sounds like I should just ignore this error? 3.) Can device be overridden? Is there any way to fix / override the “device” value? Maybe something I could change in the override.conf file? /etc/systemd/system/plexmediaserver.service.d/override.conf ---
**Author:** ![jrExt\_outlook\_com](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jrExt\_outlook\_com](https://forums.plex.tv/u/jrExt_outlook_com)\ **Post date:** [February 17, 2025, 2:43am UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015/4 "2025-02-17T02:43:05Z")
I get the same problem with a new Raspberry Pi install /etc/os-release ```auto PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ``` And the PMS version info ```auto SpeedyPi 1.41.4.9463-630c9f557 Plex Media Server Linux 12 (bookworm) ``` The errors in the log contain ` [HttpHeader] invalid 'X-Plex-Device' header value (Raspberry Pi 4 Model B Rev 1.5)` The server fails to scan a newly added library throwing these errors. ---
**Author:** ![jrExt\_outlook\_com](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jrExt\_outlook\_com](https://forums.plex.tv/u/jrExt_outlook_com)\ **Post date:** [February 17, 2025, 6:16pm UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015/5 "2025-02-17T18:16:08Z")
Does anyone know how `X-PLEX-DEVICE` is set? I tried setting `Device="Rpi4"` in`Preferences.xml` but that didn’t work. ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [May 18, 2025, 6:16pm UTC](https://forums.plex.tv/t/invalid-x-plex-device-header-value-in-plex-media-server-log/905015/6 "2025-05-18T18:16:14Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.