Closed gerryflux closed 4 months ago
If you have a trailing / in your server url for the media server address, this failure occurs. Remove the trailing slash and suddenly everything works flawlessly. It would be a good idea to check and correct this issue seamlessly behind the scenes when validating.
I can confirm that's not the issue
The connection to Plex works fine, it can scan and identify the libraries.
With the trailing slash I was able to connect Wizarr to Plex, scan the libraries, etc. Everything appeared to work, but invites would consistently fail. Removing the trailing slash solved that issue for me.
I'm also having this issue. Did you manage to get it sorted?
If you're having this issue then you must have an issue with your Plex Token. Please ensure you're grabbing the correct Plex Token and not a temporary one. This is a very small case issue which can be rectified by yourself.
Like mentioned, check you don't have a trailing slash, this issue has been fixed on the beta branch. Any other issues caused by inviting is most likely an incorrect Plex Token.
Please read the official Plex documenation: https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
They also detail "Getting a New Token" which occurs for some users, not most.
I use jellyfin not plex and don't have a trailing slash
I use jellyfin not plex and don't have a trailing slash
Then this issue does not apply to you. Reach out on Discord and i'll assist.
Will do
Originally posted by @gerryflux in https://github.com/wizarrrr/wizarr/issues/281#issuecomment-1901815666