@hwally Does your ISP device require you reboot it when you change devices?

@stephenw10 Thanks Steve!

I was able to reproduce it.
I'll apply this patch.

PHP errors

PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 2208, Message: Uncaught TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /etc/inc/util.inc:2208 Stack trace: #0 /etc/inc/util.inc(2208): round('', 2) #1 /usr/local/pfSense/include/www/bandwidth_by_ip.inc(172): format_number('', 2) #2 /usr/local/www/bandwidth_by_ip.php(36): printBandwidth('wan', 'local', 'in', '', 'iftop') #3 {main}

Ok got it sorted.. The "IP Passthrough" state wasn't being recognized on ATT's end, and had to be reset by them to get it to apply, even though I rebooted it on my end. Thats what they tell me anyhow...

I suspect a resent power outage we had somehow messed its configuration and reset it or something.. A theory anyway...

Thanks for the responses all, much appreciated.

Also upgrade from 2.4.5p1 --

Outdated signature.. fixed now. thanks..

@cool_corona thank you for the pointer... I shall investigate!

@johnpoz Hm? It doesn't throw any error when this outages happen, but occasionally Spotify is unhappy with my network rules I suppose, telling me to check my network and refuses to leave that screen. I then have to reboot the player, then works just fine again...

@machu-picchu I did exactly this using two VM's on EXSI when I was testing PF latest release.

...or at the console directly.

@bob-dig said in Can't access web-UI after upgrade from 2.7 to Plus 23.01:

Maybe just bad timing on my part but I got me a VPS the other day and am installing pfSense 2.7 on it. After doing the upgrade to plus, I can't access the web-ui anymore. The VPS only has one NIC.

Can I force an upgrade to the latest RC of 23.05 via ssh?

@stephenw10 said in HELP! pfSense is dead after upgrade to plus:

Like you went from CE 2.7 to Plus 23.01?

That's not valid unless it was a 2.7 snapshot from Feb 15th or earlier because of the php change. You should be able to recover by running a full forced pkg reinstall if that is what you did.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall

@spacebass said in registered for pfSense Plus, no upgrade options from CE:

not to be obtuse, but I have a limited amount of time to fill out the same form.

Most likely you have a plug-in that is making it not work -- it has worded in all browsers and on all major platforms internally following your report.

Could be a DNS issue. But, again, we did thorough testing after your report and could not replicate it.

@stephenw10 Thanks :) I'll give it a try and see how it goes.

root@pve2:~# cat /proc/cpuinfo |grep microcode microcode : 0x24000024 microcode : 0x24000024 microcode : 0x24000024 microcode : 0x24000024

@burgerking31337 after I upgraded my Proxmox machine to latest intel microcode (not debian's latest, the actual latest), I never have a single reboot on any VM.

@stephenw10 sounds good. Thanks for checking

It's trying to open pages that don't exist in pfSense. It probably was previosuly connected to something at the pfSense IP and hasn't updated yet.

Hmm, it just keeps running for me in 23.01. You're just viewing the default screen?

@menethoran store.netgate.com have excellent selections and help support the project

Ooops I missed a bunch of replies here. I see you solved it already. Nice.

Yeah, if your WAN connection is actually 1.5Mbps then I wouldn't expect to see anywhere near 1ms to anything external. I assume that's DSL? The 30ms you were previously seeing is probably about right but what was that to?

@mauro-tridici

Most easy known solution : only accept really trusted devices on your pfSense LAN.
From this LAN network, you could connect your own device - that you should trust - and access pfSense. You can even lock down to access to just one LAN IP : the one your device will get when it is connected.

All other users : use another LAN called OPT2. From this OPT2, devices they can do what they want, but they should only be able to contact pfSense over port 53, UDP and TCP. Block the rest with destination .LAN2 IP pfSense.