Messages

1

20.1 Legacy Series / Re: Dynddns can't determine public IP

« on: July 18, 2020, 07:52:39 pm »

Got it working using the "Cloudflare API Token" service rather than the v6 one.

EDIT:  I see what happened now.  v6 refers to ipv6.  Of course that won't work for me with ipv6 disabled.  I thought the v6 referred to the api version or something.

2

20.1 Legacy Series / Re: Dynddns can't determine public IP

« on: July 18, 2020, 07:34:09 pm »

No it doesn't.  It's a "real" IP.  235.xxx.xxx.xxx.  Strange thing is; I used to use the namecheap dyndns setting and that one works without trouble.  The cloudflare v6 token doesn't appear to work for me.

3

20.1 Legacy Series / Dynddns can't determine public IP

« on: July 18, 2020, 02:34:18 am »

OPNsense 20.1.8_1-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
LibreSSL 3.0.2

I'm trying to get dyndns working with cloudflare.  I have a simple set up with just a static ipv4 ip (ipv6 is disabled).  I get the following error in log files when trying to update cloudflare.  The overview page under interfaces shows an IP.

opnsense: /services_dyndns_edit.php: Dynamic DNS (xxxxxxt) There was an error trying to determine the public IP for interface - wan(vtnet1). Probably interface is not a WAN interface.

4

18.1 Legacy Series / Re: Uncaught Error: Call to undefined function encrypt_data()

« on: May 26, 2018, 06:06:18 pm »

I'm seeing this as well.  I just created this account to post about this problem and saw this post so I'll just keep an eye on it instead of making another.