![]() This should be fixed by Netgate so that already deployed units using NO-IP Dynamic DNS, that upgrade to the latest PFSense, don't stop working unexpectedly. Maybe someone can go back and see how the username was encoded in the previous working versions of PFsense. If it doesn’t open up, the issue lies on the websites’ end.If so, in your Dynamic DNS settings of PFsense, what is the format of your NO-IP username?Īll of my PFSense units have been configured, for years, using the following format, which was the correct format at the time they were configured (and is still valid to NO-IP): has changed in the latest versions of PFsense that appears to prevent this previously working format from working. Check if other websites are working and verify it by opening the site in another browser. Important Note: Some websites might also throw this error, either it is caused due to a faulty internet connection or due to an error at the website’s end.
0 Comments
Leave a Reply. |