[pfSense] 502 Bad Gateway

2016-08-01 Thread Paul Galati
This morning I logged into the router to bring up the dashboard as I usually do. I began my day and some time later I revisited the dashboard to check on things and I get a 502 bad gateway error. I did not make any changes to the config at all today. From the beginning I did enable https

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread Jim Pingle
On 07/08/2016 10:09 AM, Bill Arlofski wrote: > I just realized something thanks to your post. It seems that I have also > witnessed that OpenVPN stops working when this occurs. It would depend on the type of OpenVPN. RA or SSL/TLS using certificates would likely fail as the scripts the verify

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread Bill Arlofski
On 07/08/2016 03:21 AM, Chris Buechler wrote: > It's worth trying at least. The case I had where that problem was > replicable was worked around in 2.3.1_5 on this ticket. > https://redmine.pfsense.org/issues/6318 > > There may be a related issue still outstanding from that, as the root > cause

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread Bill Arlofski
On 07/08/2016 02:44 AM, J. Echter wrote: > Hi, > > same issue here. I cannot access OpenVPN after a while and locally i get > bad gateway when connecting to pfSense webui. > > J Yes! I just realized something thanks to your post. It seems that I have also witnessed that OpenVPN stops working

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread Bill Arlofski
On 07/07/2016 02:50 PM, Vick Khera wrote: > On Thu, Jul 7, 2016 at 2:16 PM, Bill Arlofski > wrote: > >> I guess I will remove it the next time this happens and see if there is any >> change. >> > > It seems to me you should remove it *before* to see if you avoid it >

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread Chris Buechler
On Thu, Jul 7, 2016 at 1:16 PM, Bill Arlofski wrote: > On 07/07/2016 08:09 AM, Jon Gerdes wrote: >> Bill >> >> I maybe off target here but the IPSEC widget used to cause php-fpm >> daemon to die after a few days. >> >> I haven't looked into it since but removing that

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread J. Echter
i forgot to mention: pfSense 2.3.1. It works again if i restart php-fm. J ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] 502 Bad Gateway

2016-07-08 Thread J. Echter
Am 05.07.2016 um 19:19 schrieb Bill Arlofski: > Hi everyone... > > I noticed after one of the recent upgrades to the 2.2.x "RELEASE" series > everything works perfectly fine for a while but then, I get "502 Bad Gateway" > message when I attempt to access the web GUI. > > Up until recently, I

Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Jim Thompson
I run the widget on my dashboard without issue. Please stop assuming there is a problem, and take steps to prove it instead. -- Jim > On Jul 7, 2016, at 1:16 PM, Bill Arlofski wrote: > >> On 07/07/2016 08:09 AM, Jon Gerdes wrote: >> Bill >> >> I maybe off target

Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Vick Khera
On Thu, Jul 7, 2016 at 2:16 PM, Bill Arlofski wrote: > I guess I will remove it the next time this happens and see if there is any > change. > It seems to me you should remove it *before* to see if you avoid it happening. ___

Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Bill Arlofski
On 07/07/2016 08:09 AM, Jon Gerdes wrote: > Bill > > I maybe off target here but the IPSEC widget used to cause php-fpm > daemon to die after a few days. > > I haven't looked into it since but removing that widget fixed it for me > on two pfSenses. > > Cheers > Jon Hi Jon, Hmmm, I do have

Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Jon Gerdes
On Tue, 2016-07-05 at 13:19 -0400, Bill Arlofski wrote: > Hi everyone... > > I noticed after one of the recent upgrades to the 2.2.x "RELEASE" > series > everything works perfectly fine for a while but then, I get "502 Bad --- snip > > So, I am suspecting that the php-fpm

[pfSense] 502 Bad Gateway

2016-07-05 Thread Bill Arlofski
Hi everyone... I noticed after one of the recent upgrades to the 2.2.x "RELEASE" series everything works perfectly fine for a while but then, I get "502 Bad Gateway" message when I attempt to access the web GUI. Up until recently, I had been "fixing" this by physically powering off the firewall