-
Notifications
You must be signed in to change notification settings - Fork 22
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
API endpoint Issue #93
Comments
new logs that i think shows more stuff
|
Sorry for the late reply, I am away from my dev PC. Hopefully I can sort out your problem without it.
You should see a The URL that is generated is not always correct, especially if the Jellyfin installation is not on bare metal or VM. |
Thank you for your reply, and no worries :). No i connect to jellyfin using http://10.0.0.5:8096/ as i am using it inside of UnraidOS and for some reason it has "192.168.0.9" as "JELLYFIN_PublishedServerUrl:" but it never worked for me and it has "172.17.0.3" as "AniSYNC:" variable. Edit: |
I haven't used UnraidOS before so I might not be able to help much, but do you get a response of |
Yes i get this message "This is the correct URL.", in that case shouldnt i be able to authenticate? or is it bugged? |
I would have thought it would work. Does this suggestion help you at all? It sounds like they may have a similar environment to you. Unfortunately as I run my environment in a VM on proxmox I can't provider much help for your use case. |
it did not work for initial testing but i have to do some more fiddling to see if it does. |
You can try checking if there's an extra space in front of the client ID and client secret. I was having issues authenticating, but after I noticed and removed the extra spaces, everything worked. Side note: I was getting a |
I had the same @ForsakenTwilight problem. What I found is 2 problems, one of configuration on my part and another in the authentication procedure in the plugin also on my part:
I had configured well the Note 1.The IP is not real, it is an example.
After correctly configuring the API in my MAL account, you have to go to the plugin configuration, fill in the required fields according to the guide and finally click on the "Authorize User" button. This will generate a URL, which must be pasted into a new tab to allow the local JellyFin user to use the App we created in MAL. |
I was following the guide to setup API endpoint, but it seems to have an issue for some reason, Please see this screenshot of my jellyfin server API endpoint: https://i.imgur.com/XP7lK73.png
I believe I set it up correct, now what happens is if i try to test it as the guide suggests using (http://172.17.0.3:8096)
I'll get the usual "can't reach this page" error when testing with http://172.17.0.3:8096/AniSync/apiUrlTest
I have also created MAL api ID and secret, but when i try to test the authentication it also fails, which is how i know my API endpoint is not working.
Any help would be appreciated
Logs
Please let me know if these logs are enough or if i should recreate the issue again
To Reproduce
Steps to reproduce the behavior:
-use api endpoint http://172.17.0.3:8096
-test with "url/AniSync/apiUrlTest"
Expected behavior
it should show a message as the guide suggests
Screenshots
https://i.imgur.com/ZOfKaLd.png
https://i.imgur.com/XP7lK73.png
Desktop (please complete the following information):
Additional context
I am using this in my UnraidOS server
The text was updated successfully, but these errors were encountered: