Dynamic ddns (no-Ip) causing pfSense crash?
I normally have to start all my post by stating that this is a beefy dell r210 server with 8 cpu and 4 cores and 32 gigs of Ram with a quad 10gig nic. So it’s really it’s a powerful box. I just used it for a big event and it ran incredibly smooth. But now getting it ready for another event it has been behaving weird. I was at first having a problem with the gui just being completely sluggish and just hanging whenever the main page would load and it would take about 1 min or so just to switch between pages. And sometimes would never finish “generating cpu usage” on the main screen. After playing with the dns that problem faded. But last night trying to configure dynamic ddns with (no-Ip). Never got it to work by the way. But during that process the whole pfSense box just froze and I tried reboot the web configurator through ssh and it never came back. I was only able to get it back by reboot the whole box. Any ideas on what happened or advice on how to look for what the problem could of been.
When this happened there was not even one client on the network it’s been just on my work bench.
Gertjan last edited by Gertjan
First things first : the bigger the system, the bigger the chance something goes wrong.
Issues with "no-ip" are quiet common, often seen on this forum. For different, non common reasons (this somewhat excludes no-ip and pfSense. and the route between them ....)
IMHO : Setting up a no-ip dyndns account will not / can not crash your pfSense.
"Something not working" is often a DNS issue, and DNS issues can produce a slow GUI access, it won't crash your pfSense.
No need to play with DNS. The out of the box settings are perfect. That is, I know it will work.
I advise you to have a look at the logs for more information.
But during that process the whole pfSense box just froze and I tried reboot the web configurator through ssh and it never came back. I was only able to get it back by reboot the whole box
Restarting a web server without getting any reactions, and it brought down the system, that was a symptom, not the reason.
I would checks the basics right away : IP / network gateway ok ? On both sides ?
Can you ping the NIC / IP of pfsense from your device
Can you contact pfSense over SSH - or the console access ?
What does 'top' has to tell you ? the web server, nginx, is running ? unbound is running ? Can you do some dns look up on the command line ? Any zombie tasks ? Tasks that have eaten all memory ? real time consumed processor time ok ? Free memory ok ? etc etc.
Also : drive ok ?
pfSense up to date ?
Dell R210 : that quiet a "senior" device (but capable, I know, I have two T310 from 2008 still 'doing something not mission critical' - although I withdrew their health care assurance )
@gertjan should i delete the 188.8.131.52 and 184.108.40.206..?
@gertjan I did end up removing the 220.127.116.11 and 18.104.22.168 dns servers.. and no im not on the latest im on 2.5.1