plexrequests-meteor
plexrequests-meteor copied to clipboard
lokenx
unable to connect with couchpotato on dediseedbox
I've been trying to connect up to couchpotato and it just says error. When I goto logs, there really is no info there...I tried doing an api call via my web browser (chrome) and that seems to work so I don't understand what I'm doing wrong...been searching forums for hours and haven't found anything helpful
Did you save the settings before trying to test? You have to enter the details and save them first before you can run the connection test.
Lol yes. Did that like 600 times plus restarts of the app and such...sickrage had the same issue too
On Tue, Apr 24, 2018, 16:26 Ricky Grassmuck [email protected] wrote:
Did you save the settings before trying to test? You have to enter the details and save them first before you can run the connection test.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384099572, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak2GNzEJ8-vtgIYTgUto8EcdCXaW8wuYks5tr6aBgaJpZM4TfB1G .
It sounds like a networking issue within docker causing Plex requests to not be able to reach the applications. Have you tried using the IP address instead of the domain name for the server URL?
On Tue, Apr 24, 2018, 6:09 PM gswscreagle [email protected] wrote:
Lol yes. Did that like 600 times plus restarts of the app and such...sickrage had the same issue too
On Tue, Apr 24, 2018, 16:26 Ricky Grassmuck [email protected] wrote:
Did you save the settings before trying to test? You have to enter the details and save them first before you can run the connection test.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384099572 , or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak2GNzEJ8-vtgIYTgUto8EcdCXaW8wuYks5tr6aBgaJpZM4TfB1G
.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384108324, or mute the thread https://github.com/notifications/unsubscribe-auth/AQbPDdpq7dj_dxk8-xw5V7wOpyPkcC9fks5tr7CfgaJpZM4TfB1G .
Yeah the IP had the same issues
On Wed, Apr 25, 2018, 17:31 Ricky Grassmuck [email protected] wrote:
It sounds like a networking issue within docker causing Plex requests to not be able to reach the applications. Have you tried using the IP address instead of the domain name for the server URL?
On Tue, Apr 24, 2018, 6:09 PM gswscreagle [email protected] wrote:
Lol yes. Did that like 600 times plus restarts of the app and such...sickrage had the same issue too
On Tue, Apr 24, 2018, 16:26 Ricky Grassmuck [email protected] wrote:
Did you save the settings before trying to test? You have to enter the details and save them first before you can run the connection test.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <
https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384099572
, or mute the thread <
https://github.com/notifications/unsubscribe-auth/Ak2GNzEJ8-vtgIYTgUto8EcdCXaW8wuYks5tr6aBgaJpZM4TfB1G
.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub < https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384108324 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AQbPDdpq7dj_dxk8-xw5V7wOpyPkcC9fks5tr7CfgaJpZM4TfB1G
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384465725, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak2GN4MExnOrpghciw30Mrrcwx1jJL6Gks5tsQdngaJpZM4TfB1G .
Can you connect to those services from the same box docker is running on?
Something like...
curl -IL http://<host>:port/
Running something like that outside of docker (but on the same server docker is running on) should tell if it's a network issue and or not.
On Wed, Apr 25, 2018, 8:24 PM gswscreagle [email protected] wrote:
Yeah the IP had the same issues
On Wed, Apr 25, 2018, 17:31 Ricky Grassmuck [email protected] wrote:
It sounds like a networking issue within docker causing Plex requests to not be able to reach the applications. Have you tried using the IP address instead of the domain name for the server URL?
On Tue, Apr 24, 2018, 6:09 PM gswscreagle [email protected] wrote:
Lol yes. Did that like 600 times plus restarts of the app and such...sickrage had the same issue too
On Tue, Apr 24, 2018, 16:26 Ricky Grassmuck [email protected] wrote:
Did you save the settings before trying to test? You have to enter the details and save them first before you can run the connection test.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <
https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384099572
, or mute the thread <
https://github.com/notifications/unsubscribe-auth/Ak2GNzEJ8-vtgIYTgUto8EcdCXaW8wuYks5tr6aBgaJpZM4TfB1G
.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub <
https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384108324
, or mute the thread <
https://github.com/notifications/unsubscribe-auth/AQbPDdpq7dj_dxk8-xw5V7wOpyPkcC9fks5tr7CfgaJpZM4TfB1G
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384465725 , or mute the thread < https://github.com/notifications/unsubscribe-auth/Ak2GN4MExnOrpghciw30Mrrcwx1jJL6Gks5tsQdngaJpZM4TfB1G
.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384483246, or mute the thread https://github.com/notifications/unsubscribe-auth/AQbPDf1tFvc-BPJo62jFBHiE0Z1Coujqks5tsSHigaJpZM4TfB1G .
I don't have should access to it.itsca seedbox on dediseedbox..Plex, couch potato, sick rage, headphones, jackett, and rutorrent all seem to talk to each other fine. Plex request is the first item I've had issues with. I was able to get Plex request to talk to Plex...
On Apr 25, 2018 20:10, "Ricky Grassmuck" [email protected] wrote:
Can you connect to those services from the same box docker is running on?
Something like...
curl -IL http://<host>:port/
Running something like that outside of docker (but on the same server docker is running on) should tell if it's a network issue and or not.
On Wed, Apr 25, 2018, 8:24 PM gswscreagle [email protected] wrote:
Yeah the IP had the same issues
On Wed, Apr 25, 2018, 17:31 Ricky Grassmuck [email protected] wrote:
It sounds like a networking issue within docker causing Plex requests to not be able to reach the applications. Have you tried using the IP address instead of the domain name for the server URL?
On Tue, Apr 24, 2018, 6:09 PM gswscreagle [email protected] wrote:
Lol yes. Did that like 600 times plus restarts of the app and such...sickrage had the same issue too
On Tue, Apr 24, 2018, 16:26 Ricky Grassmuck [email protected] wrote:
Did you save the settings before trying to test? You have to enter the details and save them first before you can run the connection test.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <
https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384099572
, or mute the thread <
https://github.com/notifications/unsubscribe-auth/Ak2GNzEJ8-vtgIYTgUto8EcdCXaW8wuYks5tr6aBgaJpZM4TfB1G
.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub <
https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384108324
, or mute the thread <
https://github.com/notifications/unsubscribe-auth/AQbPDdpq7dj_dxk8-xw5V7wOpyPkcC9fks5tr7CfgaJpZM4TfB1G
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <
https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384465725
, or mute the thread <
https://github.com/notifications/unsubscribe-auth/Ak2GN4MExnOrpghciw30Mrrcwx1jJL6Gks5tsQdngaJpZM4TfB1G
.
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub < https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384483246 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AQbPDf1tFvc-BPJo62jFBHiE0Z1Coujqks5tsSHigaJpZM4TfB1G
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-384490154, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak2GN4OabMVezVXiF0dJJgaBpoLNQ2Fgks5tsSyTgaJpZM4TfB1G .
I just noticed you have "/api/" set as the couchpotato subdirectory. This is likely the issue unless you actually access the couchpotato interface using a URL like the one below.
http://my.dediseedbox.com:25374/api/
That box is for when you have a proxy setup and use a directory to determine which application a request is going to.
Plexrequests will handle building the URL for the API calls automatically and just needs the information needed to connect to the service itself. Try removing the "/api/" and saving the settings and it will likely work.
I tried without originally...doesn't work either way
On Fri, Apr 27, 2018, 20:33 Ricky Grassmuck [email protected] wrote:
I just noticed you have "/api/" set as the couchpotato subdirectory. This is likely the issue unless you actually access the couchpotato interface using a URL like the one below.
http://my.dediseedbox.com:25374/api/
That box is for when you have a proxy setup and use a directory to determine which application a request is going to.
Plexrequests will handle building the URL for the API calls automatically and just needs the information needed to connect to the service itself. Try removing the "/api/" and saving the settings and it will likely work.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-385133506, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak2GN1xE9z8D1DKnTqSgpUbJyMjjlr3Kks5ts9TxgaJpZM4TfB1G .
You may need to get in touch with dediseed and see if they can provide you with any console output. It looks like we still have the errors from that method being sent to the console(moving everything to using the logging module is a WIP) so without access to that we won't know exactly what the error is.
With that said, all we are doing for that test is sending a request like the one below and looking for the success key in the response.
http://couchpotato.domain.com/api/<API_KEY>/app.available
That should respond with something like(don't remember off the top of my head the exact structure but it would at least have the contents below):
{success: true}
You can try to run that example and see what it is reporting back but if it's something with the application (I'm assuming they likely use docker) then we won't be able to tell without console output that is being generated by the error.
tried it out and it came back ok....
On Fri, Apr 27, 2018 at 8:55 PM, Ricky Grassmuck [email protected] wrote:
You may need to get in touch with dediseed and see if they can provide you with any console output. It looks like we still have the errors from that method being sent to the console(moving everything to using the logging module is a WIP) so without access to that we won't know exactly what the error is.
With that said, all we are doing for that test is sending a request like the one below and looking for the success key in the response.
http://couchpotato.domain.com/api/<API_KEY>/app.available
That should respond with something like(don't remember off the top of my head the exact structure but it would at least have the contents below):
{success: true}
You can try to run that example and see what it is reporting back but if it's something with the application (I'm assuming they likely use docker) then we won't be able to tell without console output that is being generated by the error.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lokenx/plexrequests-meteor/issues/535#issuecomment-385134839, or mute the thread https://github.com/notifications/unsubscribe-auth/Ak2GNxIdorULfAPj0mFgkRHuamlPFX9Wks5ts9o_gaJpZM4TfB1G .
See my comment on this issue. Haven't forgot about ya, just need to make some major changes to help with the debugging process for these issues. Hoping to have a new release pushed out this week to address a large bit of tech debt that has accumulated.
https://github.com/lokenx/plexrequests-meteor/issues/538#issuecomment-387687549