-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
Trakt.tv API connection - Slim Application Error #1872
Comments
can you ping api.trakt.tv from inside the container? |
This gives me: |
that is correct. seems you have a network issue somewhere.
…Sent from my iPhone
On Aug 2, 2022, at 3:47 PM, ralothar ***@***.***> wrote:
docker exec -ti organizr ping api.trakt.tv would be the right command I believe, right?
This gives me: ping: bad address 'api.trakt.tv'
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Alright I guess then I will have to narrow it down. Since I can ping api.trakt.tv from windows command I guess it shouldn't be a router-firewall problem. Does organizr need another open port apart of the regular one? Lets say I can access organizr through port 8285, would the connection to trakt-api need a different one? |
No you don’t need another port. I would suggest searching something along the lines of docker synology network issues.
…Sent from my iPhone
On Aug 2, 2022, at 4:03 PM, ralothar ***@***.***> wrote:
Alright I guess then I will have to narrow it down. Since I can ping api.trakt.tv from windows command I guess it shouldn't be a router-firewall problem.
Does organizr need another open port apart of the regular one? Lets say I can access organizr through port 8285, would the connection to trakt-api need a different one?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
I see. Well turning off the built in synology-firewall for testing purposes seemed to make it work. So I guess something is blocking that connection. I know it might be a far fetch but do you have an idea what it might be? I've enabled forwarding all connections as well as allowing all protocols on organizrs port and still no luck |
So as it turns out the way the Synologys Firewall is different to what I am used to. I had to manually allow the subnet, the container bridge was bound to, to bypass the firewall. Now I can ping api.trakt.tv through terminal command
Unfortunatley I still get this error when trying to connect to Trakt:
|
try the latest dev release |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Organizr Version: V 2.1.2330
Branch: Master
WebServer: Nginx (I think)
Operating System: Synology DSM (Linux based) (Docker)
Problem Description:
When I try to connect Organizr to the Trakt.tv API, following the recommended steps, I get a
Slim Application Error
code and can't continue.I've tried tinkering around with different adresses, different browsers, users, deleting cookies and get this result either way.
Since I had no problem with the trakt API up until now and didn't find a solution to my problem here on Github nor on Reddit, I would like to ask for help.
Reproduction Steps:
https://organizr.mydomain.com/api/v2/oauth/trakt
as well as192.XXX.X.XX:Port/api/v2/oauth/trakt
Allow New Organizr Integration to use your account?
Errors on screen? If so paste here:
The text was updated successfully, but these errors were encountered: