then it changed to installing packages for another hour and a half (To be fair I did not have that may packed installed in the first place) The web configurator was accessible but still had the message stating 'pfsense was still booting'ĭHCP was not issuing/renewing leases while it was 'still booting' for more than 45 mins.PFsense was very slow all through the upgrade Just to be sure can you confirm if /usr/local/etc/nginx/nf is used by the webconfigurator? As it stands the webconfigurator is exposed to the WAN side as the built in nginx seems to be listening on all interfaces and my port 80 is open on the WAN like to know what issues you had to fix post-upgrade. Thanks cmb, I shall try the separate nginx instance approach. Ps: I use the term native loosely here and refer to the nginx supplied with pfsense 2.3 Is it possible to have virtualhosts configured on the 'native' nginx and what files needs to be changed for the same? There is a remnant rc.d script from 2.2.6 nginx that I had installed, could here be two versions of nginx setting on the box ? How do I check this and if remove one to just retain the 'native' version?Ĥ. I have made some changes to the nf at the above location, that seems to be ignored. Where do the configuration file(s) for the native nginx on 2.3 reside? Is it /usr/local/etc/nginx ?Ģ.

I was using nginx on 2.2.6 as a way of hosting multiple websites (virtual hosts that proxy on to internal servers) and I was hoping the native NGINX in 2.3 would be much more convenient but I am stuckġ. With a downtime of nearly 2 hours and some minor issues to fix ( I am not here to go over them).

The upgrade was a success but it was not as smooth as I would have expected.

Hope someone has fixed a similar problem and is able to answer my questions…

Nxfilter pfsense 2.3