Is there a way to backrev to 2.2.5? 2.2.6 is no good for me… cp dies often
-
Same problem here.
Happens a few times a week, seems random.
Services status still reports captiveportal as Up so the only chance to know if its down is if a client user is reporting or if you use external monitoring on the CP's http/https. -
What will be lighttpd replacement in PfSense 2.3 ?
Beta section of the forum https://forum.pfsense.org/index.php?board=65.0 : third line ….
-
Same problem here.
Happens a few times a week, seems random.
Services status still reports captiveportal as Up so the only chance to know if its down is if a client user is reporting or if you use external monitoring on the CP's http/https.Try upgrading lighttpd as others have done successfully, 'pkg install lighttpd', then option 16 followed by option 11 at the console.
-
Same problem here.
Happens a few times a week, seems random.
Services status still reports captiveportal as Up so the only chance to know if its down is if a client user is reporting or if you use external monitoring on the CP's http/https.You can check this using CLI (ssh public key auth for automation):
ps -aux | grep http
root 13324 7.0 1.4 169520 115368 - S 2:52PM 57:12.67 /usr/local/sbin/lighttpd -f /var/etc/lighty-ssid_ups-CaptivePortal-SSL.co
root 11329 0.0 0.1 56884 7736 - S 2:52PM 0:40.39 /usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf
root 13040 0.0 0.2 67120 17404 - S 2:52PM 3:42.73 /usr/local/sbin/lighttpd -f /var/etc/lighty-ssid_ups-CaptivePortal.confOr checking log file for Lighttpd 'Core dump' error.
Denis.
-
Does anyone know if this problem i solved in 2.3 ?
-
Well ….. knowing that "lighttpd" isn't part of pfSEnse 2.2.3 anymore ....... ;)
2.2.3 works fine for me ....
Oops : I meant 2.3.
-
Gertjan: The new version is named 2.3
The version you are referring to, is prior to 2.2.5 and 2.2.6 and still contains lightppd. -
Yes it is solved in 2.3. lighttpd no longer exists, that's been switched to nginx which has no such problems.
