It ends with @sotirone said in 1200 DynDNS Email Notifications Every Night: Sep 17 17:36:11 php-fpm 75704 /services_dyndns_edit.php: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS so the file contains the same IP as the actual WAN IP and the file date is younger as 25 days from now. So there is nothing to do : all looks fine. Another look at : Sep 17 17:39:07 php 8219 notify_monitor.php: Message sent to email redacted OK The mail gets send, but some failure stops the mail from getting de-queued - and it will get send again. So not a dynsds issue, as no further dyndns log lines are shown, but a notification system issue.

@stephenw10 Got it. Thanks again! Switched monitoring IP to the Comcast primary DNS server: 75.75.75.75

If an IPSec P2 config is over-matching it will grab that traffic and send it across the tunnel so it never reaches the DMZ. That affect it whatever the NIC assignment though. It only applies to subnets. Steve

Ah, good catch. I was just going to suggest something must be blocking it upstream. Odd that you were able to ping 8.8.8.8 from a client on LAN though. Steve

@stephenw10 Thanks, it was good to get clarity as to why this is so, and that's OK. ;o)

Ah, good call!

Urgh, well bad news on the hardware but always good to hear support feedback. Steve

Thanks all for the advice. I have set it to 8.8.8.8 and increased the probe/alert intervals.

@bmeeks Thanks so much, adjusted accordingly. This being my first Pfsense setup I guess I am bit nervous, I'm use to working Sophos XG NG's and Junipers completely different animals and with this system going thousands of miles away just want to make sure I am providing them with a secure device.

Hi! Just to close this. Bought another unit and it is now working perfectly. So it was, indeed, faulty hardware. Thanks @stephenw10 and @Patch for the help. Manuel

For example the running firewall users are created from the config file at each boot. So whatever you have on there now is the result of the config that was present at the last boot.

@stephenw10 great, thanks! I will consider doing so. But you know what? The one employee using OpenVPN told me an hour ago that she doesn't even use it anymore! So I might not even need that setup anymore. For my own administrative purposes I can simply start from scratch or even use Wireguard instead. Thanks all for the feedback and help!

@bearhntr Still works, but I'm afraid you'll need to muddle around like I did. Too much to list and not terribly helpful anyway, more of a "wonder if I can do this" exercise.

Thanks! I changed it to a pfSense Docs ticket since it's specifically a documentation change.

@kevs @kevs said in FORGOT PASSWORD IN PFSENSE WEB ADMIN: Because we don't want to reset our firewall and delete all the configuration just to access the admin GUI. That : Menu option 4 : Reset to factory defaults What you want is : Menu option 3 : Reset webConfigurator password

@johnpoz Yes, I understand. Router should not effect the local traffic. The only thing that was changed was the router and it stopped working after that. I added that entry to DNS Resolver and it didn't help. I want to watch movies and listen to music so I'm done messing with it. It's been a couple days of messing with this, I gave up. I don't need the extra hassle but appreciate your help. Thanks.

@louis2 said in Information about status and release plan would be appriciated: Same hold for things like the update server, which is down now for about five weeks. That is probably valid, however again some background and progress info like ^The update server will be offline because "abc" we expect that it to be online again in about "x days/weeks". The development build server was down for updates and has recently been restarted for some internal testing. I would expect in the coming days you will see new builds coming out for both the next release of pfSense Plus as well as Community Edition.

@stephenw10 I used it just as an example.