mirror of
https://github.com/tubearchivist/tubearchivist-plex.git
synced 2026-03-23 20:37:11 +00:00
[GH-ISSUE #25] [Installation Help]: Scans but no metadata/images #5
Labels
No labels
bug
bug
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tubearchivist/archived-tubearchivist-plex#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zudiguy on GitHub (Oct 24, 2023).
Original GitHub issue: https://github.com/tubearchivist/tubearchivist-plex/issues/25
Installation instructions
Operating System
Docker/linux
Your installation or setup question
Having problems with getting metadata and images to show - I've tried everything ta host from https:/tubearchivist.mydomain.com & docker Ip address. This is my 3rd server I tried this on. The server currently is running traefik & authelia not sure if that will cause a conflict
Relevant log output
@lamusmaser commented on GitHub (Oct 24, 2023):
From the
Managed Library>Edit...>Advanced, what do you have configured forTubeArchivist URL?@zudiguy commented on GitHub (Oct 24, 2023):
https://tubearchivist.mydomain.com
@lamusmaser commented on GitHub (Oct 24, 2023):
OK, and if you attempt to go to that address normally, does it pull up as expected? Additionally, if you attempt to connect via the API, does that direct connect or is there an intermediary response that comes through before that point?
@zudiguy commented on GitHub (Oct 24, 2023):
Yes, when I go to domain it connects. Not sure what you mean connect via api
@lamusmaser commented on GitHub (Oct 24, 2023):
We have details via the docs. I would start with a login request, then a ping request. If you need more specific guidance, please let us know.
@zudiguy commented on GitHub (Oct 24, 2023):
@lamusmaser commented on GitHub (Oct 24, 2023):
OK, so the connections are coming through and they don't seem to have problems with an intermediary. From the system that is running Plex, can it reach the tubearchivist API?
@zudiguy commented on GitHub (Oct 24, 2023):
/api/login/ returns
@lamusmaser commented on GitHub (Oct 24, 2023):
The login is a POST request.
@zudiguy commented on GitHub (Oct 24, 2023):
This what happens when ran in a another browser
@zudiguy commented on GitHub (Oct 24, 2023):
{"detail":"Method "GET" not allowed."}
@lamusmaser commented on GitHub (Oct 24, 2023):
Right, so you have to be authenticated and pass the authentication token with the ping request's header. If you can run a
curlor programmatic approach to the API request from the Plex server's system to the TA endpoint, that should help us understand what is happening with the request. Based on what I am seeing, I would assume that the API key is probably not correct, since I am seeing a Response 200 with 401 in between.@zudiguy commented on GitHub (Oct 24, 2023):
I think Authelia is causing problems.
@lamusmaser commented on GitHub (Oct 24, 2023):
It is possible. I don't have Authelia setup, so I can't test its integration limitations.
Ultimately, what is being looked for is:
The TubeArchivist endpoint at the designated URL.
The API key from TubeArchivist that allows access.
That should return a response that verifies that the connection can be made.
If that doesn't work as expected, then it can cause issues. If Authelia is standing in between any of those steps and not passing it properly to the endpoint, then we might have a problem.
@zudiguy commented on GitHub (Oct 24, 2023):
That was it I had had to setup a bypass for tubearchivist
@zudiguy commented on GitHub (Oct 24, 2023):
Thanks for your help