Bug #12537
closedIPsec -> Advanced Settings not working: PHP Fatal error
0%
Description
On every pfSense 2.5.2 box I'm getting:
Fatal error: Uncaught TypeError: Argument 4 passed to Form_Select::__construct() must be of the type array, null given, called in /usr/local/www/vpn_ipsec_settings.php on line 385 and defined in /usr/local/www/classes/Form/Select.class.php:31 Stack trace: #0 /usr/local/www/vpn_ipsec_settings.php(385): Form_Select->_construct('filtermode', 'IPsec Filter Mo...', NULL, NULL) #1 {main} thrown in /usr/local/www/classes/Form/Select.class.php on line 31 PHP ERROR: Type: 1, File: /usr/local/www/classes/Form/Select.class.php, Line: 31, Message: Uncaught TypeError: Argument 4 passed to Form_Select::_construct() must be of the type array, null given, called in /usr/local/www/vpn_ipsec_settings.php on line 385 and defined in /usr/local/www/classes/Form/Select.class.php:31 Stack trace: #0 /usr/local/www/vpn_ipsec_settings.php(385): Form_Select->__construct('filtermode', 'IPsec Filter Mo...', NULL, NULL) #1 {main} thrown
I have verified that the global variable "ipsec_filtermodes" used to instantiate the "Form_Select" class is declared as global in /usr/local/www/vpn_ipsec_settings.php (38) and that it has no value assigned. That variable doesn't exist in any other php script in /usr/local/www/*
Hope this help you to fix soon this little bug.
Regards
Files
Updated by Kris Phillips over 3 years ago
Hello,
I'm not able to reproduce this in 2.5.2. What specific steps are you doing to cause this error?
Updated by Guillermo Martínez over 3 years ago
Hi, I don't do anything special, I just access IPsec -> Advanced settings and get this error (see attached image), and there's no IPsec VPN settings, it's all empty.
I have 14 pfSense boxes all CE 2.5.2, some running virtualized and the rest bare metal and I'm getting the same error in all, that's why I thought maybe it could be a bug.
Updated by Viktor Gurov over 3 years ago
Unable to reproduce it on 2.5.2 VM clean install
Where did you download the pfSense image?
Updated by Guillermo Martínez over 3 years ago
Sorry, it has been a problem in globals.inc, a custom modification caused the failure, I'm sorry for your time waste loss and have bothered, since it occurred on so many machines I thought it was something generalized. The case can be closed.