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:
[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?
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?
Does the update work anyway? There are other dyndns services out there... ;-)
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.
no, I mean there are other dyndns service providers out there, look drop down menu under "Service type" in Services -> Dynamic DNS
Or try "Service type" -> Custom and enter the credentials you have...
Can confirm, exact same issue here!
Quote from: ezhik on November 20, 2021, 10:19:04 PM
Can confirm, exact same issue here!
Thanks for chiming in! Seems like an issue with namecheap or the dyndns package then.
Following, found the same thing.
Same issue here and it generates a dump file every time has well, have submitted to the team.
Hopefully a fix soon
There should be a log line in the system log starting with "Dynamic DNS (namecheap): PAYLOAD". What does it say?
This seems like namecheap changed the response since the code hasn't changed or something with PHP 7.3 -> 7.4 migration. Not sure.
Cheers,
Franco
This is what my one says :
2021-11-19T01:11:00 opnsense[13440] /usr/local/etc/rc.dyndns: Dynamic DNS (domain.com): PAYLOAD: <?xml version="1.0" encoding="utf-16"?>
I also get this just about every day when I log into the web Gui :
PHP Errors:
[25-Nov-2021 00:38:35 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
[25-Nov-2021 00:38:35 PHP Warning: simplexml_load_string(): in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 00:38:35 PHP Warning: simplexml_load_string(): ^ in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 00:38:42 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
[25-Nov-2021 00:38:42 PHP Warning: simplexml_load_string(): in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 00:38:42 PHP Warning: simplexml_load_string(): ^ in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 00:38:42 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
[25-Nov-2021 00:38:42 PHP Warning: simplexml_load_string(): in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 00:38:42 PHP Warning: simplexml_load_string(): ^ in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 01:11:00 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
[25-Nov-2021 01:11:00 PHP Warning: simplexml_load_string(): in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
[25-Nov-2021 01:11:00 PHP Warning: simplexml_load_string(): ^ in /usr/local/etc/inc/plugins.inc.d/dyndns/phpDynDNS.inc on line 1502
I would expect these errors to repeat if the issue is indeed not solved ;)
Please try the patch at https://github.com/opnsense/plugins/issues/2666#issuecomment-979154701
It's really just a POC to see if the remote end broken this.
Cheers,
Franco
Nice! The patch works for me.
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
It might be an improved validation with some recent PHP 7 update so that the error was there quite a while, but in any case our side is not a fix indeed.
Cheers,
Franco
Thank you Franco, applied the patch and the issue has been resolved.
Great work!
Not resolved, just diagnosed and temporarily fixed. As soon as they fix their file to emit UTF-16 characters instead of UTF-8 it will break again on our end...
Cheers,
Franco
Quote from: eschmacher 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
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).
Quote from: katamadone [CH] on November 26, 2021, 09:02:16 AM
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.
I just opened a ticket with them. Will post back when I get updates
Any updates?
so the plugin update, seems to be working now! Thank you all!
Sure, workaround is applied now in the release, but it could break again so let me know if that happens. :)
Cheers,
Franco
Quote from: lcasale on November 30, 2021, 04:55:55 AM
I just opened a ticket with them. Will post back when I get updates
Did you hear something? Or do you have a ticket number? So I would file one, too - with reference to your ticket.
I am not sure if this is the correct thread, but I post it anyway.
I have also issues with the dyndns service. I use freedns. Since the last update of the package to version1.27_1 the update of a change IP doesn't work anymore. Please find the log entries below:
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): (Unknown Response)
2021-12-16T01:11:02 opnsense[79456]
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): PAYLOAD: Error 404 : Page not found
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): Current Service: freedns
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): _checkStatus() starting.
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org via freeDNS): _update() starting.
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): running dyndns_failover_interface for wan. found igb0
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): 80.108.241.82 extracted
2021-12-16T01:11:00 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS: updatedns() starting
The service status shows the value "n/a" in the field "Cached IP". This is awkward as the service seems to extract the correct IP according to the logfile...
Could this also be connected to the issues with the last version 1.27_1?
Really not a great place to post FreeDNS issues in well-known Namecheap topic.
Cheers,
Franco
Quote from: franco on December 16, 2021, 11:13:32 AM
Really not a great place to post FreeDNS issues in well-known Namecheap topic.
Well, I thought that this might be a general issue of the dyndns package independent of the DNS provider. Should I better create a new topic?
Yes, otherwise it makes it harder to keep track of things.
Quote from: marjohn56 on December 16, 2021, 12:51:28 PM
Yes, otherwise it makes it harder to keep track of things.
Done. Please delete all my posts in this thread including this one. Sorry for the inconvenience caused!
No worries, thanks