@stephenw10 i just went ahead and reinstalled this morning. i appreciate the reply.

@BassStation70 yep. PfB can’t spoof HTTPS certs with valid certs so your browser will show the warning.

Re: still working, could be DNS caching on your device, or a list update, etc.

Ah, it looks exactly like this: https://redmine.pfsense.org/issues/14685

So try a few rounds of fsck as mentioned there. Or switching to ZFS would also prevent it.

Steve

Did you try the known fix for that? https://redmine.pfsense.org/issues/14207#note-2

https://docs.netgate.com/pfsense/en/latest/hardware/tune.html#rate-limiting

Steve

@Gertjan @stephenw10

Yes, to both of you guys. I was tired and just trying to get things done. I made a backup in the UI and it was larger than I had thought it would be.

Wanted to thank all of you for your help, and let you know I was/am not meaning to be rude. I wasn't able to get on yesterday, as my central air went out and as I don't have just over $12k to replace it, I had to do what I could to get it running again. Took about 7 straight hours.

As for my firewall, I have not messed with it anymore, as I just haven't had the time. I cannot reproduce the issue, so I cannot submit it as a bug report. I am sure it is something stupid I did, while up all night after playing COD or something like that. When I first got my box, I had only the basic understanding of python, very basic, and had forgotten most of php, and the networking I did was 20 plus years ago. So it's been a bit of a challenge for me. You all have been VERY helpful, and again, thank you!

Hmm, so it tries to connect via em0 before it has an IP and fails. Then retries successfully?

That's what you would see if the device loses it's default route or has an invalid default route.

Check Diag > Routes when it happens.

Make sure the default gateway in System > Routing > Gateways is set to WAN and not automatic.

Steve

@NollipfSense said in Register DHCP WAN address with unbound?:

I found it best also to have a real domain (often a $10/yr cost)

Exact.
And it comes with a free bonus : free certificates.

@stephenw10 said in Questions about log messages:

Add a note to that bug report.

It's more of an issue because sshguard spams the system log at rotation IMO.

I updated that bug report and created another one for the mangled link-local addresses.

https://redmine.pfsense.org/issues/14692

Checked the connection last night and this morning again, confirmed it's still good. So, I believe this was the issue 100%.

Glad I can go home with no worries. Thanks guys.

@Khoomn oh so you won't be using the dumb switches then?

@michmoor said in interface rename causes brief outage:

Now that i think about it, i think its related to my ticket - https://redmine.pfsense.org/issues/14483

This seems familiar. Applying any changes to an IPsec config even if its phase 1 results in all FRR neighborships flapping.

That should be logged if it's happening.

@stephenw10 Now that 23.05.1 and 2.7 have been released, is it back on the timeline?

Ah, that would do it! 👍

@Gertjan @stephenw10

Thank you for the support. I received the device at my office. So tried all possible commands, but the web gui failed to show up. I also did factory reset to default but that didn't help. Finally I have decided to reinstall the system.

Definitely not the 1100 internal switch. But, yes, could be a bridge somewhere if you have any defined. Bridges in pfSense do support STP.

@mrrobot . I managed to solve the problem, but what exactly is going on? I can't say.
Change DNS Resolution Behavior to "Use remote DNS Servers" and put 9.9.9.9 as your first DNS server.

Open a ticket with us to get the link: https://www.netgate.com/tac-support-request

@jimp said in HAProxy error after upgrade to 23.05.01:

If you still get this try, moving from haproxy-devel to haproxy. The haproxy-devel you were on in past versions is now haproxy.

The version of haproxy on 23.05.1 (now) has the same PHP/package code as haproxy-devel but haproxy-devel is now on an even newer base version of haproxy binaries that may have other problems as it hasn't been tested as much (if at all).

Swapping to HAProxy fixed the issue - thank you.