#Config errors

1 messages · Page 1 of 1 (latest)

kind patrolBOT
#

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

Including the meta.log from the beginning is a huge help use !logs for more information.

dim sand
#

@frank onyx you have shared your plex token. Please delete the token and create a new one for your plex server

#

Never share passwords or tokens here

#

I deleted the message but you should still make changes to your token

graceful tideBOT
#
Providing Log Files

You have been asked to provide your log file, which will allow us to support you further.

You can find your meta.log file within the logs folder of your Plex Meta Manager config folder [right next to config.yml].

You can drag-and-drop your meta.log file directly into Discord, you do not need to upload it to a third-party site unless it exceeds the 50mb size limit.

Please DO NOT manually extract, copy and paste text from your log files directly into Discord as the formatting can be difficult to read and can often redact parts of the log file that are important for full context.

#
Providing a redacted config.yml file

You have been asked to provide your config file, which will allow us to support you further.

Please DO NOT share your config.yml file as is without redacting it. It contains information that you do not want the public to have, nor do we need it to troubleshoot your scenario in MOST cases.

We will use a regex parser to redact the file for you.

:one: Goto https://regex101.com/r/DMo1DQ/latest
:two: Copy the contents of your config.yml to the TEST STRING box in that page
:three: The results will be immediate and found in the SUBSTITUTION box below
:four: From the SUBSTITUTION box, select all, then copy and paste the redacted text into the channel where you want to share your config. (You will see (redacted) where confidential information was replaced)

Consider using Discord code blocks when sharing small parts of your config file. Check out !code for more info on code blocks

dim sand
#

Btw, did you follow the wiki for installation?

graceful tideBOT
#
Wiki Links

You can find access to the Plex Meta Manager Wiki for each branch at the following links:

Please use the correct link for the branch that you're running, as each branch's wiki has information that may not yet be available in other branches.

frank onyx
# dim sand Btw, did you follow the wiki for installation?

Thank you for deleting the post, my appoligies. I updated the token.
I tried using the wiki with the generic config.yml file (just trying to get it to work as a proof of concept), but I got the same error. In a attempt to resolve the error the config file is now copied from a github file that was closer to my desired result. Both config files were generating the same error trying to connect to plex.

Attached are the log and redacted config files (config file was too long to copy paste).

civic zenith
#

[ERROR] | Plex Error: Plex url is invalid

#

how exactly have you set the plex url part of your config? if its a private LAN IP you can safely post the entire url here

frank onyx
#

Hi zaP!
url: 192.168.1.78:32400

civic zenith
#

use url: http://192.168.1.78:32400 instead and try again

dim sand
#

And maybe even https

sour jasper
#

plex: # Can be individually specified per library as well
url: http://10.1.1.9:32400
token: *********
timeout: 60
clean_bundles: false
empty_trash: false
optimize: false

graceful tideBOT
#
Using Code Blocks

Please use code blocks when sending any code-related text (such as error messages or configuration file extracts.)

The Grave Accent key (`) is used to define code blocks and is typically found to the left of the number 1 key on a standard keyboard.

See the below sample text and output for basic code block text.

YOU TYPE THIS

`​`​`hello`​`​`

DISCORD DISPLAYS
hello

If you are posting any yaml-formatted text (such as collections), you can give your code block YAML formatting. See the below sample text and output

YOU TYPE THIS

`​`​`yaml
collections:
  Documentaries:
    smart_filter:
      all:
        genre: Documentary
`​`​`

DISCORD DISPLAYS

collections:
  Documentaries:
    smart_filter:
      all:
        genre: Documentary
dim sand
#

This seems like a PMM setup issue with Unraid as well as I see directories missing in the meta.log

civic zenith
#

afaik https shouldnt be needed by default and if used can cause a lof other issues to figure out first, if both plex server and pmm are in the samd, trusted, local network i would highly recommend http instead simply to save a lot of headache with plex's ssl certs

frank onyx
civic zenith
#

ohh unraid again, well i gotta go, errr my kid is sick! take over frostymoose 😂

sour jasper
#

My plex is running on a qnap

civic zenith
#

where is your pmm and your plex server running? are you using docker? are you sure that ip is reachable?

frank onyx
#

PMM and plex are both running on the unraid server. both are in their own docker containers. Plex is reachable in my network via https://192.168.1.78:32400

civic zenith
#

frosty is probably more qualified about unraid stuff here but to me this smells a lot like a docker network config problem

dim sand
#

Yup

civic zenith
#

you basicallly need to make sure they can both talk to each other

dim sand
#

Essentially it seems that the PMM container cannot talk to the plex container

civic zenith
#

yep, and if the token was wrong you would get a different error, so it seems more likely that its like *there is nothing at this url talking to me at all"

frank onyx
#

@dim sand that makes sense. I have set up and tried enough config files that I am pretty confident one of them had to be good, but they all had the same issue of not able to connect to plex.
The PMM docker in unraid did not come with port configuration enabled, if you are also using PMM in a docker, did you map it to a specific port?

civic zenith
#

pmm doesnt need any port mapped

#

typically you only need to map ports for incoming connections, not for outgoing, so pmm doesnt act as a server for incoming connections so this isnt needed, it can open connections outgoing anyway

#

but your plex server needs to accept incoming connections on its port and needs to be mapped, but since you can reach it from other clients, i would say ports are not the issue

#

its that pmm has no clue how to reach that ip of your plex server, ignore the port

dim sand
#

Btw, are you using lsio image for PMM?

#

Screenshots of plex container and PMM container advanced settings could be useful

#

Try PMM in bridge mode please. Do not use lsio image for pmm

civic zenith
#

that first^ if that still doesnt work, i think when both are running in host mode using url: http://127.0.0.1:32400 would work too? unsure but easy to try out

dim sand
#

Btw, you exposed your plex claim in that image

civic zenith
#

noticed that too hehe but im quite sure the claim token can only be used once and is worthless after, still good to remove it from here

frank onyx
#

Much appreciated. TY
bridge mode did not make any changes. Still the same error

dim sand
#

Stick with http as well

frank onyx
#

let me update the config. Its currently https

civic zenith
#

http is definitly the way to go but even if using https and that would cause this problem, im sure the error would very different

frank onyx
#

It looks to be failing at the same point with http and bridge mode. Update logs attached.

dim sand
civic zenith
#

try host mode for both and 127.0.0.1 as ip

dim sand
#

That is my setup

civic zenith
#

then im out of ideas

dim sand
#

I am using hotio plex media server

frank onyx
#

Everything looks to be the same, except I am using the official plex container.
I will experiment around with hotio. Thank you both for you assistance!

dim sand
#

Sure thing the other thing you might try is switching branches of PMM

#

Nightly or develop

#

It won’t change much, but the Mets.log contains more info for troubleshooting

frank onyx
#

is that set here?

dim sand
#

Yes

frank onyx
#

cool. I will switch to develop

dim sand
#

We’re you testing all this in nightly?

frank onyx
#

No, the branch I was in was "meisnate12/plex-meta-manager". I noticed yours was nightly in the screen shots so just tried a few min ago

#

I will do through the develop Mets.log in the morning.
Thank you again for all your help. I appreciate it

kind patrolBOT
#

This post has been marked as Resolved and will be closed in one hour.

If you require further assistance on this issue, you can send another message in this post to re-open it.

If you require further support that is unrelated to this post, please start a new post and do not re-open this one.

Thanks for using Plex Meta Manager.

frank onyx
#

@dim sand I found the issue. The setting in Plex for "secure connections" was set to required.
After i updated it to "preferred", PMM ran without issues.
Thanks again for your help debugging my set up.

dim sand
#

woot!