I've seen a lot of forum posts saying that you should definitely be able to access the web UI of a Flint 2 in AP Mode, but I am unable to get to mine.
I have one Flint 2 (A) at the point of WAN entry in my home and then another (B) at the end of a Cat6 run for the other end of the house that I've just added. The 2.5G LAN1 of (A) is plugged into the 2.5G WAN port of (B) I plugged it in, turned it on and set it to AP mode.
Functionally, it is fine. I can connect to it, access my home network and the original Flint 2 (A). However it is still broadcasting it's network as GL-MT6000-XXX-5G. I figured I could change this by going into the web UI, so I looked at the web UI of the original Flint 2 (A) and saw GL-MT6000 in the clients list at 172.16.XX.XX. But when I put it's IP in the browser, I get nothing.
Curiously, when I nmap the IP address, I see that it has 80 and 443 as open ports which suggests a web UI should be available. Plus I am able to SSH into it as well. But the web UI simply doesn't want to load. This persists across a reboot. Any ideas?
Thanks for your help. I put in the commands as you suggested and the output is below. But crucially, it has started working? Such an unsatisfying solve as I haven't touched it since I made the post, except to put in this commands. Doesn't seem to me that there's any chance ps or curl could make it jump to life so it must've been something else.
root@GL-MT6000:~# ps | grep nginx
7160 root 9680 S nginx: master process /usr/sbin/nginx -c /etc/nginx/
7321 root 12320 S nginx: worker process
7322 root 11340 S nginx: worker process
7323 root 11340 S nginx: worker process
7324 root 12320 S nginx: worker process
20616 root 1232 S grep nginx
root@GL-MT6000:~# curl -v 127.0.0.1
> GET / HTTP/1.1
> Host: 127.0.0.1
> User-Agent: curl/7.83.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.26.1
< Date: Fri, 07 Mar 2025 09:32:20 GMT
< Content-Type: text/html
< Content-Length: 786
< Last-Modified: Thu, 05 Dec 2024 01:20:08 GMT
< Connection: keep-alive
< ETag: "6750ffc8-312"
< Cache-Control: private, no-store, no-cache, must-revalidate, proxy-revalidate
< X-Frame-Options: DENY
< Accept-Ranges: bytes
<
<!DOCTYPE html><html lang=""><head><meta charset="utf-8"><meta name="robots" content="noindex, nofollow"><meta http-equiv="Cache-Control" content="no-cache,no-store,must-revalidate"><meta http-equiv="pragma" content="no-cache"><meta http-equiv="expires" content="0"><meta http-equiv="X-UA-Compatible" content="IE=edge"><meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,minimum-scale=1,user-scalable=no"><link rel="icon" href="/favicon.ico"><title>Admin Panel</title><link href="/js/app.070fab0a.js" rel="preload" as="script"></head><body><noscript><strong>We're sorry but gl-ui doesn't work properly without JavaScript enabled. Please enable it to continue.</strong></noscript><div id="app"></div><script src="/js/app.070fab0a.js"></script></body></html>root@GL-MT6000:~#
For anyone coming across this with this problem; whilst I couldn't access the web UI, I changed the WiFi details using SSH.
I used sudo vim /etc/config/wireless to edit the file to change the name and password for the WiFi network it was broadcasting. I changed option ssid and option key in two sections, config wifi-iface 'wifi5g' and config wifi-iface 'wifi2g'.