Able to get API key, but connection test fails, no errors logged

[FoxBJK]

I'm trying to set up this app for the first time, but it's not getting past the "test" portion. The app has no problem connecting to my server to get the API key by itself, but when hitting the "test" button I get a message that says "Connection to failed". The address is right, the port number is right, the API key is right. I don't understand why there's an error.

Nothing is logged on my SickRage server. The phone is a Nexus 5 running 6.0.1, and v.1.3 of the app

[But4ler]

Exactly the same problem on the same phone (first time too)
Phone Nexus 5
Android 6.0.1
App: v1.3

[MGaetan89]

It seems there is an issue in the connection process, but I didn't find it yet.
When the test fails, the URL is displayed in the error message. Does this URL look correct to you? What happens if you enter it in a web browser?

[But4ler]

In sickrage, if I active authentication:

• In the application, I entered, the IP, port, user password
  • The recovery of API key does not work
    App message: connecting to http://myip:port/apikey impossible
    The log message from the server:
    2016-01-01 10:05:06 p.m. TORNADO WARNING :: :: User Attempted has failed login to the web interface from IP SiCKRAGE: myip

If I disable authentication:
The application recovers well the API key and connecion works, but I do not have access to any information about the server (log OK)

[FoxBJK]

On both desktop and mobile, the full API url that the app shows me works just fine. I've proof-read it as much as I can, and it appears to be correct. I've cycled the API key a couple of times to be sure, and at one point used the IP address instead of the hostname to pull up my SickRage install.

If there's some way I can produce logs for this, I'll be happy to.

[MGaetan89]

Thanks for the information. I will look into this issue and let you know when it is fixed or if I need more information.

[FoxBJK]

I figured out the problem; the app doesn't pay attention to custom ports. I was running SickRage on 8083 before, but I went ahead and switched back to 8081, and now the app works just fine.

Not going to close this, because I'd like to be able to run SR over a custom port, but for now I'll use the default.

Thanks!

[MGaetan89]

That's weird, because I am using 8083 and it is working fine for me. I'll do more testing to check this.

@But4ler are you using a custom port? If so, are you able to change to the default port to see if it fixes the issue for you too?

[tinywiz]

@MGaetan89 I have the same problem on Galaxy S6 5.1.1

Using port 8083 gives connection fail, switching to port 8081 solves it for me.

[MGaetan89]

In the error message, does it display the correct port (8083)? That would mean that ShowsRage is trying to use the correct port.
Maybe your router is blocking this port?

[tinywiz]

@MGaetan89

Hi again.

After som more port changing (ex. port 8000 also working) I tried to go back to port 8083 when SickRage (on NAS) stopped responding at all. I restarted the Synology NAS (on which I have SickRage) and bam, 8083 works. Any other port also works, but if I change the port to often, say 3 times, in sickrage and try to restart it will die (ex stop responding even if it says it is running on the NAS).

I have no clue on if this is a Synology problem or SickRage on the NAS problem. But restarting the NAS seems to fix the problem for me.

Update: All test done on LAN.

[FoxBJK]

Well, if it helps, I'm also using a Synology NAS. Still using port 8081, and everything's working fine

[monk-blade]

Same problem. Changed port vice versa. No solution. Browser gives following thing.
{"message": "", "data": "No such cmd: ''", "result": "error"}

[monk-blade]

Sickrage log :
2016-11-26 07:28:07 API :: 'Core' object has no attribute 'STARTED'

[monk-blade]

Oh... app is working but give failed connection. Changed to other port. In short, Test fails but app is working fine.

[monk-blade]

Ohh..it gives new errors.
2016-11-26 07:40:12 API :: 'int' object has no attribute 'getitem'
2016-11-26 07:40:07 API :: 'int' object has no attribute 'getitem

[MGaetan89]

That's interesting.
Can you tell me which fork of SickRage you are using? And also which version?

[monk-blade]

https://github.com/SiCKRAGETV/SiCKRAGE
SR version from info page : e294e587103020f3697b0493a8656454c9998f9d

[MGaetan89]

Thanks. I'm using SickRage/SickRage, so maybe there is a difference in the API of both forks.
I will install your fork to see what happens.
If it is easy to fix, I will do it in the next version (1.6). Otherwise it will be in the following one (2.0), where I plan on improving/providing support for multiple forks.

@FoxBJK, @But4ler, @tinywiz: can you tell me which fork you use, so I can check them as well?

[monk-blade]

Okay. If I get free time, I will try to check your version.

[monk-blade]

Tested your version. Its version related problem. Huh...At last, problem solved. Try to mention in README or Google play store info so that user wont end up in problem like I did.

[MGaetan89]

Thanks for checking this.
I'll do some tests on my side too, to see if I can fix it in ShowsRage.
Otherwise I'll add a note about this issue, as you suggested.