bogenpirat / remote-torrent-adder

A handy Chrome extension to add torrent files to torrent clients
237 stars 80 forks source link

Torrents not being added to ruTorrent again #286

Closed GorillaJohnson closed 4 years ago

GorillaJohnson commented 4 years ago

hi, same issue as here https://github.com/bogenpirat/remote-torrent-adder/issues/278

Seem to be fixed but has started happening again 3 days agp.

Anyone else having the problem?

Thanks

bogenpirat commented 4 years ago

there were a lot of different things being reported in that issue. please supply some more information about your exact setup and the nature of your problem, or link to a specific comment.

at the very least, you should add information about:

GorillaJohnson commented 4 years ago

apologies. rutorrent, chrome and this error message pops up

Failure could not contact feralhosting.com Error: Unauthorized

i went to the link on chrome you posted all seemed fine. i'm not really sure were i should be looking

bogenpirat commented 4 years ago

unauthorized means that the server didn't accept the credentials. => obviously, check your login credentials.

if that doesn't solve it, back to the devtools window. go to the network tab, leave it open and try to add a torrent in another tab, go back to the devtools window and you should have an entry there that points to rutorrent's "addtorrent.php". click on it, a newly-opened right pane should show some details about the request. under the "headers" tab, under response headers, is there a WWW-Authenticate header? if not, under request headers, is there an Authorization header? is the first word of it Basic or Digest?

GorillaJohnson commented 4 years ago

I'm signed into rutorrent and my seedbox no problem.

I'm a novice with this. are these the"devtools" you mention? developers.google.com/web/tools/chrome-devtools/open

if so i clicked network on the left and had 3 options "get started" "network issues guide" "Reference"

bogenpirat commented 4 years ago

sorry, i was referring to my earlier post:

whether there are any error messages in the background page of RTA in the devtools (see chrome://extensions/?id=oabphaconndgibllomdcjbfdghcmenci)

you enter the chrome://-url into your address bar and click on this link: image that should present you with a new pane or window in your browser that contains the "chrome devtools". when you have those open, follow the aforementioned instructions. that may help shed some light on what's going wrong.

GorillaJohnson commented 4 years ago

is this where i should be looking https://imgur.com/6tvkEMe

i went to chrome://extensions/?id=oabphaconndgibllomdcjbfdghcmenci

Below that is https://imgur.com/a/WgdwoQp

When i click "Extension options" https://imgur.com/a/eBUXtDS

bjmomo commented 4 years ago

I am having this issue too, also with feralhosting. chrome, rutorrent.

under the addtorrent.php-->response headers in DevTools, there is this: WWW-Authenticate: Basic realm="[myusername]" under request headers there is no Authorization header

bogenpirat commented 4 years ago

@GorillaJohnson your first screenshot is the correct function of chrome (on the right side of the screen), however it is opened from the wrong place - the extensions overview screen of chrome instead of from within the context of the RTA extension. in order to see the link i screencapped in my last post, you may need to turn on the "developer mode" in the top right of the extensions overview screen. you can then view errors in the console tab that is visible on your first screenshot at the bottom of the right pane (dismiss "what's new").

your config doesn't have a port set. try setting one. do you use http or https? that would be 80 or 443, respectively.

@bjmomo you wouldn't happen to also have a missing port setting? if not, any errors under console? in your case, it seems that a WWW-Authenticate-challenge wasn't answered. this might be the case when the request handler that deals with supplying credentials in the background didn't register to the correct URL.

bjmomo commented 4 years ago

thank you! adding port 80 fixed the issue. 👍

GorillaJohnson commented 4 years ago

same fix as above. big thanks