search

RandomNinjaAtk / docker-lidarr-extended

lidarr-extended :: Lidarr application packaged with multiple scripts to provide additional functionality
GNU General Public License v3.0
276 stars 24 forks source link

[Bug]: can't hit api at http://lidarrIP:8686/api?apikey=XXXX #188

Closed captainnapalm closed 1 year ago

captainnapalm commented 1 year ago

Describe the bug Attempting to hit the api to confirm version at http://lidarrIP:8686/api?apikey=XXXX returns a 404 instead of the expected json output of something like: 

{
    "current": "v1",
    "deprecated": []
}

I attempted to use the lidarr.audio v1.0 api docs page to test (https://lidarr.audio/docs/api/#/), but received a TyperError: NetworkError when attempting to fetch resource. I am however able to receive an output for something like http://lidarrIP:8686/api/v1/system/status?apikey=XXXX (https://lidarr.audio/docs/api/#/System/get_api_v1_system_status).

This was all brought on by attempting to run lidarr-true-singles and the api check failing.

To Reproduce Steps to reproduce the behavior:

  1. Navigate in browser to http://lidarrIP:8686/api?apikey=XXXX
  2. Receive lidarr's 404 page

Expected behavior Expected output is json as formatted above

Log Data Imgur

Docker Info:

RandomNinjaAtk commented 1 year ago

Seems like your having a general lidarr issue, I only support the packaged/included scripts. The scripts do everything via API calls, so the API is definitely functioning as expected. So your issue, might be something related to your specific configuration or something wrong with that other project....

Lidarr API examples from script: https://github.com/RandomNinjaAtk/docker-lidarr-extended/blob/00421aa29739d0c3469bdbf66c274914efa4263a/root/scripts/Audio.sh#L783

https://github.com/RandomNinjaAtk/docker-lidarr-extended/blob/00421aa29739d0c3469bdbf66c274914efa4263a/root/scripts/Audio.sh#L55

https://github.com/RandomNinjaAtk/docker-lidarr-extended/blob/00421aa29739d0c3469bdbf66c274914efa4263a/root/scripts/Audio.sh#L965

You may want to ask the author of the other docker for help...

Feel free to open a discussion, but this is not a bug and likely a usage issue...