Messages

No, but thanks for suggestion.  Issue has disappeared.  Suspect it was issue with my laptop, not opnsense.

This came up in my Google search results on this issue, so posting here for the benefit of others.

I had to do two things in the web interface to get the ddclient working with Porkbun.

1) On the 'general settings' tab, select ddclient as the backend.  On my machine, it defaulted to 'native' as the backend.
2) When adding the Porkbun account, select 'Interface' as the 'check ip method'.

The web ui for ddclient has columns for 'current ip' and 'updated'.  On my machine, these remain blank and are not updated in the web ui (bug?).  However, ddclient does update the Porkbun A record.  I'm not sure, but you might need to create an A record on Porkbun in the first place.  I pointed it at 127.0.0.1 so I could tell when ddclient updated it.  Check /var/log/ddclient/latest.log to confirm.

I have 4 interfaces as follows:

[LAN] 192.168.x.0/24
[VLAN200] 192.168.y.0/24
[VLAN300] 192.168.z.0/24
[WAN] <public ip address>

Sometimes, I have been logged in to OPNsense from my laptop on the LAN or VLAN20 network and then I lose access to OPNsense.  It responds to pings, but nmap suggests no ports are open.

Now, the weird thing is that I'm able to log in again, but only from the public WAN address.  This only works from my internal networks, I'm not able to access it from the public internet.  Then, after a while I'm able to access it again from the LAN or VLAN20 network and nmap shows ports open again.

Grateful for any insights.