Messages

1

22.1 Legacy Series / Re: cyrus-sasl

« on: March 02, 2022, 07:44:46 pm »

Franco, I am not trolling.  This is a response that I would typically see in pfsense. I legit do not see a resolution in your previous post, I see you posted some information on diagnosing, but no fix. I did a google search and found that 2.1.28 was updated 2.23.22 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262133 But I do not see an update for opnsense or how to get this fix.

"I can't vouch for third party code included here including squid (see above), but it's a relatively safe bet that when we do not configure SASL use from core that the vulnerable code is never used by us, even indirectly." - This seems pretty self-explanatory to me.

2

21.7 Legacy Series / Re: Namecheap with DynDNS receives "unknown response" after upgrade to 21.7

« on: November 29, 2021, 08:41:12 pm »

Same here, did you hear already something from namecheap?
Do you have a ticket number? If needed / wanted I'd submit one or two more at namecheap (company and private account).

I just asked the rep on reddit and they said they didn't open a ticket. If you have the ability, that would be great. I fear without one, this will get sidelined from them.

3

21.7 Legacy Series / Re: Namecheap with DynDNS receives "unknown response" after upgrade to 21.7

« on: November 25, 2021, 07:22:44 pm »

This means the issue is on namecheap's end, as I understand it.

I already brought this up to a namecheap rep and they said they're investigating.
https://www.reddit.com/r/NameCheap/comments/qz1mjf/namecheap_dynamic_dns_returning_utf16_encoded/hljqzja

4

21.7 Legacy Series / Re: Namecheap with DynDNS receives "unknown response" after upgrade to 21.7

« on: November 20, 2021, 10:27:02 pm »

Can confirm, exact same issue here!

Thanks for chiming in! Seems like an issue with namecheap or the dyndns package then.

5

21.7 Legacy Series / Re: Namecheap with DynDNS receives "unknown response" after upgrade to 21.7

« on: November 20, 2021, 08:31:39 pm »

It does update the IP in namecheap, but the "cached IP" in opnsense shows N/A.
Also, there are other dyndns clients plugins for opnsense? I'd rather keep it on my gateway.

6

21.7 Legacy Series / Re: DynDNS receives "unknown response" after upgrade to 21.7

« on: November 20, 2021, 08:11:55 pm »

So, I started with a fresh install, imported my config, and got the same error.

Then I removed my dyndns config entirely, and added my namecheap account again. Issue immediately returns after save and force update. Maybe namecheap changed something in their response?

7

21.7 Legacy Series / Namecheap with DynDNS receives "unknown response" after upgrade to 21.7

« on: November 19, 2021, 05:08:52 pm »

I recently upgraded from 21.1 to 21.7.5. I have one domain set up with namecheap, and recently received a pop up on the lobby page about an error.

The error was:

Code: [Select]

[19-Nov-2021 11:02:30 America/New_York] PHP Warning:  simplexml_load_string(): Entity: line 1: parser error : Document labelled UTF-16 but has UTF-8 content in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[19-Nov-2021 11:02:30 America/New_York] PHP Warning:  simplexml_load_string():  in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[19-Nov-2021 11:02:30 America/New_York] PHP Warning:  simplexml_load_string():                                      ^ in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
I submitted this error report and then tried forcing dyndns update manually to watch the log. Everything looked fine except for the final line:

/services_dyndns_edit.php: Dynamic DNS: (Unknown Response)

Is this something that got broken during the upgrade from 21.1? Should I consider wiping my dyndns settings and putting it in fresh?

8

21.1 Legacy Series / Re: Webgui fails to start after upgrade to 21.1.3

« on: March 12, 2021, 06:21:30 am »

Signs pointed to a corrupted filesystem, how that ended up happening, I'm not sure. So let's blame it on my cheap SSD.

System is back up after a complete reinstall on a new disk.

9

21.1 Legacy Series / Webgui fails to start after upgrade to 21.1.3

« on: March 11, 2021, 10:40:50 pm »

After upgrading from 21.1.2 to .3, I got error 503 in my browser.

Here's the log from /var/log/lighttpd.log:

Code: [Select]

Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.332) child signalled: 6
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.601) gw-backend failed to start: /usr/local/bin/php-cgi
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.603) If you're trying to run your app as a FastCGI backend, make sure you're using the FastCGI-enabled version.  If this is PHP on Gentoo, add 'fastcgi' to the USE flags.  If this is PHP, try removing the bytecode caches for now and try again.
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.1061) ERROR: spawning gw failed.
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.475) unlink /tmp/php-fastcgi.socket-0 after connect failed: Connection refused
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.332) child signalled: 6
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.601) gw-backend failed to start: /usr/local/bin/php-cgi
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.603) If you're trying to run your app as a FastCGI backend, make sure you're using the FastCGI-enabled version.  If this is PHP on Gentoo, add 'fastcgi' to the USE flags.  If this is PHP, try removing the bytecode caches for now and try again.
Mar 11 16:06:10 OPNsense lighttpd[29627]: (gw_backend.c.1061) ERROR: spawning gw failed.
Mar 11 16:06:11 OPNsense lighttpd[29627]: (gw_backend.c.475) unlink /tmp/php-fastcgi.socket-1 after connectCLOG▒▒▒▒root@OPNsense:~ #
I've attempted to roll back with opnsense-revert, but now I just get error 500. Not sure what to check at this point. It passes traffic, so I'd prefer to attempt the fix the issue with lighttpd/fast-cgi before resorting to a complete reinstall.