Sorry for the late reply. I made my post and promptly left town. I’m back at home now and I downloaded the latest version you released yesterday, and am having the same problem. Verbose logging reveals that it’s trying to reach Plex on IP addresses that will never work.
18:51:16.291 › Selected server: hippie
18:51:16.293 › Checking address for server: hippie
18:51:16.294 › Checking: https://172.18.0.5:32400
18:51:17.214 › ET Created
18:51:20.872 › Export Main type selected: 15
18:51:21.321 › No response recieved
18:51:21.321 › Checking: https://<PUBLIC IP ADDRESS REDACTED>:32400
18:51:22.196 › Secondary export type selected as: 2001
18:51:22.196 › Export Sec type selected: 2001
18:51:22.196 › Getting list of libraries
18:51:22.196 › Target is: 15
18:51:22.197 › fetchSections called
18:51:22.198 › Getting levels for: 2001
18:51:22.198 › ET LevelNames: {"Level 1":"level1","Level 2":"level2","All":"all"}
18:51:22.198 › ET Custom LevelNames: {}
18:51:26.322 › No response recieved
18:51:26.323 › Returning valid address as:
The first IP address it tries is the IP address of my Plex Docker container (172.18.0.5), which isn’t going to be accessible unless I run this on the same machine as the Plex Docker container. The second IP address is my public IP address, which isn’t going to be reachable inside my network either.
To further confirm that this is the problem, I was able to use WebTools-NG to export a playlist when I was away from home, outside my local network.
I just enabled NAT reflection on my firewall and it started working. This is a satisfactory solution for me, but I’m happy to help with testing if you want to support a use case where someone is running Plex in Docker and enabling NAT reflection is not an option for them.
