Unknown Eception: Bad Gatewat and Path not found

Sonarr version (2.0.0.4689):
Mono version (if Sonarr is not running on Windows):
OS: WINDOWS 10

((Debug logs)):

(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here)
Description of issue:
I changed system and installed sonarr.
I restore my setting and everything using backup and restore from my previously installed sonarr.
When I tried to create a path for my downloads, only one network drive was being mapped. The other network drive sonarr doesn’t see it (Series’ root folder (\NAS\Movies\TV Episodes) doesn’t exist.). Even when I typed it, it said path not found. It was odd since it was able to mapped the other network drive for my anime but not for my tv episodes directory.

rtorrent wasn’t connecting either. when everything were running smoothly before Please logs above.
I apologize for not knowing how to use hastebin.

Thank you.

You just need to copy the contents of the file and post it there, save it and copy the link and post it here. Please psot them as the formatting of them here is off and I can’t tell if the path is actually invalid or the formatting has changed them. Also make sure you’ve read the ((FAQ)) as network shares is explicitly covered there.

For rTorrent make sure the hostname/port is correct, though it may be a problem with the system’s gateway to the internet.

https://hastebin.com/ayakuhonil.tex

The setting for my download client is correct. I copied the settings from my previous installations.
If the systems gateway to the internet is wrong, how would I resolved it?

My network shares were the same as before. with the correct UNC path (\server\folder).
Even when it showed, the space was showing up empty.

Thank you.

This is the error that I am having:

My DHCP Server, Default Gateway and DNS server have the same IP addresses.

Thank you.

Please post the full log file, not just the errors.

For the gateway, can you connect to the seedbox from the PC that is running Sonarr (from Edge/IE)?

I don’t know how to make it fit on hastebin without exceeding the limit, but please click on the link for logs:
https://1drv.ms/t/s!AneG2TvCiWuid2eSxxmn3kL6MhA

Yes:

I don’t have problem connecting to my seedboxes online from my PC.

Should you be using oceanus.fealhosting.com in the server field in Sonarr since that’s what you’re using in the browser (not sure if you intentionally changed it).

I’m also seeing:

The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

For requests, which means the server didn’t respond at all.

I intentionally changed it after using the correct address.

That’s just one problem, sir. I still haven’t figured why Sonarr is not seeing the rest of my network path?

The only other thing that I think could be wrong is the URL base, have you tried with a leading slash? (offhand, I’m not sure it if makes a difference)

Have you read the ((FAQ))?

Still didn’t work even with two slashes.

I solved the remote server problem by running sonarr under my account. Solution found on the faq that you provided, thanks a lot for that.

What’s wrong with feraaaallll!

A slash before the URL Base, not the Host (a slash before the Host is invalid, which the error message shows).

oops!

Didn’t work still “Unknown exception: Bad Gateway”.

at /username/rtorrent/rpc

Probably best to contact feralhosting’s support to see if they have any ideas as this seems to be an issue on the rtorrent side of things. I believe you’re actually getting an error similar to 502 Bad Gateway error from the RPC server, though I’m not 100% sure.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.