SABnzbd HTTP Error 502: Bad Gateway

[welshys]

Hi All

I've setup several plugins working all harmoniously until we had a power surge last night and the freeNAS box lost power. On restart everything came back online except the sabnzbd service. Every time I try and turn the service on I get this, any help would be awesome, I'm totally new to all this so not sure how to troubleshoot, if there are some commands I can input to check please let me know. Thank you so much!:

Oct 26 11:28:30 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v Oct 26 11:28:31 freenas last message repeated 4 times Oct 26 11:28:31 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.1.66/plugins/sabnzbdplus/1/_s/status: HTTP Error 502: Bad Gateway Oct 26 11:29:01 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v Oct 26 11:29:15 freenas last message repeated 5 times Oct 26 11:29:16 freenas manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.1.66/plugins/sabnzbdplus/1/_s/status: HTTP Error 502: Bad Gateway Oct 26 11:29:49 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v

 

[cyberjock]

Bad gateway is a network configuration problem. So either the configuration is bad, or you have a problem with your network(perhaps related to the power surge).

I'll say this just once... running FreeNAS without a UPS is a recipe for disaster. You should have a UPS so that the system can shut down properly on a loss of power. You are luck as some users have not had a UPS and when power came back they lost their pool and all of their data. Don't be a statistic!

 

[welshys]

Thanks for the reply, I'll look into buying a UPS post haste. In regards to the actual issue is there anything I can do to troubleshoot a network config problem? I don't understand how it is only SABnzbd plugin that has stopped working whilst sick beard, couch potato, dlna, plex and transmission are fine. If I do have to reinstall it does anyone know where the config file is stored so I don't have to setup all the different categories etc.

 

[sdspieg]

Could somebody please provide some ideas on how this 'Error 502: Bad Gateway' problem can be resolved? It has been asked many time on this forum, but has - as far as I can tell - not been answered yet.

These are the error codes I receive since I had to resilver a drive recently (I'm not sure whether that has anything to do with the problem, but things worked fine before that):

Code:

Dec  7 14:24:50 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.1.6/plugins/sickbeard/10/_s/treemenu: HTTP Error 502: Bad Gateway
Dec  7 14:24:50 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.1.6/plugins/Couchpotato/11/_s/treemenu: HTTP Error 502: Bad Gateway
Dec  7 14:24:50 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.1.6/plugins/sabnzbdplus/12/_s/treemenu: HTTP Error 502: Bad Gateway
Dec  7 14:24:50 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.1.6/plugins/plexmediaserver/13/_s/treemenu: HTTP Error 502: Bad Gateway
Dec  7 14:24:50 freenas manage.py: [freeadmin.navtree:522] Couldn't retrieve http://192.168.1.6/plugins/sabnzbd/15/_s/treemenu: HTTP Error 502: Bad Gateway

Here is my network configuration summary:

Code:

Name    IPv4 Address
re0    192.168.1.6/24
Nameserver
8.8.8.8
8.8.4.4
Default route
192.168.1.1

I do have network connectivity from my FreeNAS; and the transmission plugin I reinstalled today works fine. But all the other plugins do not (EVEN when I enter the gateway manually). So if anybody would have any suggestions of where to find a solution (where even to look), I'd be very grateful.

 

[raymonvdm]

I`m having this same issue after deleting one plugin al the others don`t start anymore

Code:

Jan  8 15:24:43 freenas02 manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.120.190/plugins/owncloud/2/_s/status: HTTP Error 502: Bad Gateway
Jan  8 15:24:43 freenas02 manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.120.190/plugins/sabnzbdplus/3/_s/status: HTTP Error 502: Bad Gateway

 

[Naesstrom]

I got the same problem to, listening in if anyone finds a solution!

 

[Mark allen]

I've got this issue with a variety of FreeNAS .pbi's as well- and haven't seen any real solution after looking through the forum posts (though there have been a variety of questions concerning this topic over the years). For me, When installing a specific version of Transmission, rTorrent or Deluge (or any pbi from the "Upload" feature), a jail is created, an IP assigned and the service fails to start with the "HTTP 502 Error" shown.
My ethernet works, and will function (upload, download and show connectible) with Transmission 2.82 when installed from the list of selected (current) built-in pbi's. I'm however, limited to certain versions of specific programs (e.g. Transmission 2.42, Deluge 1.3.5 or 1.3.6). Any help would be appreciated.

 

[Red Arrow]

I'm in the same situation. New to FreeNAS and got Plex running in one Jail and SABnzbd and Sickbeard in another. Everything was working fine then this morning it seems SAB and Sickbeard no longer turn on and I'm getting the same error. Plex is running fine.

No setting have been changed, the default gateway is correct in the SAB and Sickbeard Jail. I'm at a lose on what has caused this.

 

[Red Arrow]

Anyone know of a solution? After doing some digging around this forum it seems a lot of people have encountered this issue yet there has been no solution apart from try deleting the Jail and start again. Something I've done a few times but this problem then comes back.

It's getting to the point where I might have to dump FreeNAS and go back to Windows as I need Sickbeard to work.

 

[Mark allen]

I was never able to get any of the non-included pbi's to work. Each one always gave the "Bad Gateway" error. I eventual went with another NAS config. I would have liked to stay with FreeNAS (RAID options, seemingly good array of pbi's) but in the end I needed Sickbeard and specific a version of Transmission which I could never get to work.

 

[Red Arrow]

I was never able to get any of the non-included pbi's to work. Each one always gave the "Bad Gateway" error. I eventual went with another NAS config. I would have liked to stay with FreeNAS (RAID options, seemingly good array of pbi's) but in the end I needed Sickbeard and specific a version of Transmission which I could never get to work.

What did you end up switching too?

 

[Mark allen]

Xpenology 4.3. Right now, I'm working on getting the setup to shed wattage. Started at ~89w (Asus MB, Quad Core 9550 chip, 8GB DDR2, 6 WD Red HD's).
Presently, I de-clocked the CPU, reduced the CPU voltage and removed 2 of the sticks of ram (2.5 watts each) and am down to 75w while serving ~40 active files on Transmission (2.42), with Plex and Sickbeard running. I think this is about as good as I am going to get (without changing the CPU to a low wattage 775 or going to a Haswell setup), and about 20-25w more than my old CS-406e (4 disk).
For me, this would be >$10/month if run 24/7, which I think is acceptable.

 

[marcevan]

It's a jails to plugins config issue. I'm still researching the sqlite3 tables that house this.

found:

services_pluginsjails but that seems deprecated (no data for working plugins or freshly installed ones)
plugins_plugins but that backends the GUI plugins table for installed ones, not the navtree

So still fishing, though in my situation my plugins work, but are not showing in the navtree (hence my 502 errors).

 

[ijfrederick]

I`m having this same issue after deleting one plugin al the others don`t start anymore

Code:

Jan  8 15:24:43 freenas02 manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.120.190/plugins/owncloud/2/_s/status: HTTP Error 502: Bad Gateway
Jan  8 15:24:43 freenas02 manage.py: [plugins.utils:87] Couldn't retrieve http://192.168.120.190/plugins/sabnzbdplus/3/_s/status: HTTP Error 502: Bad Gateway

Interested. Same problem

 

[Lusca]

Anything new on this topic?

I got the same issue, just with cp and sab..

Code:

Mar 15 14:35:35 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 15 14:35:35 freenas manage.py: [freeadmin.navtree:526] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/treemenu: HTTP Error 502: Bad Gateway
Mar 15 14:35:44 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/status: HTTP Error 502: Bad Gateway
Mar 15 14:35:44 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/status: HTTP Error 502: Bad Gateway
Mar 15 14:37:30 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/status: HTTP Error 502: Bad Gateway
Mar 15 14:37:30 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/status: HTTP Error 502: Bad Gateway
Mar 15 14:37:51 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/couchpotato/1/_s/status: HTTP Error 502: Bad Gateway
Mar 15 14:37:51 freenas manage.py: [plugins.utils:92] Couldn't retrieve http://192.168.1.220/plugins/sabnzbd/2/_s/status: HTTP Error 502: Bad Gateway

 

[marcevan]

I'm getting this for transmission only. Happened one day ago and I made no plugin or permission changes.

 

[Lusca]

No fix? Ive tried some.. But seems like reinstallere and yet another reconfigure is the only way?
Frustrating

 

[marcevan]

I'm actually getting a 500 on transmission, not a 502, but I have no idea what caused it. Did no installs or permission changes and now it's not listed in the plugins and gives that error.

 

[dantest69]

I just got the error 502 today but I haven't made any changes to my FreeNAS config. Just happened out of the blue with Crashplan.

Very odd. I tried several reboots but the problem remains. Now I can't switch on my PBI plugins under "service status".

Glad I'm not the only one having this error.

 

[marcevan]

There's definitely something weird going on with plugins and jails.

If you uninstall a plugin it appears to remove the jail; however if you reinstall the plugin the prior jail is back with the mounted storage you had.
If you delete the jail you have another problem where the plugin will bring it back plus another so you'll have a _1 and _2 versions of the jail
500 and 502 errors occur spontaneously or with the above 2 cases. Going to the jail and removing VIMAGE helps in some, but not all cases. Transmission in particular. However I've seen that work for Plex and Sickbeard.