Yup, exactly just recover it during the install or at boot afterwards using the External Config Locator.

@provels said in NTP driving me crazy: offset -1410.220612 sec: They say the man with 2 watches never really knows what time it is. That's why you pool them up

Ok i'll write you privatly

@Gertjan Yes these two are the ones I meant by saying "default". but yeah you are absolutely right about the others generated by other packages. @stephenw10 Thanks for the info dear

What widgets do you have on the dash? Did you try the suggested patch to revert the widget refresh method?

@stephenw10 said in How to handle Crash-Report: Is this the first time you've seen it? Yes, it was first time. I do use pfsense since mid June 2024. So not for very long

Mmm, that is probably the way to go. Those scripts are expected to be run as root. Curious that it changed in 24.11 though.

@stephenw10 this is what I was looking for thanks a lot

I haven't been able to replicate this so far. Changing the name of the WAN or editing other values on it doesn't by itself appear to cause a problem. It must be some combination of things or some unique config.

If its actually being used you would see a bunch of logs indicating the new device when that module is loaded.

Well yes. Where is pfSense running in that case? If it's in AWS then you need to use the elastic IP assigned to it there. I had thought you were using the AWS VPC wizard remotely.

@stephenw10 Got it. For some reason it didn't like Brave (my usual browser). Switched to ungoogled chromium and it worked fine. Restored my backup and I'm waiting currently as it reinstalls packages. Thanks for your help.

@zennb1 Cool, now all you have to do is try to figure out a use case for 8 Gbit. I can't say I have found any clear live use for my 10G connection... The best I think I have seen from Steam or Battle.net is 2.5-3 Gbit, but most of the time it's below 2... For consumers, I think 2.5 may be a good top tier option, also because 2.5G switches and devices are so much more affordable.

@viragomann i do really appreciate your help finally it worked for me. my problem was in the port 8080 with TomCat apache, i just changed the port to 8081, reboot the server, and its worked. by the way, it's working on both as Action & Backend pass thru just fine again, thanks a lot @viragomann

Hmm, well that shouldn't happen. Can you make a manual backup successfully? In Services > Auto Configuration Backup > Backup Now?

Hmm, so to be clear it tried to upgrade and then you ended up with no branches showing and the pkg error from repoc? And after removing some packages repoc returned cleanly and the pkg repo branches returned? How many packages did you have installed? The bug that should be fixed in 24.11 was caused by the package list sent by repoc being so long it overran the allowed size.

What do you see? Anything? You see the virtual com port when you connect the USB cable?

@EricAiken Not really clear, what you want to achieve. Created a CA Created a server cert Created a RAS user. (using that CA) Created a openvpn server. using the CA and the server cert After you did this properly, the clients, who have assigned certificate issued by this CA should appear in the client export. If they don't recheck the certs and server settings. Tried creating a client, but only get peer-to-peer options. OpenVPN Clients on pfSense are ever meant for peer-to-peer connections and have nothing to do with the client export. The later is only for users who are entitled for a remote access servers.

Testing it with as basic a config as you can would be a good test. Hard to imagine it using enough additional power over 24.03 to trigger a PSU issue though.