LuCI unavailable after initial setup

Installed 24.10.4 on a Ubiquiti 6+ without issue. LuCI worked fine. A day or so later without changing anything I'm aware of only ssh is available. There was a firefox update in the interim.Firefox without extensions and defaults with http disabled as much as you can still changes to a secure link the majority of the time, unsure why it attempts occasionally. NIC set to same parameters I believe, but simply 192.168.1.2 and 255.255.255.0

I reset the router and changed the password, but nothing has helped. It feels like my error due to unfamilarity. There's a similar post, without resolution. What might have caused this? I can just reinstall LuCI through ssh, but I don't feel like that's the problem. Thanks.

Let's take a look at the config to see if we can find the issue:

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):

Screenshot 2025-10-20 at 8.14.14 PM

Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall
cat /etc/config/uhttpd
1 Like
root@OpenWrt:~# ubus call system board
{
	"kernel": "6.6.110",
	"hostname": "OpenWrt",
	"system": "ARMv8 Processor rev 4",
	"model": "Ubiquiti UniFi 6 Plus",
	"board_name": "ubnt,unifi-6-plus",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "24.10.4",
		"revision": "r28959-29397011cc",
		"target": "mediatek/filogic",
		"description": "OpenWrt 24.10.4 r28959-29397011cc",
		"builddate": "1760891865"
	}
}
root@OpenWrt:~# cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix ‘redacted’

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	option ip6assign '60'

root@OpenWrt:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc/18000000.wifi'
	option band '2g'
	option channel '1'
	option htmode 'HE20'
	option disabled '1'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'OpenWrt'
	option encryption 'none'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc/18000000.wifi+1'
	option band '5g'
	option channel '36'
	option htmode 'HE80'
	option disabled '1'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'OpenWrt'
	option encryption 'none'

root@OpenWrt:~# cat /etc/config/dhcp

config dnsmasq
	option domainneeded '1'
	option boguspriv '1'
	option filterwin2k '0'
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'lan'
	option expandhosts '1'
	option nonegcache '0'
	option cachesize '1000'
	option authoritative '1'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option nonwildcard '1'
	option localservice '1'
	option ednspacket_max '1232'
	option filter_aaaa '0'
	option filter_a '0'

config dhcp 'lan'
	option interface 'lan'
	option start '100'
	option limit '150'
	option leasetime '12h'
	option dhcpv4 'server'
	option dhcpv6 'server'
	option ra 'server'
	option ra_slaac '1'
	list ra_flags 'managed-config'
	list ra_flags 'other-config'

config dhcp 'wan'
	option interface 'wan'
	option ignore '1'

config odhcpd 'odhcpd'
	option maindhcp '0'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'
	option piofolder '/tmp/odhcpd-piofolder'

root@OpenWrt:~# cat /etc/config/firewall
config defaults
	option syn_flood	1
	option input		REJECT
	option output		ACCEPT
	option forward		REJECT
# Uncomment this line to disable ipv6 rules
#	option disable_ipv6	1

config zone
	option name		lan
	list   network		'lan'
	option input		ACCEPT
	option output		ACCEPT
	option forward		ACCEPT

config zone
	option name		wan
	list   network		'wan'
	list   network		'wan6'
	option input		REJECT
	option output		ACCEPT
	option forward		REJECT
	option masq		1
	option mtu_fix		1

config forwarding
	option src		lan
	option dest		wan

# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
	option name		Allow-DHCP-Renew
	option src		wan
	option proto		udp
	option dest_port	68
	option target		ACCEPT
	option family		ipv4

# Allow IPv4 ping
config rule
	option name		Allow-Ping
	option src		wan
	option proto		icmp
	option icmp_type	echo-request
	option family		ipv4
	option target		ACCEPT

config rule
	option name		Allow-IGMP
	option src		wan
	option proto		igmp
	option family		ipv4
	option target		ACCEPT

# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
config rule
	option name		Allow-DHCPv6
	option src		wan
	option proto		udp
	option dest_port	546
	option family		ipv6
	option target		ACCEPT

config rule
	option name		Allow-MLD
	option src		wan
	option proto		icmp
	option src_ip		fe80::/10
	list icmp_type		'130/0'
	list icmp_type		'131/0'
	list icmp_type		'132/0'
	list icmp_type		'143/0'
	option family		ipv6
	option target		ACCEPT

# Allow essential incoming IPv6 ICMP traffic
config rule
	option name		Allow-ICMPv6-Input
	option src		wan
	option proto	icmp
	list icmp_type		echo-request
	list icmp_type		echo-reply
	list icmp_type		destination-unreachable
	list icmp_type		packet-too-big
	list icmp_type		time-exceeded
	list icmp_type		bad-header
	list icmp_type		unknown-header-type
	list icmp_type		router-solicitation
	list icmp_type		neighbour-solicitation
	list icmp_type		router-advertisement
	list icmp_type		neighbour-advertisement
	option limit		1000/sec
	option family		ipv6
	option target		ACCEPT

# Allow essential forwarded IPv6 ICMP traffic
config rule
	option name		Allow-ICMPv6-Forward
	option src		wan
	option dest		*
	option proto		icmp
	list icmp_type		echo-request
	list icmp_type		echo-reply
	list icmp_type		destination-unreachable
	list icmp_type		packet-too-big
	list icmp_type		time-exceeded
	list icmp_type		bad-header
	list icmp_type		unknown-header-type
	option limit		1000/sec
	option family		ipv6
	option target		ACCEPT

config rule
	option name		Allow-IPSec-ESP
	option src		wan
	option dest		lan
	option proto		esp
	option target		ACCEPT

config rule
	option name		Allow-ISAKMP
	option src		wan
	option dest		lan
	option dest_port	500
	option proto		udp
	option target		ACCEPT


### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
#	option src		lan
#	option src_ip	192.168.45.2
#	option dest		wan
#	option proto	tcp
#	option target	REJECT

# block a specific mac on wan
#config rule
#	option dest		wan
#	option src_mac	00:11:22:33:44:66
#	option target	REJECT

# block incoming ICMP traffic on a zone
#config rule
#	option src		lan
#	option proto	ICMP
#	option target	DROP

# port redirect port coming in on wan to lan
#config redirect
#	option src			wan
#	option src_dport	80
#	option dest			lan
#	option dest_ip		192.168.16.235
#	option dest_port	80
#	option proto		tcp

# port redirect of remapped ssh port (22001) on wan
#config redirect
#	option src		wan
#	option src_dport	22001
#	option dest		lan
#	option dest_port	22
#	option proto		tcp

### FULL CONFIG SECTIONS
#config rule
#	option src		lan
#	option src_ip	192.168.45.2
#	option src_mac	00:11:22:33:44:55
#	option src_port	80
#	option dest		wan
#	option dest_ip	194.25.2.129
#	option dest_port	120
#	option proto	tcp
#	option target	REJECT

#config redirect
#	option src		lan
#	option src_ip	192.168.45.2
#	option src_mac	00:11:22:33:44:55
#	option src_port		1024
#	option src_dport	80
#	option dest_ip	194.25.2.129
#	option dest_port	120
#	option proto	tcp
root@OpenWrt:~# cat /etc/config/uhttpd

config uhttpd 'main'
	list listen_http '0.0.0.0:80'
	list listen_http '[::]:80'
	list listen_https '0.0.0.0:443'
	list listen_https '[::]:443'
	option redirect_https '0'
	option home '/www'
	option rfc1918_filter '1'
	option max_requests '3'
	option max_connections '100'
	option cert '/etc/uhttpd.crt'
	option key '/etc/uhttpd.key'
	option cgi_prefix '/cgi-bin'
	list lua_prefix '/cgi-bin/luci=/usr/lib/lua/luci/sgi/uhttpd.lua'
	option script_timeout '60'
	option network_timeout '30'
	option http_keepalive '20'
	option tcp_keepalive '1'
	option ubus_prefix '/ubus'

config cert 'defaults'
	option days '397'
	option key_type 'ec'
	option bits '2048'
	option ec_curve 'P-256'
	option country 'ZZ'
	option state 'Somewhere'
	option location 'Unknown'
	option commonname 'OpenWrt'

Thank you.

I don't see anything really out of the ordinary here -- pretty close to defaults.

Is this connected to your network?

Or is it only to your computer (and obviously via a PoE source -- in other words: directly through a PoE injector or via a switch with just the two connections to your computer and the AP)?

How are you trying to connect (what address, what browser, etc.)? Does your host have any VPNs running? Or do you have any other network connections on the computer?

After the inital flash I changed the root password and that was as far as I went. I have been stopping the WiFi, VPN, firewall, all on the client side before enabling the nic and connecting to the U6+ with what I'm assuming is the PoE that came with it. I've restarted the computer with all above disabled and it doesn't make any difference. Firefox is the only thing that's unhappy I think. After reading your post I went and tried Firefox again in troubleshooting mode, removed an extenstion, refreshed it with the same result, so it's not a result of anything I changed in Firefox.

Have you tried another browser?

Are you using 192.168.1.1 for the address in the browser?

1 Like

I will, but haven't yet. Just need a bit to figure it out, haven't run anything other than Firefox for a while and don't want to get a blatantly privacy disrespecting browser. I've been out of hardware/software for a couple decades so it'll take me a few to get up to speed. Thanks.

edited to add....

I haven't tried the browser yet, but I took the Starlink router offline and tried from a cold boot. I got a "welcome to starlink" splash screen with a rocket on the page. Really unsure how that's happening since the Starlink router has no power and I am not supposed to have any connectivity to it, only the U6+.

Try clearing your browser cache.

1 Like

It's set to never remember history. It still manages to store a few things, but they are removed almost at every site visit. It's always completely clean when I've tried, at least what I can see.

How about a different computer?

1 Like

I found the reason I started getting the starlink jpg and that was I'd assumed the router reset to 192.168.1.1 when it resets to .20 How it got the jpg without any cache or connectivity is beyond my ability. Anthropromorphic Interface error. So while that went on the router has been alternating white/blue for well over an hour trying a hard reset. A hard reset during this has no effect. Unsure if it's bricked or just takes well over the 3-5 minutes it says on the Unify U6+ page. Something must have been corrupted during the reset. I'll let it run for a while, then try a different 6+ if it doesn't boot.

I've got to get some knowledge back in my brain. Any good references other than the manuals for linux and networking in general you'd recommend? It would seem all search results now only return AI built pages that link to amazon purchases. Many years ago there were many very good sites out there, but I don't recall the names and search engines appear to be full fledged manipulation tools. Likely don't index them anymore if they present factual information. Thanks again.

I'm a bit confused...

From a reset-to-defaults perspective, unless you changed it (which requires building your own custom image), OpenWrt's default address is 192.168.1.1. That means that if you reset the device, it should revert to the .1 address (with wifi disabled and the DHCP server enabled).

On the other hand, if you changed the address in the standard config from .1 to .20, you wouldn't be able to ssh into the device at 192.168.1.1 either.

The 192.168.1.20 address is, however, the default address when you are running the actual Unifi firmware. So if the device was using the .20 address, it suggests that it's not running official OpenWrt.

It might be some kind of OEM bootloader recovery mode.

https://help.ui.com/hc/en-us/articles/360043360253-UniFi-Recovery-Mode

LED flashes white, blue, off as indicated in our LED Status Guide. This indicates your device is ready for TFTP Recovery and you can release the button.
Set a static IP address on your computer to communicate with the AP, which has a default IP address of 192.168.1.20.

Maybe... but the DHCP server wouldn't be active if the recovery mode (TFTP) was enabled. Unless the OP is setting static IPs on the host, or a DHCP server is active on the network that is not the U6+, the host wouldn't have an IP... all things that are confusing about the situation the OP has described.

What DHCP?
I believe the OP mentioned manually set 192.168.1.2 in his original message.

The symptoms seem to match the OEM recovery mode, so that is my guess so far.

Ah... good catch. I missed the manual IP! Yes, I agree.

But LuCI wouldn't work... so if the OP is seeing LuCI, then I'm really confused.

Well the first messages were before the hard reset attempt, so the current situation (with blinking blue/white LEDs) may be different than the situation with SSH access in the first messages.

1 Like

It was at .1 on the first reset and I had a manual ip in the computer. I only changed the root password. At this point it is looping evidently trying to boot. White light, Blue Light, 8 second pause, repeat. I can't recall if I verified the signature, but normally I do.I believed it was coming from here, but that's the way man in the middle works I think. I don't want to just let it run indefinitely because I don't know what it's doing. I imagine at this point it might be a recovery of some type. Don't know if you can force an install or not. I have very llittle time to try to fix it today, but will look later or tomorrow. I'll get back to everyone who posted probably tomorrow, just so you know I'm not abandoning the thread. Thank you.

In theory, you don't need a static IP on your computer -- DHCP is often used. But static vs DHCP on the computer will not cause any of the issues described, as long as the IP address is in the 192.168.1.0/24 subnet and not .1, or .20 (and of course not .0 or .255).

Changing the root password would not cause a boot loop. In fact, it doesn't require a reboot at all.

This is likely in TFTP mode, which would explain the .20 address.

not sure what you mean here.

I think you're in TFTP recovery mode.
My recommendation would be to reinstall the Unifi firmware, then follow the directions again to install OpenWrt.

It was in TFTP recovery mode. Tried one flash from Ubiquiti and it wouldn't work. Went to 6.5.54 and it worked. When you originally ssh the router after the flash you put a key in your ssh hosts file. Then when I try to scp (which for some reason I added a -o switch on the inital flash and cannot determine why). A simple command like this (scp) without any reference can consume hours for someone unfamiliar. In any case, I cannot determine why it now is unhappy about an sha1 fingerprint when trying to use scp or why it needs this plus the the hosts file entry. Rather than assume this is benign I don't want to proceed with my guess on the scp command unless I know it's ok to do so? Thank you,.

This is a good link for the Unify 6+ light status. It's currently in adoption mode.

Unify U6+ Light Status Indicators