Options not showing when using reverse proxy about chrome-transmission-remote-plus HOT 9 OPEN

Hi, when on the options page can you open the javascript console (View > Developer > JavaScript console) and see if there is any errors? if so paste them here

from chrome-transmission-remote-plus.

Yup

jquery-3.2.1.min.js:2 jQuery.Deferred exception: Cannot read property '1' of null TypeError: Cannot read property '1' of null
at HTMLDocument. (chrome-extension://kfbocdnicmioodheiciijiegbmfoliim/js/options.js:201:28)
at j (chrome-extension://kfbocdnicmioodheiciijiegbmfoliim/js/jquery-3.2.1.min.js:2:29999)
at k (chrome-extension://kfbocdnicmioodheiciijiegbmfoliim/js/jquery-3.2.1.min.js:2:30313) undefined
r.Deferred.exceptionHook @ jquery-3.2.1.min.js:2
jquery-3.2.1.min.js:2 Uncaught TypeError: Cannot read property '1' of null
at HTMLDocument. (options.js:201)
at j (jquery-3.2.1.min.js:2)
at k (jquery-3.2.1.min.js:2)

from chrome-transmission-remote-plus.

Looking at the code https://github.com/YodaDaCoda/chrome-transmission-remote-plus/blob/master/source/js/options.js#L201 i would guess it means that URL does not match the regex. Do you have any strange characters etc in the URL?

If you have problem changing it now you can probably change it by using localStorage.server = "..." in the javascript console on the options page and reload the page.

from chrome-transmission-remote-plus.

Hey,

well that part is fixed, the options now show properly and I can edit them. Now the issue is the opposite, the options are right but the connection in itself doesnt work. So:

http://ip:someport/transmission (with login, password, rpc and web path correctly configured) works
https://someaddress:443/transmission (same) doesnt

any way I could get this to work? What may be the issue?

Thanks!

from chrome-transmission-remote-plus.

Hmm not sure, maybe check the network tab in developer console and check for failing requests?

from chrome-transmission-remote-plus.

Yup, Failed to load resource: the server responded with a status of 409 ()

from chrome-transmission-remote-plus.

It may have something to do with this:

409: Conflict
Your request had an invalid session-id header.

To fix this, follow these steps:

When reading a response, get its X-Transmission-Session-Id header and remember it
Add the updated header to your outgoing requests
When you get this 409 error message, resend your request with the updated header

from chrome-transmission-remote-plus.

There is a 409 response? I think is already should be handling the session id header thing. It seems to work fine for me at least. I wonder if the URL ends up wrong i some way so it ends up talking to something else etc

from chrome-transmission-remote-plus.

Could be, any way that I could check that?

from chrome-transmission-remote-plus.