How to return to "old" interface?

rloeb

Upgraded to 26.07, turned on Nexus, interface makes no sense. How do I get back to previous interface? Attempt to connect at :80 address fails.

cybrnook

As far as I understand, Nexus doesn't "take over" the old interface, it runs alongside it. When I had Nexus enabled, all I had to do was navigate to https://192.168.1.1/8443/login while the php interface remained available at https://192.168.1.1/

With that said, I also disabled Nexus for now.

AndyRH

@rloeb said in How to return to "old" interface?:

:80 address fails

80 or 443? Mine runs on 443.

rloeb

@AndyRH Times out on :443 and :80. Only responds at :8080 which then switches to :8443.

johnpoz

@rloeb and was your old gui running on 443?

Go into the new gui and check..

The php gui I had running on 8443, so I ran the new gui on 9443

The old and new nexus are meant to run along side each other - but if you have one setting on the port the other is running on, then yeah going to be an issue.

rloeb

@johnpoz Old GUI was running on :80, e.g., http://192.168.0.1. New GUI is on :8443, although I'm getting there from :8080. Desperately need to get back to old GUI to make some changes to keep users operating...

Rog

johnpoz

@rloeb so you didn't have https enabled on the old gui? 80 was only used to redirect to the https port. Unless you did not have https enabled.

I would suggest you use the new nexus gui to validate your old php interface settings.

But they run in parallel. Unless you are stepping on the ports

luckman212

The legacy PHP interface + Nexus can definitely coexist (I use them both on my system). Do you have console/ssh access?

If yes, drop to an sh shell and copy & paste the output of the command below:

for x in webgui/protocol webgui/port pfnet-controller/http_port pfnet-controller/https_port; do echo "$x: $(read_xml_tag.sh string system/$x)"; done

example
79a730b5-547f-4631-a859-37d589292a19-CleanShot 2026-09-01 at 11.56.18.png

then, make sure your FW rules are allowing access to those ports from LAN or whatever interface you're connecting from…

johnpoz

@luckman212 said in How to return to "old" interface?:

make sure your FW rules are allowing access to those ports from LAN or whatever interface you're connecting from…

Nice script cmd - and this comment reminds me to check redmine. If you enable the new nexus gui I wonder why this port isn't added to the antilockout rule..

See my example from @luckman212 I have the http redirects disabled, and no port is shown

[26.07-RELEASE][admin@sg4860.home.arpa]/root: sh
# for x in webgui/protocol webgui/port pfnet-controller/http_port pfnet-controller/https_port; do echo "$x: $(read_xml_tag.sh string system/$x)"; done
webgui/protocol: https
webgui/port: 8443
pfnet-controller/http_port: 
pfnet-controller/https_port: 9443
#

rloeb

@luckman212 Don't have console access. Can set it up, but the device is on another floor and I'm slammed this morning because I can't get into pfsense properly. New interface makes no sense! Can't even find how to reload from backup... Horrible interface!

rloeb

@johnpoz said in How to return to "old" interface?:

for x in webgui/protocol webgui/port pfnet-controller/http_port pfnet-controller/https_port; do echo "$x: $(read_xml_tag.sh string system/$x)"; done

Bad : modifier in $ ' '.

johnpoz

@rloeb you have to run sh first.

As to get to backup/restore in the new gui

I wouldn't say this

@rloeb said in How to return to "old" interface?:

Horrible interface!

Its a bit rough around the edges, and needs a bit of polish - but sofar it seems have the important bits.. Remember this is designed to manage multiple pfsenses.. Why the front page doesn't have the menus your familiar with.

It is night and day faster than the old gui that is for sure.

rloeb

@johnpoz
webgui/protocol: http
webgui/port: 8080
pfnet-controller/http_port:
pfnet-controller/https_port:

What is pfnet-controller???

When I connect on :8080, it switches immediately to :8443 and I can login with my previous credentials. But...I desperately need to get to the old interface to make some rule changes to keep the business functioning,

johnpoz

@rloeb said in How to return to "old" interface?:

What is pfnet-controller???

this is what runs the new gui.

Looks like your old gui is running on the same 8080 port that the new gui http redirect runs on - since you have no ports listed I assume they are just the default for the new gui 8080 redirect and https 8443.

I would suggest you edit these ports in the new gui. You can change both the old php gui, and the new gui ports.

I would take it from that output that you changed your http old gui to 8080, never enabled https. And now your new gui default redirect is stepping on your old gui http port. Correct them to how you want them in the new gui so they do not step on each other.

rloeb

@johnpoz Thank you. I believe I now know how to get back to the old gui, but that will require rebooting pfsense. Can't do that now because it will kill dozens of user sessions.

johnpoz

@rloeb why would you have to reboot - just change the old gui port in the new gui to something other than 8080, say 8181 -- once you get into the old gui you can alter the ports the new nexus runs on and make sure you are not stepping on ports. Not sure you would have to reboot to do this?

rloeb

@johnpoz Because it's refusing to accept my login credentials...

johnpoz

@rloeb thought you said you were logged in? how is a reboot going to fix that? if you have console access you can reset the password, do you have ssh access?

rloeb

@johnpoz Changed GUI port to 8181 as suggested. The old sign in interface page is displayed. When I enter my username and password, it blanks the page and returns to the login screen. No error message, just new login screen.

johnpoz

@rloeb restart the gui from the console - option 16 I believe.