Messages

Thank you so much Franco,
We are using ZFS not UFS. We know isn't much to do once it's been corrupted but the problem we want to know what is the reason for that.
I mean the corrupted captiveportal.sqlite.
This issue does not occur immediately in the reboot or after a reboot, but it starts happening while the OPNsense router is up, running and working normal. It occurs multiple times a day.
Best Regards,
Saleh

[Services: Captive Portal: Log File]

Hello Franco,

Could you please help us to fix this issue. This issue occurs multiple times a day. When it happens  current users Sessions in the captive portal not appears and users can connect the internet without the hotspot authentication.

Services: Captive Portal: Log File

2025-05-15T08:34:11   Error   captiveportal   sqlite3 repair /var/captiveportal/captiveportal.sqlite   
2025-05-15T08:34:11   Error   captiveportal   Forcefully repair database (Traceback (most recent call last): File "/usr/local/opnsense/scripts/OPNsense/CaptivePortal/cp-background-process.py", line 251, in main bgprocess.db.cleanup_sessions() File "/usr/local/opnsense/scripts/OPNsense/CaptivePortal/lib/db.py", line 360, in cleanup_sessions cur.execute(""" delete sqlite3.OperationalError: no such table: accounting_state )   
2025-05-15T08:33:11   Error   captiveportal   sqlite3 repair /var/captiveportal/captiveportal.sqlite [done]   
2025-05-15T08:32:40   Error   captiveportal   sqlite3 repair /var/captiveportal/captiveportal.sqlite   
2025-05-15T08:32:40   Error   captiveportal   Forcefully repair database (Traceback (most recent call last): File "/usr/local/opnsense/scripts/OPNsense/CaptivePortal/cp-background-process.py", line 251, in main bgprocess.db.cleanup_sessions() File "/usr/local/opnsense/scripts/OPNsense/CaptivePortal/lib/db.py", line 360, in cleanup_sessions cur.execute(""" delete sqlite3.OperationalError: no such table: accounting_state )   

Thank you.

Hello,
We are getting every day many log errors in the captive portal service regarding captiveportal.sqlite, what is the reson that the captiveportal.sqlite file is corrupted. please see the below logs and images.

025-05-14T13:44:39    Error    captiveportal    sqlite3 repair /var/captiveportal/captiveportal.sqlite   
2025-05-14T13:44:39    Error    captiveportal    Forcefully repair database (Traceback (most recent call last): File "/usr/local/opnsense/scripts/OPNsense/CaptivePortal/cp-background-process.py", line 251, in main bgprocess.db.cleanup_sessions() File "/usr/local/opnsense/scripts/OPNsense/CaptivePortal/lib/db.py", line 360, in cleanup_sessions cur.execute(""" delete sqlite3.OperationalError: no such table: accounting_state )

Thank you

[Services: Captive Portal: Log File]

Note: Another thing there are no logs in the
Services: Captive Portal: Log File

[Services: Captive Portal: Sessions]

After updating to the latest version 25.1.5_5, we are experiencing empty sessions in the Captive Portal Sessions. This issue does not occur immediately after a reboot, but it starts happening while the OPNsense router is running. It occurs multiple times a day. The sessions only reappear after we stop the captive portal, delete the captiveportal.sqlite file, and then restart the captive portal.

We are only facing this issue after updating OPNsense to version 25.1. Why is the captiveportal.sqlite file getting corrupted?

Services: Captive Portal: Sessions

Thank you

[OPNsense 25.1.5]

Today I upgrade OPNsense 25.1.5 to the latest hotfix release 25.1.5_4 after that the Captive Portal user authentication not working and give the message "authentication failed" although the username and password is correct. Removing the captive portal and recreating it didn't solve the issue.
Note: Allowed addresses is working but the Captive Portal user authentication not working although the username and password is correct and tested with System: Access: Tester.

Thank you.

Is there any example for JSON body for addRule?
Thank you

Hello,

We need to update captive portal accounting every 600 seconds. In the current setting the update made every 6 seconds. We think to use the Acct-Interim-Interval attribute so that we have changed the test user profile like the below:

test Cleartext-Password := "testing123", Simultaneous-Use := "1"
        Acct-Interim-Interval := 600,
        Framed-Protocol = PPP

But after testing we found the Acct-Interim-Interval attribute have no effect (Not working) and the accounting update made every 6 seconds like the below example:

Sat Aug 24 20:57:55 2024
        NAS-Identifier = "66c122ef7fec9"
        Service-Type = Framed-User
        Framed-Protocol = 15
        NAS-Port = 0
        NAS-Port-Type = Ethernet
        User-Name = "test"
        Acct-Status-Type = Interim-Update
        Acct-Session-Id = "mf2CWztLHGcqmOs11VvR+A=="
        Acct-Authentic = Local
        Acct-Session-Time = 683
        Acct-Input-Octets = 5252767
        Acct-Output-Octets = 6038308
        Framed-IP-Address = 192.168.1.201
        NAS-IP-Address = 127.0.0.1
        Event-Timestamp = "Aug 24 2024 20:57:55 EEST"
        Acct-Unique-Session-Id = "912d036be955f3df393c422e346ffa99"
        Timestamp = 1724522275

Sat Aug 24 20:58:01 2024
        NAS-Identifier = "66c122ef7fec9"
        Service-Type = Framed-User
        Framed-Protocol = 15
        NAS-Port = 0
        NAS-Port-Type = Ethernet
        User-Name = "test"
        Acct-Status-Type = Interim-Update
        Acct-Session-Id = "mf2CWztLHGcqmOs11VvR+A=="
        Acct-Authentic = Local
        Acct-Session-Time = 689
        Acct-Input-Octets = 5253158
        Acct-Output-Octets = 6038468
        Framed-IP-Address = 192.168.1.201
        NAS-IP-Address = 127.0.0.1
        Event-Timestamp = "Aug 24 2024 20:58:01 EEST"
        Acct-Unique-Session-Id = "912d036be955f3df393c422e346ffa99"
        Timestamp = 1724522281

Any idea how to fix this issue.
Thank you

We are using static route without BGP on IPSEC route based but we are sure that after upgrade to latest version  23.1.7_3 the static routing not working. I think there is a problem on the manual  created VPN Gateway.

System: Gateways: Single

Please update us regarding the static routing issue (IPsec route based ) on the latest version 23.1.7_3.
Is the issue fixed.
Thank you.

Hello,

After upgrade from 23.1.5 to 23.1.7_3 the static routing is broke and stopped working without any change to the settings (IPsec route based). Reverting to 23.1.5 fixes the static routing issue.
Note: The same issue for wireguard

https://forum.opnsense.org/index.php?topic=33937.0

Thank you.

We have the same issue. Static routing not working for "IPsec - Route based setup" after upgrade to 23.1.7
How we can fix this issue.
Thank you.