Messages

Hi,

had the same issue on 1 of 3 firewall updates. Killing the crowdsec bouncer did the job.

Regards

Michael

Just found the problem. Port was set to 22. Dont know how this happened...

The only log message i get, when i try to start unbound:

daemonize unbound dhcpd watcher

Hello,

since i installed the update this morning unbound wont start. This is the message i have found:

opnsense-pa.xxxx.de configd.py[279]: [aadf7eeb-b26a-4b3c-8812-c18be4675d0c] Script action failed with Command '/usr/local/opnsense/scripts/unbound/wrapper.py -s ' returned non-zero exit status 1. at Traceback (most recent call last):   File "/usr/local/opnsense/service/modules/processhandler.py", line 482, in execute     subprocess.check_call(script_command, env=self.config_environment, shell=True,   File "/usr/local/lib/python3.9/subprocess.py", line 373, in check_call     raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/unbound/wrapper.py -s ' returned non-zero exit status 1

Can someone help please?

Regards

Michael

This fixes the issue:

https://github.com/opnsense/plugins/pull/3406

Hi. Have you checked Quick (see attached image) on the rules?

Hello,

i ran the update to 23.1.6 yesterday and i have a dual WAN setup. The os-ddclient is configured to use the IP of WAN2. Since the update it uses the WAN1 IP.

Thanks for any ideas how to fix that.

Michael

Friends who use OPNsense on ESX:

Which ESX version are you on?  We would like to know about the problematic versions.

Hello. I have the same problem. My setup:
Hypervisor: VMware ESXi 6.7.0 Update 3 Build 16316930
VM Compatibiltiy: 6.7 U2
Standard vSwitch

Running OPNsense with no special interfaces configurations (VLAN etc.) using vmxnet3.