Unable to connect to Plex Server post reinstall | Tracearr | Page 1

dawn plumeBOT Feb 22, 2026, 9:29 AM

#

Thanks for opening a support thread!
Please include the following so we can help:

Required Information

• Tracearr version
• Environment (Docker, LXC, Unraid, etc.)
• Docker compose file
• Logs (pastebin.com) or screenshots

Describe The Issue

• Expected behavior
• Actual behavior
• Steps to reproduce

Read The Docs

Docs · Logs · FAQ

gleaming cobalt Feb 22, 2026, 9:34 AM

#

Tracearr version: 1.4.18
• Environment: Bare Metal Ubuntu
• Logs (pastebin.com) or screenshots : https://pastes.io/level30tim-33786

torpid dock Feb 22, 2026, 9:37 AM

#

can you provide your compose file please

gleaming cobalt Feb 22, 2026, 9:37 AM

#

https://pastes.io/docker-com?syntax=logs

torpid dock Feb 22, 2026, 9:39 AM

#

have you tried logging out and back into tracearr?

gleaming cobalt Feb 22, 2026, 9:40 AM

#

torpid dock have you tried logging out and back into tracearr?

Yes, tried it in a private window as well and in a different browser too

torpid dock Feb 22, 2026, 9:41 AM

#

looks like a networking issue

#

do you have split dns on your lan?

#

i.e does athena.odysseypx.com resolve to an internal IP on your network?

gleaming cobalt Feb 22, 2026, 9:42 AM

#

torpid dock i.e does athena.odysseypx.com resolve to an internal IP on your network?

Nope

#

The server is hosted on hetzner and the same resolves to the plex server ip.

#

I did go through some basic troubleshooting since I thought it would be dns.

torpid dock Feb 22, 2026, 9:45 AM

#

can you show me the output of this? docker exec -it tracearr wget -O - https://athena.odysseypx.com

#

i'm just unsure right now whether its an actual http connection issue or if the invalid plex token is causing the same exception throw

#

the wget should tell us

gleaming cobalt Feb 22, 2026, 9:49 AM

#

torpid dock can you show me the output of this? `docker exec -it tracearr wget -O - https://...

docker exec -it tracearr wget -O - https://athena.odysseypx.com
Connecting to athena.odysseypx.com (5.9.71.80:443)
wget: server returned error: HTTP/1.1 401 Unauthorized

torpid dock Feb 22, 2026, 9:52 AM

#

let me dig through some code, one moment

#

what about this? docker exec -it tracearr node -e "fetch('https://athena.odysseypx.com').catch(e => console.log(e.cause ?? e))"

gleaming cobalt Feb 22, 2026, 9:56 AM

#

torpid dock what about this? `docker exec -it tracearr node -e "fetch('https://athena.odysse...

docker exec -it tracearr node -e "fetch('https://athena.odysseypx.com').catch(e => console.log(e.cause ?? e))"
AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1134:18)
    at internalConnectMultiple (node:net:1210:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 5.9.71.80:443
        at createConnectionError (node:net:1678:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
        at listOnTimeout (node:internal/timers:607:11)
        at process.processTimers (node:internal/timers:541:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '5.9.71.80',
      port: 443
    },
    Error: connect ENETUNREACH 2a01:4f8:161:814e::2:443 - Local (:::0)
        at internalConnectMultiple (node:net:1206:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
        at listOnTimeout (node:internal/timers:607:11)
        at process.processTimers (node:internal/timers:541:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a01:4f8:161:814e::2',
      port: 443
    }
  ]

torpid dock Feb 22, 2026, 9:56 AM

#

bingo

#

tracearr (node) cant connect to your plex server, but wget could.. weird

gleaming cobalt Feb 22, 2026, 9:59 AM

#

It was working fine on the same version before, the only difference is I was using the supervised image from the older docs since it was an installation form a month or so ago

#

I kept updating it throughout till the server reinstall when I saw the docs again and it was changed

torpid dock Feb 22, 2026, 9:59 AM

#

can we try this: docker exec -it tracearr node -e "const s = require('net').connect(443, '5.9.71.80', () => { console.log('connected'); s.destroy(); }); s.on('error', e => console.log(e))"

gleaming cobalt Feb 22, 2026, 10:00 AM

#

torpid dock can we try this: `docker exec -it tracearr node -e "const s = require('net').con...

docker exec -it tracearr node -e "const s = require('net').connect(443, '5.9.71.80', () => { console.log('connected'); s.destroy(); }); s.on('error', e => console.log(e))"
connected

torpid dock Feb 22, 2026, 10:00 AM

#

ok getting somewhere, now try docker exec -it tracearr node -e "const tls = require('tls'); const s = tls.connect(443, '5.9.71.80', {servername: 'athena.odysseypx.com'}, () => { console.log('connected', s.getProtocol()); s.destroy(); }); s.on('error', e => console.log(e))"

#

i'm stepping through the layers of node networking here..

gleaming cobalt Feb 22, 2026, 10:01 AM

#

torpid dock ok getting somewhere, now try `docker exec -it tracearr node -e "const tls = req...

docker exec -it tracearr node -e "const tls = require('tls'); const s = tls.connect(443, '5.9.71.80', {servername: 'athena.odysseypx.com'}, () => { console.log('connected', s.getProtocol()); s.destroy(); }); s.on('error', e => console.log(e))"
connected TLSv1.3

torpid dock Feb 22, 2026, 10:01 AM

#

and now docker exec -it tracearr node -e "const https = require('https'); https.get('https://athena.odysseypx.com', r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))"

gleaming cobalt Feb 22, 2026, 10:02 AM

#

torpid dock and now `docker exec -it tracearr node -e "const https = require('https'); https...

docker exec -it tracearr node -e "const https = require('https'); https.get('https://athena.odysseypx.com', r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))"
AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1134:18)
    at internalConnectMultiple (node:net:1210:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 5.9.71.80:443
        at createConnectionError (node:net:1678:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
        at listOnTimeout (node:internal/timers:607:11)
        at process.processTimers (node:internal/timers:541:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '5.9.71.80',
      port: 443
    },
    Error: connect ENETUNREACH 2a01:4f8:161:814e::2:443 - Local (:::0)
        at internalConnectMultiple (node:net:1206:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
        at listOnTimeout (node:internal/timers:607:11)
        at process.processTimers (node:internal/timers:541:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a01:4f8:161:814e::2',
      port: 443
    }
  ]
}

torpid dock Feb 22, 2026, 10:02 AM

#

right

#

have you tried restarting the tracearr container?

gleaming cobalt Feb 22, 2026, 10:03 AM

#

torpid dock have you tried restarting the tracearr container?

yes, I can restart again

torpid dock Feb 22, 2026, 10:03 AM

#

no thats ok

#

can you add this line to your environment: section of the tracearr container in your compose file:

- NODE_OPTIONS=--dns-result-order=ipv4first

and then do a docker compose -f your.compose.file down and docker compose -f your.compose.file up -d

#

or actually, can you try this first: docker exec -it tracearr node -e "const https = require('https'); https.get('https://athena.odysseypx.com', {autoSelectFamily: false}, r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))" if its not too late

#

just trying to rule out ipv6

gleaming cobalt Feb 22, 2026, 10:06 AM

#

torpid dock or actually, can you try this first: `docker exec -it tracearr node -e "const ht...

docker exec -it tracearr node -e "const https = require('https'); https.get('https://athena.odysseypx.com', {autoSelectFamily: false}, r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))"
401

torpid dock Feb 22, 2026, 10:06 AM

#

if it is ipv6, we can disable that in your compose file

#

right

#

bingo

gleaming cobalt Feb 22, 2026, 10:07 AM

#

Hadn't done the env change yet

torpid dock Feb 22, 2026, 10:07 AM

#

ok dont do the above NODE_OPTIONS, lets disable ipv6 in the container

#

modify your compose file to put enable_ipv6: false under your tracearr_network, so it should look like this:

networks:
  tracearr-network:
    driver: bridge
    enable_ipv6: false

#

to the existing networks block down the bottom

#

and then the down and up commands from my earlier message

gleaming cobalt Feb 22, 2026, 10:08 AM

#

torpid dock modify your compose file to put `enable_ipv6: false` under your tracearr_network...

torpid dock Feb 22, 2026, 10:09 AM

#

docker compose -f your.compose.file down and docker compose -f your.compose.file up -d to restart the stack

#

after it comes back, the docker exec -it tracearr node -e "fetch('https://athena.odysseypx.com').catch(e => console.log(e.cause ?? e))" should succeed

#

if it does, you can try the web ui again

gleaming cobalt Feb 22, 2026, 10:11 AM

#

hahaha

#

Sorry

#

but same error again

torpid dock Feb 22, 2026, 10:11 AM

#

aw geez

gleaming cobalt Feb 22, 2026, 10:12 AM

#

torpid dock aw geez

 docker exec -it tracearr node -e "fetch('https://athena.odysseypx.com').catch(e => console.log(e.cause ?? e))"
AggregateError [ETIMEDOUT]: 
    at internalConnectMultiple (node:net:1134:18)
    at internalConnectMultiple (node:net:1210:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 5.9.71.80:443
        at createConnectionError (node:net:1678:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1737:38)
        at listOnTimeout (node:internal/timers:607:11)
        at process.processTimers (node:internal/timers:541:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '5.9.71.80',
      port: 443
    },
    Error: connect ENETUNREACH 2a01:4f8:161:814e::2:443 - Local (:::0)
        at internalConnectMultiple (node:net:1206:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
        at listOnTimeout (node:internal/timers:607:11)
        at process.processTimers (node:internal/timers:541:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a01:4f8:161:814e::2',
      port: 443
    }
  ]
}

torpid dock Feb 22, 2026, 10:12 AM

#

can you try the NODE_OPTIONS thing i mentioned before

gleaming cobalt Feb 22, 2026, 10:13 AM

#

Sure

torpid dock Feb 22, 2026, 10:14 AM

#

if that fails i still have a few tricks up my sleeve

#

i dont know if your technical or not, but even though ipv4 connect is also failing in that output, there is some known jank with nodes implementation of the happy eyeballs thing where a returning ipv6 result can poison the ipv4 attempt. so we are trying to tell node to completely ignore ipv6

#

the fact that the connections not using node are succeeding make me suspect this case

gleaming cobalt Feb 22, 2026, 10:15 AM

#

I did add the env var, it still failed with the same error above

torpid dock Feb 22, 2026, 10:15 AM

#

ok, lets try this: docker exec -it tracearr node -e "const https = require('https'); https.get('https://5.9.71.80/', {servername: 'athena.odysseypx.com'}, r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))"

#

this bypasses the dns lookup so we wont get ipv6 result at all

gleaming cobalt Feb 22, 2026, 10:16 AM

#

torpid dock ok, lets try this: `docker exec -it tracearr node -e "const https = require('htt...

docker exec -it tracearr node -e "const https = require('https'); https.get('https://5.9.71.80/', {servername: 'athena.odysseypx.com'}, r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))"
421

torpid dock Feb 22, 2026, 10:16 AM

#

right, this confirms it is the ipv6

#

can you show me your modified compose file?

gleaming cobalt Feb 22, 2026, 10:17 AM

#

torpid dock can you show me your modified compose file?

https://privatebin.net/?9414904d56b6a0cf#7sZ3oPkjnDLDnEv6o5QEc3SbVMpDzrQWCgPWeQVyWvyi

gleaming cobalt Feb 22, 2026, 10:18 AM

#

torpid dock right, this confirms it is the ipv6

would disabling ipv6 machine wide help?

torpid dock Feb 22, 2026, 10:18 AM

#

and just to confirm (sorry i have to ask), you are bring down the compose stack and starting it again ?

#

not just restarting the container

gleaming cobalt Feb 22, 2026, 10:18 AM

#

torpid dock and just to confirm (sorry i have to ask), you are bring down the compose stack ...

yes, did that post each change

#

torpid dock Feb 22, 2026, 10:19 AM

#

im not sure disabling ipv6 on the host will fix it, because its the dns result thats hinting at ipv6.

#

try this: docker exec -it tracearr node -e "const https = require('https'); https.get('https://athena.odysseypx.com', {autoSelectFamily: false}, r => { console.log(r.statusCode); r.resume(); }).on('error', e => console.log(e))"

gleaming cobalt Feb 22, 2026, 10:19 AM

#

Results in a 401

torpid dock Feb 22, 2026, 10:20 AM

#

sudo iptables -L DOCKER -n
docker network inspect tracearr_network | grep -i mtu

torpid dock Feb 22, 2026, 10:20 AM

#

gleaming cobalt Results in a `401`

this confirms its 100% ipv6.

gleaming cobalt Feb 22, 2026, 10:21 AM

#

torpid dock ```sudo ufw status sudo iptables -L DOCKER -n docker network inspect tracearr_ne...

ubuntu@zeus:~/Tracearr$ sudo ufw status
sudo iptables -L DOCKER -n
docker network inspect tracearr_network | grep -i mtu
[sudo] password for ubuntu: 
Status: inactive
Chain DOCKER (2 references)
target     prot opt source               destination         
ACCEPT     6    --  0.0.0.0/0            172.18.0.4           tcp dpt:3000
DROP       0    --  0.0.0.0/0            0.0.0.0/0           
DROP       0    --  0.0.0.0/0            0.0.0.0/0           
Error response from daemon: network tracearr_network not found

torpid dock Feb 22, 2026, 10:21 AM

#

ack sorry that should be tracearr-network not an underscore

gleaming cobalt Feb 22, 2026, 10:22 AM

#

torpid dock ack sorry that should be `tracearr-network` not an underscore

would be tracearr_tracearr-network 😛

#

sudo ufw status
sudo iptables -L DOCKER -n
docker network inspect tracearr_tracearr-network | grep -i mtu
Status: inactive
Chain DOCKER (2 references)
target     prot opt source               destination         
ACCEPT     6    --  0.0.0.0/0            172.18.0.4           tcp dpt:3000
DROP       0    --  0.0.0.0/0            0.0.0.0/0           
DROP       0    --  0.0.0.0/0            0.0.0.0/0

torpid dock Feb 22, 2026, 10:23 AM

#

uh docker might be calling it something weird, check with docker network ls

gleaming cobalt Feb 22, 2026, 10:23 AM

#

torpid dock uh docker might be calling it something weird, check with `docker network ls`

yep I did check

gleaming cobalt Feb 22, 2026, 10:24 AM

#

gleaming cobalt yep I did check

docker network ls
NETWORK ID     NAME                        DRIVER    SCOPE
7c35b41f0cf4   bridge                      bridge    local
49656ea58fa3   host                        host      local
204f3b7b51fb   none                        null      local
efc27e5ca830   tracearr_tracearr-network   bridge    local

torpid dock Feb 22, 2026, 10:24 AM

#

right ok

#

lets try modifying the compose again, and lets merge this into what you have:```services:
tracearr:
sysctls:
- net.ipv6.conf.all.disable_ipv6=1

#

so we will add the last 2 lines

gleaming cobalt Feb 22, 2026, 10:25 AM

#

torpid dock Feb 22, 2026, 10:25 AM

#

and then restart the stack: docker compose -f your.compose.file down and docker compose -f your.compose.file up -d

gleaming cobalt Feb 22, 2026, 10:27 AM

#

torpid dock and then restart the stack: docker `compose -f your.compose.file down` and `dock...

want me to run docker exec -it tracearr node -e "fetch('https://athena.odysseypx.com').catch(e => console.log(e.cause ?? e))" ?

torpid dock Feb 22, 2026, 10:27 AM

#

yes please

gleaming cobalt Feb 22, 2026, 10:27 AM

#

no errors on this

torpid dock Feb 22, 2026, 10:27 AM

#

fantastic

gleaming cobalt Feb 22, 2026, 10:27 AM

#

let me try to login

torpid dock Feb 22, 2026, 10:27 AM

#

yes

gleaming cobalt Feb 22, 2026, 10:27 AM

#

yep, that worked

#

thanks a lot for the help

torpid dock Feb 22, 2026, 10:28 AM

#

you should be fine to remove the NODE_OPTIONS and the disable_ipv6 stuff we added, and just keep that sysctl part.
and i will get this added to the docs FAQ for future issues

#

can you try removing those so i can confirm they arent needed?

gleaming cobalt Feb 22, 2026, 10:28 AM

#

torpid dock can you try removing those so i can confirm they arent needed?

yep 1 moment

torpid dock Feb 22, 2026, 10:29 AM

#

so we just keep this bit: sysctls: - net.ipv6.conf.all.disable_ipv6=1

gleaming cobalt Feb 22, 2026, 10:29 AM

#

yep, works just with that

torpid dock Feb 22, 2026, 10:30 AM

#

great

gleaming cobalt Feb 22, 2026, 10:30 AM

#

Thank you @torpid dock , much appreciated ❤️

torpid dock Feb 22, 2026, 10:30 AM

#

hope you enjoy tracearr ❤️

gleaming cobalt Feb 22, 2026, 10:31 AM

#

torpid dock hope you enjoy tracearr ❤️

I have been, cheers to you guys

#

now back to importing tautulli db again

torpid dock Feb 22, 2026, 10:32 AM

#

haha goodluck that can be a pain

sharp nest Feb 22, 2026, 11:41 AM

#

torpid dock haha goodluck that can be a pain

Oh you’ve done it? 😏👀😂

torpid dock Feb 22, 2026, 11:43 AM

#

sharp nest Oh you’ve done it? 😏👀😂

luckily i have never had to deal with it, only experience through others.. but as with all things we only see the bad times, not the good.

sharp nest Feb 22, 2026, 11:48 AM

#

torpid dock luckily i have never had to deal with it, only experience through others.. but a...

There is one thing I haven’t dug into and that’s an endpoint that accepts sql… but I think you have to change an env var in Tautulli. Which is more of a hassle than i want for the experience

gleaming cobalt Feb 22, 2026, 2:50 PM

#

btw @torpid dock , is there any way to cancel a library sync?

torpid dock Feb 22, 2026, 2:51 PM

#

no

#

you could interrupt it by restarting the container, but it would just start syncing again when it starts up

gleaming cobalt Feb 22, 2026, 2:51 PM

#

Hmm, alright ty.

#

Library sync for me always takes upto 4-5 hours sometimes more.

torpid dock Feb 22, 2026, 2:52 PM

#

thats strange. do you have any errors in the log?

gleaming cobalt Feb 22, 2026, 2:54 PM

#

I don't see anything at all

#

📎 message.txt

#

There's a tautulli import pending since it was interuppted but that's all

torpid dock Feb 22, 2026, 2:59 PM

#

Gotta feed my cat, brb

#

ok back

#

can you browse to /debug and go to Tasks, do you have failed jobs?

gleaming cobalt Feb 22, 2026, 3:04 PM

#

torpid dock can you browse to /debug and go to Tasks, do you have failed jobs?

nope

#

torpid dock Feb 22, 2026, 3:06 PM

#

I'm not clued up on the import tasks at all, we may need @sharp nest here

#

is the progress moving at all?

#

in the debug Overview page, can you show the counts on the top section of the page

gleaming cobalt Feb 22, 2026, 3:08 PM

#

torpid dock is the progress moving at all?

would sound strange but that bar on the library sync job has moved from 5-99% and back multiple times, each time I've refreshed after a certain time has passed

gleaming cobalt Feb 22, 2026, 3:09 PM

#

torpid dock in the debug Overview page, can you show the counts on the top section of the pa...

torpid dock Feb 22, 2026, 3:10 PM

#

keep an eye on those figures, see if they change

#

you will need to refresh the page i think, they wont auto update

gleaming cobalt Feb 22, 2026, 3:10 PM

#

torpid dock you will need to refresh the page i think, they wont auto update

Will keep an eye out

torpid dock Feb 22, 2026, 3:10 PM

#

Galla should be around in a while, he's the boss

#

the connection to your plex is going out over the internet yeah?

gleaming cobalt Feb 22, 2026, 3:12 PM

#

torpid dock the connection to your plex is going out over the internet yeah?

yep

#

I get around 150-200 Mbps to the server itself

torpid dock Feb 22, 2026, 3:12 PM

#

can you see the network bandwidth graph over on the plex dashboard?

#

just to see if its actually doing something

gleaming cobalt Feb 22, 2026, 3:13 PM

#

torpid dock can you see the network bandwidth graph over on the plex dashboard?

#

But there's 10 streams running right now too

torpid dock Feb 22, 2026, 3:13 PM

#

yeah, so hard to tell if its media playback or the import

#

do you have some docker monitoring to show you the tracearr bandwidth?

gleaming cobalt Feb 22, 2026, 3:14 PM

#

np, I'll keep an eye out.

iirc took a long time last time as well

gleaming cobalt Feb 22, 2026, 3:14 PM

#

torpid dock do you have some docker monitoring to show you the tracearr bandwidth?

I'll set up beszel, was supposed to after the os reinstall

sharp nest Feb 22, 2026, 3:14 PM

#

gleaming cobalt Library sync for me always takes upto 4-5 hours sometimes more.

Manual, or auto triggers

torpid dock Feb 22, 2026, 3:15 PM

#

mmm beszel looks nice, new toy thank you

gleaming cobalt Feb 22, 2026, 3:15 PM

#

sharp nest Manual, or auto triggers

this one was manual, after I added the 2 servers and synced

sharp nest Feb 22, 2026, 3:16 PM

#

I mean yeah that’s gonna take awhile for sure

#

It’s building a full historical snapshot of the new severs

torpid dock Feb 22, 2026, 3:18 PM

#

i think as long as those numbers keep increasing on the overview page, its going

#

there are many factors contributing to the time. network, disk reads/writes, cpu.. and then apply that to both ends plex/tracearr

#

postgres is probably writing index updates like mad

#

(i imagine)

gleaming cobalt Feb 22, 2026, 3:26 PM

#

gleaming cobalt

Diff

#

17 mins between both screenshots

torpid dock Feb 22, 2026, 3:34 PM

#

thats... slower than i would like

#

or i would expect rather

sharp nest Feb 22, 2026, 3:36 PM

#

The daily ones def can be improved, but the first ones do a lot of different things to build out the historical timescale views

#

And then compact them, and then clean up the data used to make them

torpid dock Feb 22, 2026, 3:37 PM

#

let us know when you get beszel on there, so we can see some perf stats on those containers

gleaming cobalt Feb 22, 2026, 3:45 PM

#

torpid dock let us know when you get beszel on there, so we can see some perf stats on those...

torpid dock Feb 22, 2026, 3:47 PM

#

disk i/o ?

gleaming cobalt Feb 22, 2026, 3:50 PM

#

That's been flat at 0 KB/s

torpid dock Feb 22, 2026, 3:51 PM

#

which makes sense given it updates like 3 records in 30 minutes

#

so its a networking bottleneck ?

#

assuming cpu is low

gleaming cobalt Feb 22, 2026, 3:52 PM

#

torpid dock assuming cpu is low

Yep

#

This is to the Plex server itself

#

There shouldn't be a networking bottleneck tbh

torpid dock Feb 22, 2026, 3:55 PM

#

it remains a mystery, there must be a bottleneck somewhere. maybe disk io on plex pulling the data out?

#

or the API on tautulli

#

wherever the import is coming from

gleaming cobalt Feb 22, 2026, 3:56 PM

#

Question, does Tracearr pull data from the library itself for library sync or from the Plex DB?

sharp nest Feb 22, 2026, 3:56 PM

#

gleaming cobalt

What

#

I mean we don’t have direct access to the plex database if that’s what you are asking

gleaming cobalt Feb 22, 2026, 3:59 PM

#

Got it, had the thought that since the library is on gdrive, it might be an APi ban.
But just checked, no ban yet.

sharp nest Feb 22, 2026, 3:59 PM

#

I’m sorry… what

#

Your library for plex is on Google Drive?

gleaming cobalt Feb 22, 2026, 4:00 PM

#

Yes

torpid dock Feb 22, 2026, 4:01 PM

#

https://tenor.com/bhMu8.gif

Tenor

sharp nest Feb 22, 2026, 4:01 PM

#

Well, I don’t have an award to actually give you

gleaming cobalt Feb 22, 2026, 4:01 PM

#

Not personal gdrive, but on an enterprise acc

sharp nest Feb 22, 2026, 4:01 PM

#

But that’s definitely up there for one of the wonkiest setups

torpid dock Feb 22, 2026, 4:02 PM

#

i'm going to go ahead and say that would be the cause of the slowness

#

tracearr talks to plex via api, plex then queries its internal DB, and if thats on gdrive, you are doing random reads on a large file on an internet storage device

sharp nest Feb 22, 2026, 4:03 PM

#

Yeah you have decided to use bottlenecks as a future.

I’m sure all your media is 100% legal too so there is no exposure on your end either or TOS broken

#

awkward_look

gleaming cobalt Feb 22, 2026, 4:03 PM

#

People did use to run that when google was lax on limits

torpid dock Feb 22, 2026, 4:03 PM

#

its linux ISO's all the way down, of course we know that

sharp nest Feb 22, 2026, 4:03 PM

#

gleaming cobalt People did use to run that when google was lax on limits

Used to is a very key thing here

#

But yes, you should expect bottlenecks

torpid dock Feb 22, 2026, 4:04 PM

#

forget limits and legality. a database on an internet storage device is a world of pain. you cant fseek() to the middle of a file you have to read the contents of the whole thing until you reach the part you want

#

and you are now doing this thousands of times

#

because tracearr is asking plex to do it

gleaming cobalt Feb 22, 2026, 4:05 PM

#

to be clear, the first time I let it run overnight 😛

sharp nest Feb 22, 2026, 4:05 PM

#

I mean your results can and will probably vary

#

It’s an improper setup for a plex server

torpid dock Feb 22, 2026, 4:06 PM

#

if your total is 564,519 and you currently up to 565,403, and you did 1 title in 30 minutes, that should give you an ETA

#

wait, no ignore that

#

your library has grown since haha

gleaming cobalt Feb 22, 2026, 4:07 PM

#

ye that's a week old screenshot

torpid dock Feb 22, 2026, 4:09 PM

#

well i think we know why its going slowly, so all you can do is wait

gleaming cobalt Feb 22, 2026, 4:13 PM

#

it finished finally

#

Just these are pending now

#Unable to connect to Plex Server post reinstall