cant dl from dognzb - Githubissues

tomrip commented 10 years ago

i have verified the API is correct, but this is all it shows in log 2014-06-10 21:41:11 ERROR Unable to connect to remote host. 2014-06-10 21:41:11 INFO Parsing results from https://api.dognzb.cr

AdeHub commented 10 years ago

Tried http://api.dognzb.cr/ ?

basilfx commented 10 years ago

Can you ping it? If not, do you run any peer blockers?

It works for me though.

tomrip commented 10 years ago

i cannot ping it, is this the correct address? https://api.dognzb.cr

C:\Users\tom>ping https://api.dognzb.cr Ping request could not find host https://api.dognzb.cr. Please check the name an d try again.

C:\Users\tom>ping http://api.dognzb.cr Ping request could not find host http://api.dognzb.cr. Please check the name and try again.

C:\Users\tom>ping https://api.dognzb.cr Ping request could not find host https://api.dognzb.cr. Please check the name an d try again.

C:\Users\tom>

On Wed, Jun 11, 2014 at 7:09 AM, Bas Stottelaar notifications@github.com wrote:

Can you ping it? If not, do you run any peer blockers?

It works for me though.

— Reply to this email directly or view it on GitHub https://github.com/rembo10/headphones/issues/1708#issuecomment-45728214.

basilfx commented 10 years ago

You could also go to https://api.dognzb.cr/ in your browser. It's reachable for me.

tomrip commented 10 years ago

HTTP 403 - FORBIDDEN ACCESSYou do not have access to the area you requested. It is also possible you typed the address incorrectly, the page no longer exist or is temporarily unavailable.

If this warning continues and you believe it is being displayed in error, please contact the owner of the webpage with details on how to duplicate this event.

On Wed, Jun 11, 2014 at 8:29 AM, Bas Stottelaar notifications@github.com wrote:

You could also go to https://api.dognzb.cr/ in your browser. It's reachable for me.

— Reply to this email directly or view it on GitHub https://github.com/rembo10/headphones/issues/1708#issuecomment-45734375.

basilfx commented 10 years ago

Yes, that is correct and to be expected. This means you can reach the remote host (e.g. your computer can successfully connect to the remote host). However, this also means that Headphones should be able to connect to the remote host (if not, it returns the Unable to connect to remote host error). Maybe there was a connection error last time?

I assume you run Headphones on the same computer (and network) as where you tried to reach the remote host from within your browser?

tomrip commented 10 years ago

No. I have a media server that has headphones and sickbeard installed. I used another computer to test and it worked. since I have port forwarded everything at my job I can type in my public ip and then port of sabnzb, sickbeard and it comes up. Headphones does not. I have nzb360 for my cellphone and it loads everything but headphones. On Jun 11, 2014 8:58 AM, "Bas Stottelaar" notifications@github.com wrote:

Yes, that is correct and to be expected. This means you can reach the remote host (e.g. your computer can successfully connect to the remote host). However, this also means that Headphones should be able to connect to the remote host (if not, it returns Unable to connect to remote host). Maybe there was a connection error last time?

I assume you run Headphones on the same computer (and network) as where you tried to reach the remote host from within your browser?

— Reply to this email directly or view it on GitHub https://github.com/rembo10/headphones/issues/1708#issuecomment-45737160.

basilfx commented 10 years ago

Sorry, but I think you are mixing up #1709 with this issue. Please don't do that.

Redo the steps I provided on the same machine as where you run Headphones on. If you cannot reach it from the browser/commandline on that machine, it is not Headphones related -- your machine or network probably blocks traffic to that remote host (and therefore, Headphones cannot connect to it, just like the error message suggests).

tomrip commented 10 years ago

i posted that i could not ping or got to the url, and this sis the response from dognzb

tomrip commented 10 years ago

Ping are blocked by our Firewall. Opening the URL with no parameters, will return a 403 error.

Both responses are normal.

basilfx commented 10 years ago

I'll summarize one last time. I am only trying to help you locate the issue, but I get the feeling you don't understand (or read) my replies. This is not a general help forum, and some knowledge and input is expected.

You submit an issue regarding an Unable to connect to remote host. error.
I state that Headphones cannot connect to the remote host. Something blocks a connection (peerblocker, firewall, or maybe the host is down). I ask you to ping it, or to visit the URL Headphones tries to connect to.
You do so, telling it returns a 403 error via the browser.
I tell you, that it is the same I see, and is to be expected and CORRECT. Your browser can connect to the remote host, so Headphones should be able to do the same. To make sure, I ask you if you did this on the same machine you run Headphones on.
You say no no
I say, please try on the same machine. If you can reach the remote host on the SAME machine via terminal as Headphones runs on, it is NOT headphones related.

tomrip commented 10 years ago

I guess i am confuses. reading back, i need to switch my answer to yes, it is on the same network. i believe this is an issue with dognzb, as it is not working non my nzb360 for my phone either for search. they keep saying its headphones. So when i post the 403 error, you say it is expected. This means, that that is what we want to see?

basilfx commented 10 years ago

Your connection with nzb360 is another issue.

Even though dognzb return a 403 from your browser, it still means that it can connect with dognzb. In other words, your computer can talk with the remote computer of dognzbd. So even though it responds with a 403, it means it can connect: they can talk.

The Unable to connect to remote host. error means it cannot even talk to the remote computer. So that's why it is important to check it on the same computer as Heapdhones runs on, and if it does not work, it is a computer or network related issue -- not Headphones.

tomrip commented 10 years ago

yes, this is the computer that headphones is on. just to test a little more, i disabled all newznab but dognzb, i still get the same error. As a test further, i will disable all newznab in sickbeard and couch paotoat, to see if i get the same results. i also have tried to generate a new api number from dog nzb, same result. I will post my findigns in a few minutes. i appreciate your time. 2014-06-11 15:10:08 ERROR Unable to connect to remote host. 2014-06-11 15:10:08 INFO Parsing results from https://api.dognzb.cr

piejanssens commented 10 years ago

This is clearly not related to HP.

rembo10 / headphones

cant dl from dognzb #1708