pfSense

Ramon Alonso Costa wrote:

I am having the following issue when trying to update the DNS Resolver backup. Below is the file with the error.

Please clarify what you mean by "update the DNS Resolver backup". What is the process to reproduce the errors you're seeing?

This bug report has insufficient information to ascertain what could be going on here.

I have a similar stack trace for an issue that is maybe not completely the same.

After upgrading to version 2.7.2-RELEASE (community edition) using drag & drop to change the order of the Phase2 IPSec connections results in the stacktrace below. Go into the IPsec configuration, click on 'Show Phase 2 Entries' and then use the little anchor symbol to change the order of the connection by drag and dropping it.

[21-Feb-2024 10:54:18 Europe/Brussels] PHP Fatal error:  Uncaught TypeError: array_path_enabled(): Argument #1 ($arr) must be of type array, int given, called in /etc/inc/config.lib.inc on line 1250 and defined in /etc/inc/util.inc:3662
Stack trace:
#0 /etc/inc/config.lib.inc(1250): array_path_enabled(-1, 'notifications/s...', 'disable')
#1 /etc/inc/notices.inc(379): config_path_enabled('notifications/s...', 'disable')
#2 /etc/inc/notices.inc(662): notify_via_smtp('pfSense is rest...')
#3 /etc/inc/notices.inc(151): notify_all_remote('pfSense is rest...')
#4 /etc/inc/config.lib.inc(239): file_notice('config.xml', 'pfSense is rest...', 'pfSenseConfigur...', '')
#5 /etc/inc/config.lib.inc(695): restore_backup('/cf/conf/backup...')
#6 /usr/local/www/vpn_ipsec.php(264): write_config('Saved configura...')
#7 {main}
  thrown in /etc/inc/util.inc on line 3662

Good afternoon,

When I try to add a host to synchronize pfBlocker with other appliances, upon saving, I encounter this error, which I reproduce below:

Crash report begins.  Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT amd64 1400094 #1 plus-RELENG_23_09_1-n256200-3de1e293f3a: Wed Dec  6 21:00:32 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_09_1-main/obj/amd64/Obhu6gXB/var/jenkins/workspace/pfSense-Plus-snapshots-23_09_1

Crash report details:

PHP Errors:
[02-Apr-2024 18:06:39 Europe/Madrid] PHP Fatal error:  Uncaught TypeError: array_path_enabled(): Argument #1 ($arr) must be of type array, int given, called in /etc/inc/config.lib.inc on line 1264 and defined in /etc/inc/util.inc:3748
Stack trace:
#0 /etc/inc/config.lib.inc(1264): array_path_enabled(-1, 'notifications/s...', 'disable')
#1 /etc/inc/notices.inc(379): config_path_enabled('notifications/s...', 'disable')
#2 /etc/inc/notices.inc(662): notify_via_smtp('Netgate pfSense...')
#3 /etc/inc/notices.inc(151): notify_all_remote('Netgate pfSense...')
#4 /etc/inc/config.lib.inc(239): file_notice('config.xml', 'Netgate pfSense...', 'pfSenseConfigur...', '')
#5 /etc/inc/config.lib.inc(695): restore_backup('/cf/conf/backup...')
#6 /usr/local/www/pfblockerng/pfblockerng_sync.php(140): write_config('[pfBlockerNG] s...')
#7 {main}
  thrown in /etc/inc/util.inc on line 3748

No FreeBSD crash data found.

Furthermore, in the OpenVPN Client Export package, when adding a password to the certificate, I also encounter this other error, And the crash report:

Crash report begins.  Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT amd64 1400094 #1 RELENG_2_7_2-n255948-8d2b56da39c: Wed Dec  6 20:45:47 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_7_2-main/obj/amd64/StdASW5b/var/jenkins/workspace/pfSense-CE-snapshots-2_7_2-main/sources/F

Crash report details:

PHP Errors:
[02-Apr-2024 17:13:14 Europe/Madrid] PHP Fatal error:  Uncaught TypeError: array_path_enabled(): Argument #1 ($arr) must be of type array, int given, called in /etc/inc/config.lib.inc on line 1250 and defined in /etc/inc/util.inc:3662
Stack trace:
#0 /etc/inc/config.lib.inc(1250): array_path_enabled(-1, 'notifications/s...', 'disable')
#1 /etc/inc/notices.inc(379): config_path_enabled('notifications/s...', 'disable')
#2 /etc/inc/notices.inc(662): notify_via_smtp('pfSense is rest...')
#3 /etc/inc/notices.inc(151): notify_all_remote('pfSense is rest...')
#4 /etc/inc/config.lib.inc(239): file_notice('config.xml', 'pfSense is rest...', 'pfSenseConfigur...', '')
#5 /etc/inc/config.lib.inc(695): restore_backup('/cf/conf/backup...')
#6 /usr/local/www/vpn_openvpn_export.php(194): write_config('Save openvpn cl...')
#7 {main}
  thrown in /etc/inc/util.inc on line 3662

No FreeBSD crash data found.

Could you please help me with this error? Despite my searches, I haven't found anything, and the OpenVPN certificate isn't working because no password seems to function.

Robbe Van der Gucht wrote in #note-3:

I have a similar stack trace for an issue that is maybe not completely the same.

After upgrading to version 2.7.2-RELEASE (community edition) using drag & drop to change the order of the Phase2 IPSec connections results in the stacktrace below. Go into the IPsec configuration, click on 'Show Phase 2 Entries' and then use the little anchor symbol to change the order of the connection by drag and dropping it.
[...]

Good evening, have you solved this issue?

David Cuadrado Sanchez wrote in #note-5:

Robbe Van der Gucht wrote in #note-3:

I have a similar stack trace for an issue that is maybe not completely the same.

After upgrading to version 2.7.2-RELEASE (community edition) using drag & drop to change the order of the Phase2 IPSec connections results in the stacktrace below. Go into the IPsec configuration, click on 'Show Phase 2 Entries' and then use the little anchor symbol to change the order of the connection by drag and dropping it.
[...]

Good evening, have you solved this issue?

No. I stopped re-ordering Phase2 connection, to avoid triggering the issue.

Good afternoon, I have an update. I have noticed that if I don't use certain characters, such as Ñ and others, in both the Client Export and the SYNC tab of pfBlocker, in both password fields (certificate and firewall to which I want to synchronize the configuration), the error does not occur. Can anyone shed some light on this?

tested on:
24.03-BETA (amd64)
built on Fri Mar 22 17:08:00 UTC 2024
FreeBSD 15.0-CURRENT
patch fixes the actual crush, but reordering ipsec phase2 connections etc still doesn't work and causes config restore

Yes, with the notification error patched the real bugs generating a bad config should become apparent. Separate issues should be opened for them.