Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Installation Help]: Documentation update TubeArchivist URL #29

Open
1 task done
jfroebe opened this issue Nov 27, 2023 · 2 comments
Open
1 task done

[Installation Help]: Documentation update TubeArchivist URL #29

jfroebe opened this issue Nov 27, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@jfroebe
Copy link

jfroebe commented Nov 27, 2023

Installation instructions

  • I'm running the latest version of the TubeArchivist Plex Integration Scanner and Agent. I have read the latest release notes and installation instructions.

Operating System

Linux Container

Your installation or setup question

update install documentation

The TubeArchivist URL needs to include the port number else the plugin will attempt to connect to port 80

cat ta_config.json
{
"ta_url": "http://tube-archivist.local:8000",
"ta_api_key": "....."
}

Note: If Plex is installed in a container, you may need to specify the host to ip address to the docker run line:

--add-host "tube-archivist.local:192.168.68.4"

see "extra_hosts" for docker composer.

Relevant log output

2023-11-27 10:15:22,356 [TubeArchivist Scanner] INFO - Attempting to connect to TubeArchivist at http://tube-archivist.local with provided token from `ta_config.json` file.
2023-11-27 10:15:22,374 [TubeArchivist Scanner] ERROR - Error connecting to TubeArchivist with URL 'http://tube-archivist.local', Exception: 'No JSON object could be decoded'

^^ the plugin was connecting to port 80 (Unraid in my case).  Specifying the port # of TubeArchive resolved the issue
@lamusmaser
Copy link
Collaborator

It will connect using standard port if not supplied, so 80 for HTTP, 443 for HTTPS. Documentation can be updated to reflect this.

If someone else can get to this, that would be appreciated. Otherwise, it'll be a while before I have available resources to make the updates required.

@lamusmaser lamusmaser added documentation Improvements or additions to documentation good first issue Good for newcomers labels Dec 13, 2023
@lamusmaser
Copy link
Collaborator

Missed doing this when I was handling the updates for v0.1.6, so I'll ensure it gets included with a future update that incorporates the README fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants