Messages

After the 18.1 update, captive portal sessions aren't showing anymore (/ui/captiveportal/session/). I've also tried the CLI with configctl captiveportal list_clients 0 and i get an "execute error".

The captive portal functions are running and the CP users are not reporting any problems. It's just the session list that isn't showing anything.

Any (hopefully quick) fix for this? Thanks.

I'm still getting the warning message but captive portal works without any problems.  :)

This is good to know. I was beginning to wonder if it was caused, in my case, by a witches' brew of MultiWAN, VLANs, VMs, and a dash of proxmox

Running Opnsense under proxmox 5, everything's been running great until now. Rebooting after the 17.7.9 update, i got this boot-time error. No other functions are affected except for captive portal (transparent proxy option disabled, and getting same boot-time message with cp local database authentication enabled/disabled, too).

help.

I've since gone back to the last image I downloaded (17.7.5). Last perfectly-running version was 17.7.8.

Opnsense is running as a Proxmox vm (2 cores, 1 socket, 2GB memory allocated, virtio network device) and configured running vlans for guest lan and dual-wan (load balancing and failover), hardware is an intel i7 NUC (single NIC)

using dnsmasq dns instead of unbound works for me.

Can you explain more what do you mean exactly ?
what does works and not ?

There are two options for dns: unbound dns and dnsmasq dns. I disabled unbound dns and enabled dnsmasq. Previously, I had unbound enabled and dnsmasq disabled.

I also followed wiki how-to for multiwan. It works without any problems, at least in my case.

using dnsmasq dns instead of unbound works for me.