Messages

I also upgraded from 26.1.2_5 and received the same popup. The system continued to upgrade and seems to be working normally.

I looked in the error logs and found some suspicious entries in the backend logs, all from the config.d process:

Code Select Expand

2026-03-04T17:08:50-05:00Errorconfigd.py[8a5a8686-eb4e-4ce0-b36f-182539b085c3] Script action failed with Command '/usr/local/opnsense/scripts/ddclient/ddclient_opn.py -l' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 85, in execute subprocess.run(script_command, env=self.config_environment, shell=True, ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check=not self.disable_errors, stdout=output_stream, stderr=error_stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/ddclient/ddclient_opn.py -l' returned non-zero exit status 1.
2026-03-04T17:08:46-05:00Errorconfigd.py[e8e9881d-1ff4-4fc8-8808-d2daaa156e9f] Script action failed with Command '/usr/local/opnsense/scripts/ddclient/ddclient_opn.py -l' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 85, in execute subprocess.run(script_command, env=self.config_environment, shell=True, ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check=not self.disable_errors, stdout=output_stream, stderr=error_stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/ddclient/ddclient_opn.py -l' returned non-zero exit status 1.
2026-03-04T17:08:43-05:00Errorconfigd.py[5ecb8de5-f9dd-4ddf-9ec6-15828cc1f26b] Script action failed with Command '/usr/local/opnsense/scripts/ddclient/ddclient_opn.py -l' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/actions/script_output.py", line 85, in execute subprocess.run(script_command, env=self.config_environment, shell=True, ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ check=not self.disable_errors, stdout=output_stream, stderr=error_stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/subprocess.py", line 577, in run raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/ddclient/ddclient_opn.py -l' returned non-zero exit status 1.


Did this patch make it into 25.7.1? The patch notes did refer to netflow, but used different language than in this thread.

The patch also worked for me. I had to go to Reporting > Settings and clean things up, though.

One word of caution to those who come after--my disk filled up with netflow data in a few days, so I suggest that you either apply the patch, turn off netflow, or downgrade until this is fixed.

Follow up: I rebooted OPNsense and found that the disk was filled (due to the regression reported in #48085.15). I cleaned up the disk and reverted to the latest 25.1 snapshot and all now seems well.

I upgraded to 25.7 on release day. Seems to have largely gone smoothly.

However, yesterday, I started getting the titular CSRF error. I've tried clearing just the site cookies, rebooting my client machine, and using other browsers, neither of which had previously accessed my OPNsense GUI. Nothing has worked, including completely deleting all cookies, site data, etc. on one of the other browsers.

I haven't yet tried rebooting the OPNsense box, as I'll have to schedule some downtime.

Is there any remedy short of rebooting the box? Will this work?

Thanks in advance for any advice.