OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of eschmacher »
  • Show Posts »
  • Topics
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Topics - eschmacher

Pages: [1]
1
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?

2
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.

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2