#my script wont run correctly constantly getting this error when it tries to connect to plex library
1 messages ยท Page 1 of 1 (latest)
You can press the "Close Post" button above or type /close at any time to close this post.
๐ Great! Let's start to review and make recommendations, electricales... ๐
๐ If you want to review this again, electricales:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐
Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation โ
Page 05: Plex Configuration - Section 1
Page 06: Rec 01 - ๐ ๏ธ INCOMPLETE LOGS
Page 07: Rec 02 - Error: PMM scheduled time is missing.
Page 08: Rec 03 - Error: Memory value not found in content.
Page 09: Rec 04 - โฑ๏ธ TIMEOUT ERROR
@paper bone if you can throw the meta.log in here, that would help
what I see is a timeout
๐ Great! Let's start to review and make recommendations, electricales... ๐
๐ If you want to review this again, electricales:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐
typing !timeout as the bot suggests:
You're seen an error which includes one or both of:
socket.timeout: timed out
or
Unknown Error: HTTPConnectionPool(host='SOME_IP, port=SOME_PORT): Max retries exceeded with url: SOME_URL
Typically this is your Plex server timing out when PMM tries to connect to it. There's nothing PMM can do about this directly. You can try increasing the connection timeout in config.yml:
plex:
url: http://bing.bang.boing
token: REDACTED
timeout: 360 <<< right here
But that's not a guarantee.
Effectively what's happening here is that you're ringing the doorbell and no one's answering. You can't do anything about that aside from waiting longer. You can't ring the doorbell differently.
This seems to happen most often in an Appbox context, so perhaps contact your appbox provider to discuss it.
You're seen an error which includes one or both of:
socket.timeout: timed out
or
Unknown Error: HTTPConnectionPool(host='SOME_IP, port=SOME_PORT): Max retries exceeded with url: SOME_URL
Typically this is your Plex server timing out when PMM tries to connect to it. There's nothing PMM can do about this directly. You can try increasing the connection timeout in config.yml:
plex:
url: http://bing.bang.boing
token: REDACTED
timeout: 360 <<< right here
But that's not a guarantee.
Effectively what's happening here is that you're ringing the doorbell and no one's answering. You can't do anything about that aside from waiting longer. You can't ring the doorbell differently.
This seems to happen most often in an Appbox context, so perhaps contact your appbox provider to discuss it.
okay ill try increasing the timeout see if that fixes it
as teh message says... it might help
Rec02 is another easy fix... won't solve the timeout, but will help future-proof your config
what's Rec02? sorry I am very new to PMM. the timeout issue could also be cause I'm currently downloading a bunch of stuff
Nevermind I figured out what Rec02 was. I will definetly fix that too.