RaunoT
Unable to set up at all
Plex Rewind Version
4.4.3
Description
I've been trying to set up Plex Rewind since early 2025. But for the life in me I can;t figure it out. Maybe someone can help with this.
i'm on UnRAID and below is my config:
at the setup screen, I enter the public domains of my overseer and tautulli with the respective api keys.
i have Secure Connection Required and Strict TLS configuration enabled on my Plex
first i try with the lan http ip & port for Plex. error Plex - cannot connect
then i try with the lan https ip & port for Plex. error Plex - cannot connect
next, I try with the public domain for my plex. I get through but redirected to a 404 page.
if i refresh the 404 page, I am redirected to the login page, with the message Setup needs to be done by the admin and i can't do anything else.
this has been bugging me for so long 😢 please help me figure out what i'm doing wrong.
Thanks.
Steps to reproduce
at the setup screen, I enter the public domains of my overseer and tautulli with the respective api keys.
i have Secure Connection Required and Strict TLS configuration enabled on my Plex
first i try with the lan http ip & port for Plex. error Plex - unable to connect!
then i try with the lan https ip & port for Plex. error Plex - unable to connect!
next, I try with the public domain for my plex. I get through but redirected to a 404 page.
if i refresh the 404 page, I am redirected to the login page, with the message Setup needs to be done by the admin and i can't do anything else.
Screenshots
No response
Logs
✓ Starting... [66/989]
✓ Ready in 121ms
[CONFIG] - Error testing Plex connection! TypeError: fetch failed
at node:internal/deps/undici/undici:13392:13
at async o (/app/.next/server/app/settings/connection/page.js:1:7086)
at async /app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/n
ode_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:418
at async rT (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]
.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:8148)
at async ne (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]
.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1144)
at async doRender (/app/node_modules/.pnpm/[email protected][email protected][email protected]__reac
[email protected]/node_modules/next/dist/server/base-server.js:1406:30)
at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/[email protected]_react
[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1567:28)
at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/next@14
[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:
1475:28)
at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/[email protected]_react-dom
@[email protected][email protected]/node_modules/next/dist/server/base-server.js:1901:24)
at async NextNodeServer.renderToResponseImpl (/app/node_modules/.pnpm/[email protected]_react-do
[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1939:32) {
[cause]: SocketError: other side closed
at Socket.<anonymous> (node:internal/deps/undici/undici:6238:28)
at Socket.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'UND_ERR_SOCKET',
socket: {
localAddress: '172.17.0.20',
localPort: 45724,
remoteAddress: '10.10.0.111',
remotePort: 32400,
remoteFamily: 'IPv4',
timeout: undefined,
bytesWritten: 215, [31/989]
bytesRead: 0
}
}
}
[CONFIG] - Error testing Plex connection! TypeError: fetch failed
at node:internal/deps/undici/undici:13392:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async o (/app/.next/server/app/settings/connection/page.js:1:7086)
at async /app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/n
ode_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:418
at async rT (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]
.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:8148)
at async ne (/app/node_modules/.pnpm/[email protected][email protected][email protected][email protected]
.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1144)
at async doRender (/app/node_modules/.pnpm/[email protected][email protected][email protected]__reac
[email protected]/node_modules/next/dist/server/base-server.js:1406:30)
at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/[email protected]_react
[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:1567:28)
at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/next@14
[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:
1475:28)
at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/[email protected]_react-dom
@[email protected][email protected]/node_modules/next/dist/server/base-server.js:1901:24) {
[cause]: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altna
mes: IP: 10.10.0.111 is not in the cert's list:
at Object.checkServerIdentity (node:tls:316:12)
at TLSSocket.onConnectSecure (node:_tls_wrap:1687:27)
at TLSSocket.emit (node:events:518:28)
at TLSSocket._finishInit (node:_tls_wrap:1076:8)
at ssl.onhandshakedone (node:_tls_wrap:862:12)
at TLSWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ERR_TLS_CERT_ALTNAME_INVALID',
reason: "IP: 10.10.0.111 is not in the cert's list: ",
host: '10.10.0.111',
cert: {
subject: [Object: null prototype],
issuer: [Object: null prototype],
subjectaltname: 'DNS:*.26ca9cb21e6d4a628ea4a85e3747dd0c.plex.direct',
infoAccess: [Object: null prototype],
ca: false,
bits: 256,
pubkey: <Buffer 04 81 bc 8c 0b f3 b8 1d bd 45 4a 68 06 12 e3 04 8f 6a dd be 3c d9 b5 dc 2
a ac 1f c8 d5 fc ae e5 fd 33 72 a3 19 85 13 36 72 39 0d 05 7d 5a cc af 7c 09 ... 15 more bytes>
,
asn1Curve: 'prime256v1',
nistCurve: 'P-256',
valid_from: 'Feb 4 02:34:56 2025 GMT',
valid_to: 'May 5 02:34:55 2025 GMT',
fingerprint: '59:A8:29:E8:C2:19:04:5B:4A:3F:AA:82:FA:2E:BC:73:23:04:C8:5E',
fingerprint256: '6B:94:44:66:23:60:53:BD:2C:B9:2B:A2:FC:FA:97:F2:7B:2B:B2:F9:04:87:CA:44:
20:30:B2:B7:35:E1:EF:C5',
fingerprint512: '63:92:46:8F:05:BA:92:DB:8A:F9:9D:75:F6:2D:5C:96:6C:4C:88:9A:0F:D5:67:28:
13:20:EA:59:09:41:00:9E:BB:8B:E9:40:6E:BA:26:99:A5:AA:75:A3:F8:7B:F9:F9:CB:F9:97:A3:AB:5A:A1:D8
:94:46:A6:73:AB:C5:ED:8D',
ext_key_usage: [Array],
serialNumber: '03DBC9293BDB3B4B4970C3DC3158B8225A0B',
raw: <Buffer 30 82 03 bc 30 82 03 42 a0 03 02 01 02 02 12 03 db c9 29 3b db 3b 4b 49 70 c
3 dc 31 58 b8 22 5a 0b 30 0a 06 08 2a 86 48 ce 3d 04 03 03 30 32 31 0b 30 ... 910 more bytes>,
issuerCertificate: [Object]
}
}
}
[TAUTULLI] - No user ID found!
[TAUTULLI] - No user ID found!
Platform
desktop
Device
All
Operating System
UnRAID 7
Browser and version
All
Additional context
No response
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
if i refresh the 404 page, I am redirected to the login page, with the message Setup needs to be done by the admin and i can't do anything else.
This probably has to do with the current initial setup process being rather finicky.. I will try to improve upon this in upcoming releases.
:tada: This issue has been resolved in version 4.8.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: