#HTTPConnectionPool Errors

1 messages · Page 1 of 1 (latest)

scenic sun
#

Hello. Seeing a handful of these today
HTTPConnectionPool(host=127.0.0.1, port=32400): Max retries exceeded with url: /library/sections/15/label (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x10caf0680>, Connection to 127.0.0.1 timed out. (connect timeout=60)))
that I don't understand. Anything I can do?

📎 meta.log Screenshot_2026-02-02_at_17.45.38.png
honest pebbleBOT
#

📝 If you want to review this again, rothnd_07346:
: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> 📝

#

Welcome @scenic sun!

Someone from <@&938443185347244033> will assist when they're available.

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

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

#

You can press the "Close Post" button above or type /close at any time to close this post.

honest pebbleBOT
#
**User Info**

Author of Linked Message: TheOneTheOnly
Person who Invoked the Command: TheOneTheOnly
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Plex Configuration - Section 3
Page 08: Plex Configuration - Section 4
Page 09: Plex Configuration - Section 5
Page 10: Plex Configuration - Section 6
Page 11: Rec 01 - 💥 TRACEBACK ERROR
Page 12: Rec 02 - ❌ [ERROR]
Page 13: Rec 03 - ❌⏱️ TIMEOUT ERROR
Page 14: Rec 04 - ⚠️ [WARNING]
Page 15: Rec 05 - ⚠️ NO ITEMS FOUND IN PLEX
Page 16: Rec 06 - 💬 CONVERT WARNING

Page 1/16
silent portal
#

Kometa's trying to open a connection to 127.0.0.1 on port 32400 and that connection attempt is timing out. There's nothing Kometa can do about this aside from waiting longer, which you'd do by putting a bigger number here:

plex:
  timeout: 60
scenic sun
#

I'm seeing now that Plex just isn't reachable on 127.0.0.1

silent portal
#

Is Plex running on this Mac?

scenic sun
#

Yep, I think buggy update. Stopped/Restarted asked to login again. Getting to a new Kometa run.

#

Apparently not the cause. http://127.0.0.1:32400/webis going in and out. During this Kometa run it started failing to resolve again and throwing the timeout.

silent portal
#

Why not use the actual IP of the Mac?

scenic sun
#

Where? I'm just going by the error Kometa is throwing with that 127.0.0.1

silent portal
#

!noredact
In the the kometa config. Instead of:

plex:
  url: http://127.0.0.1:32400
  token: (redacted)

use:

plex:
  url: http://192.168.1.50:32400
  token: (redacted)

or whatever the LAN IP of the Mac is.

#

Also, no idea what "going in and out" means. Sounds like a networking issue that Kometa has nothing to do with and no control over.

scenic sun
#

Ok, I'm getting lost. When I visit that LAN based link it seems different. And more importantly, when I Get Info<View XML there's no token at the end of the url

silent portal
#

it seems different

different to what and how specifically?

If you are running a browser on this Mac, and the Mac's LAN IP is 192.168.1.50, then these two URLs:

http://192.168.1.50:32400  > the computer on the LAN with IP 192.168.1.50
http://127.0.0.1:32400     > the computer from which I am making the request

point to exactly the same thing

Now, maybe Plex responds differently to one vs the other [though I have never seen that], but from a networking and Kometa perspective they are exactly the same.

silent portal
#

But you aren't visiting it in a browser you are connecting to it with the Plex API.

#

So what the browser shows is immaterial.

scenic sun
#

Yes those links point to exactly the same thing, this I know. What was different was that it wasn't seeing me as signed-in on the LAN IP url. But even after sign-in, trying to get the token yields a different token for each url..." Which is Kometa looking for exactly?

silent portal
#

Kometa doesn't care where the token came from. It isn't looking for some specific token.

Ideally, you will use a token that you specifically generated for Kometa's use, not one taken from a URL.

The nightly wiki has a form you can use to generate such a token. If you use a webclient token or a server token, there are some odd issues that can result.

scenic sun
#

k

silent portal
#

Hover over the "pages" icon at the top of the page next to the search field OR click on "latest" down in the lower right OR change latest to nightly in the URL.

#

Doesn't matter to the API:

> python theonetheonly.py --url http://127.0.0.1:32400 --token BLAH
Connecting to http://127.0.0.1:32400...
------------------------------
Server Name:    Home-test
Plex Version:   1.42.1.10060-4e8b05daf
Platform:       Linux 6.14.0-36-generic
------------------------------
> python theonetheonly.py --url http://localhost:32400 --token BLAH
Connecting to http://localhost:32400...
------------------------------
Server Name:    Home-test
Plex Version:   1.42.1.10060-4e8b05daf
Platform:       Linux 6.14.0-36-generic
------------------------------
> python theonetheonly.py --url http://192.168.1.11:32400 --token BLAH
Connecting to http://192.168.1.11:32400...
------------------------------
Server Name:    Home-test
Plex Version:   1.42.1.10060-4e8b05daf
Platform:       Linux 6.14.0-36-generic
------------------------------
#

Using the top menu will drop you back at the front page.

Editing the URL or using the bottom-right menu will leave you on the page you are currently viewing.

drowsy dune
#

Using the menu in the bottom right-ish corner, always keeps me where I am and just changes me to nightly

silent portal
scenic sun
#

K. So I'm using the Auth Tool. It says I'm from an odd location and gives me a new window with Authentication complete. You can close this window.

drowsy dune
#

So close the window…

scenic sun
#

Um.. What about the Plex section in config..

drowsy dune
#

The new window is what I was referring to, to close. The one that says “you can close this window”

scenic sun
#

I get that, close the window, check, now what

drowsy dune
#

What is in the wiki authorization

scenic sun
#

`What happens next:

  1. Click the button below
  2. Sign in with your Plex account in the popup window
  3. Copy your access token to use with Kometa`? I'm asking where because I'm not seeing a token being generated (or the IP on which it is based, because all I've seen is close window
silent portal
scenic sun
#

Thank you. It seems an actual answer today. It did not do that properly in the wiki.

silent portal
silent portal
scenic sun
#

Yea, I wasn't getting Your Plex Access Token from the wiki form

#

Wasn't referring to you

drowsy dune
#

@silent portal I just tried and it keeps telling me pop up blocked. They’re not blocked. I’ve refreshed the page a few times, keeps logging in and then a new window opens that tells me I can close

silent portal
#

Hm, must be a readthedocs idiosyncrasy.

scenic sun
#

Yea but what does the wiki say

drowsy dune
#

Cool, the direct link does work

drowsy dune
silent portal
# scenic sun Yea but what does the wiki say

The wiki says to use the form in the page [at least it does for now], which worked when I tested it locally before deployment. Apparently readthedocs is behaving differently to a local mkdocs server in some regard.

scenic sun
#

Ah 👍

drowsy dune
silent portal
#

And the wiki no longer contains the embedded version.

scenic sun
#

lol. Any way to retrieve one of these tokens after the fact?

silent portal
scenic sun
#

Ok cool