Cannot determine relative path for unrooted paths #7461

Closed
opened 2026-02-19 23:11:44 -05:00 by deekerman · 6 comments
Owner

Originally created by @jsebt on GitHub (May 16, 2023).

Is there an existing issue for this?

  • I have searched the existing open and closed issues

Current Behavior

Ever since the May 14 update, Radarr seems to fail to trigger the "Plex" notification agent to refresh my libraries.
It fails with the error: Cannot determine relative path for unrooted paths even though my setup doesn't require any mapping betweed Radarr and Plex (they both reside bare-metal on the same Windows machine).

I do have path mapping for my torrent client that is on a separate linux computer, but I don't think it has any relevance to this bug report

Expected Behavior

Radarr triggering a library update on my Plex and not needing any path maping.

Steps To Reproduce

  1. On a Windows 10 personal computer
  2. Have both Radarr and Plex be regular "bare-metal" installs on your machine. No containers, no VMs. Both softwares see the exact same windows paths (i.e, lettered drives, multiple of them, my libraries are on multiple drives). Do not have any path maping in the Plex "Connect" settings
  3. Trigger any action in Radarr that would trigger a Plex library update according to your chosen options in "Connect" (In my case I just triggered a rename)
  4. See error in logs saying "Cannot determine relative path for unrooted paths" Trace logs are not needed to see it, but I have still included a trace log here for troubleshooting purposes.

Environment

- OS: Windows 10 build 19045.2965
- Radarr: 4.5.1.7282
- Docker Install: N/A
- Using Reverse Proxy: No
- Browser: Chrome
- Database: Sqlite 3.36.0

What branch are you running?

Develop

Trace Logs?

https://privatebin.net/?3dc0ee16f1f4299e#GkHR7Be1NWsYysy8yMTNq7gdE8EQTmEUT7tGJh1MrKUS

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

  • I have followed the steps in the wiki link above and provided the required trace logs that are relevant and show this issue.
Originally created by @jsebt on GitHub (May 16, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior Ever since the May 14 update, Radarr seems to fail to trigger the "Plex" notification agent to refresh my libraries. It fails with the error: Cannot determine relative path for unrooted paths even though my setup doesn't require any mapping betweed Radarr and Plex (they both reside bare-metal on the same Windows machine). I do have path mapping for my torrent client that is on a separate linux computer, but I don't think it has any relevance to this bug report ### Expected Behavior Radarr triggering a library update on my Plex and not needing any path maping. ### Steps To Reproduce 1. On a Windows 10 personal computer 2. Have both Radarr and Plex be regular "bare-metal" installs on your machine. No containers, no VMs. Both softwares see the exact same windows paths (i.e, lettered drives, multiple of them, my libraries are on multiple drives). Do not have any path maping in the Plex "Connect" settings 3. Trigger any action in Radarr that would trigger a Plex library update according to your chosen options in "Connect" (In my case I just triggered a rename) 4. See error in logs saying "Cannot determine relative path for unrooted paths" Trace logs are not needed to see it, but I have still included a trace log here for troubleshooting purposes. ### Environment ```markdown - OS: Windows 10 build 19045.2965 - Radarr: 4.5.1.7282 - Docker Install: N/A - Using Reverse Proxy: No - Browser: Chrome - Database: Sqlite 3.36.0 ``` ### What branch are you running? Develop ### Trace Logs? https://privatebin.net/?3dc0ee16f1f4299e#GkHR7Be1NWsYysy8yMTNq7gdE8EQTmEUT7tGJh1MrKUS ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have followed the steps in the wiki link above and provided the required trace logs that are relevant and show this issue.
Author
Owner

@bakerboy448 commented on GitHub (May 16, 2023):

Gist with relevant section as logs have 24hr expirery
https://gist.github.com/bakerboy448/3598f11a75c510ecd47b12169eafd53d

@bakerboy448 commented on GitHub (May 16, 2023): Gist with relevant section as logs have 24hr expirery https://gist.github.com/bakerboy448/3598f11a75c510ecd47b12169eafd53d
Author
Owner

@mynameisbogdan commented on GitHub (May 16, 2023):

@bakerboy448 it's already confirmed.

github.com/Radarr/Radarr@24bd2ae59b/src/NzbDrone.Core/Notifications/Plex/Server/PlexServerService.cs (L106)

Regression in 85aac789f4

@mynameisbogdan commented on GitHub (May 16, 2023): @bakerboy448 it's already confirmed. https://github.com/Radarr/Radarr/blob/24bd2ae59b3b3022af3646310c118a7e95ac98f7/src/NzbDrone.Core/Notifications/Plex/Server/PlexServerService.cs#L106 Regression in 85aac789f4daafffc5979f92a6e9d66b28d10fcb
Author
Owner

@zakkarry commented on GitHub (May 16, 2023):

Can confirm, experienced this on unRAID 6.11.5 with docker, 4.5.1.7282-ls97 - after adding MapTo and MapFrom (which was not previously necessary) - Plex Connect worked as expected.

@zakkarry commented on GitHub (May 16, 2023): Can confirm, experienced this on unRAID 6.11.5 with docker, 4.5.1.7282-ls97 - after adding MapTo and MapFrom (which was not previously necessary) - Plex Connect worked as expected.
Author
Owner

@whtdrgn commented on GitHub (May 16, 2023):

Side note. Those of us running in a windows environment with multiple NAS's we would have multiple paths that could go in the MapTo and MapFrom field. Which one do we use? Currently the path in Radarr and Plex match, just might reside on one of 4 different NAS's.

@whtdrgn commented on GitHub (May 16, 2023): Side note. Those of us running in a windows environment with multiple NAS's we would have multiple paths that could go in the MapTo and MapFrom field. Which one do we use? Currently the path in Radarr and Plex match, just might reside on one of 4 different NAS's.
Author
Owner

@jsebt commented on GitHub (May 16, 2023):

Side note. Those of us running in a windows environment with multiple NAS's we would have multiple paths that could go in the MapTo and MapFrom field. Which one do we use? Currently the path in Radarr and Plex match, just might reside on one of 4 different NAS's.

This is also relevant to a simple windows setup where libraries are on multiple different-lettered drives (like mine has G:/ and Q:/)

@jsebt commented on GitHub (May 16, 2023): > Side note. Those of us running in a windows environment with multiple NAS's we would have multiple paths that could go in the MapTo and MapFrom field. Which one do we use? Currently the path in Radarr and Plex match, just might reside on one of 4 different NAS's. This is also relevant to a simple windows setup where libraries are on multiple different-lettered drives (like mine has G:/ and Q:/)
Author
Owner

@costaht commented on GitHub (May 16, 2023):

Same problem here. These are my logs https://paste.centos.org/view/2b17ebde
I'm running:

Radarr Version: 4.5.2.7296
Package Version: nightly-4a5f300 by [hotio](https://github.com/hotio)

PMS Version 1.32.2.7002
OS: CentOS Stream release 9

Plex is running on my host, not container and testing the connection between Radarr and Plex returns success.

@costaht commented on GitHub (May 16, 2023): Same problem here. These are my logs https://paste.centos.org/view/2b17ebde I'm running: ``` Radarr Version: 4.5.2.7296 Package Version: nightly-4a5f300 by [hotio](https://github.com/hotio) PMS Version 1.32.2.7002 OS: CentOS Stream release 9 ``` Plex is running on my host, not container and testing the connection between Radarr and Plex returns success.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Radarr#7461
No description provided.