Replies: 1 comment
-
It seems to me this issue is just when trying to use Postman, when I use Panoscrobble things work. So I guess nevermind. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey before I dig too far into this, when try to call any of the API implementations I get
This happens when I do a POST (using postman within my network). To any of the following
http://192.168.1.7:42010/apis/audioscrobbler_legacy
http://192.168.1.7:42010/apis/audioscrobbler
http://192.168.1.7:42010/apis/listenbrainz
I should get a different response than just invalid API, right?
I can browse to /api_explorer perfect fine in my browser.
I can get an different response going to http://192.168.1.7:42010/apis/mlj_1/newscrobble which makes me think that API is functional
Lastly if I do a POST with http://192.168.1.7:42010/apis/mlj_1/newscrobble?key=APIKEY
I get the response I would expect to get when I call the other APIs.
Where can I look to see why this is failing with access to the other APIs?
Beta Was this translation helpful? Give feedback.
All reactions