[SOLVED] No Web GUI Access on GL-MT1300

Hello all, I have had a GL-MT1300 in my possession for a couple of years now and I have been using the stock firmware from GL-iNET. Now I figured I would upgrade it to the native OpenWRT software. Since the GL-iNET firmware is based on OpenWRT, I hoped it would be straight forward. Unfortunately after the upgrade from GL-iNET version 4.3.x (where x = .19 or .25) to 24.10.1, I don't have web GUI access or see any SSIDs coming from the router.

After looking through the documentation:

  • I was successfully able to SSH into the device at 192.168.1.1
    o I can see in the CLI the device has 'OpenWrt 24.10.1, r28597-0425664679'
  • According to the docs, it indicates web access is not included in snapshot builds and I don't think 24.10.1 is a snapshot build, so I should have web GUI.
  • There is also mention for low memory devices, a full LUCI install might fail because of lack of memory and you might need to build your own image (again, this doesn't apply here).
  • Regarding no SSIDs, it looks like this might be disabled by default according to the documentation.

My question is, any idea of why the web GUI is not working when upgrading from GL-iNET version 4.3.x to OpenWRT 24.10.1?
Thanks in advance!

Did you try to keep settings across the upgrade? If so, that would present a problem. Assuming not... let's see the following:

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:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/firewall
cat /etc/config/uhttpd
netstat -plnt

Thank you for the quick reply... now that you mention it, I think I did keep the settings across the upgrade.

The best thing to do is reset to defaults. Do not try to restore a backup from the GL-Inet firmware -- it's not compatible.

Reset and see if that helps.

firstboot -y && reboot
1 Like

Ok I reset to default using your command and I am still unable to access the GUI.

Here is the output of your commands

root@OpenWrt:~# ubus call system board
{
        "kernel": "6.6.86",
        "hostname": "OpenWrt",
        "system": "MediaTek MT7621 ver:1 eco:3",
        "model": "GL.iNet GL-MT1300",
        "board_name": "glinet,gl-mt1300",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "24.10.1",
                "revision": "r28597-0425664679",
                "target": "ramips/mt7621",
                "description": "OpenWrt 24.10.1 r28597-0425664679",
                "builddate": "1744562312"
        }
}
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 'xxxx:xxxx:xxxx::/xx'
        option packet_steering '1'

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

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'

config interface 'wan'
        option device 'wan'
        option proto 'dhcp'

config interface 'wan6'
        option device 'wan'
        option proto 'dhcpv6'

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           xxxx::/xx
        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  xx:xx:xx:xx:xx:xx
#       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 (xxxxx) on wan
#config redirect
#       option src              wan
#       option src_dport        xxxxx
#       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  xx:xx:xx:xx:xx:55
#       option src_port 80
#       option dest             wan
#       option dest_ip  x.x.x.x
#       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  xx:xx:xx:xx:xx:55
#       option src_port         1024
#       option src_dport        80
#       option dest_ip  x.x.x.x
#       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'

root@OpenWrt:~# netstat -plnt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      1961/uhttpd
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1961/uhttpd
tcp        0      0 192.168.1.1:53          0.0.0.0:*               LISTEN      2711/dnsmasq
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1544/dropbear
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      2711/dnsmasq
tcp        0      0 xxxx::xxxx:xxxx:xxxx:xxxx:53 :::*                    LISTEN      2711/dnsmasq
tcp        0      0 xxxx::xxxx:xxxx:xxxx:xxxx:53 :::*                    LISTEN      2711/dnsmasq
tcp        0      0 :::443                  :::*                    LISTEN      1961/uhttpd
tcp        0      0 :::80                   :::*                    LISTEN      1961/uhttpd
tcp        0      0 :::22                   :::*                    LISTEN      1544/dropbear
tcp        0      0 xxxx:xxxx:xxxx::x:53    :::*                    LISTEN      2711/dnsmasq
tcp        0      0 ::x:53                  :::*                    LISTEN      2711/dnsmasq

Just to clear up your questions:

Correct, 24.10 and anything with numbers like that is a release build. The only sysupgrade images built by default without the web gui (LuCI) are main snapshots, that will look like

OpenWrt SNAPSHOT, r29666-7193539c98

when you log in.

Correct again, the radios are off by default because on a clean install, you have not yet set any passwords. If they were enabled by default, you'd be broadcasting a wide open portal until you configure it, which is generally considered a Bad Thing.

1 Like

Based on the configs, it should be working. Try another browser. And make sure you don’t have any vpns active on the machine you are using.

Yes, but in case you do not realise, you will not have the Web Gui that GL-inet provide. You will only have Luci. Depending on where you got the 24.10.1 flash image, you might not be able to access Luci via https (this is the case if you used the Firmware Selector and you have to install an extra package to generate self signed certificates for https to work).

Try accessing http://192.168.1.1 from your browser.
If you tried just 192.168.1.1, your browser might have appended https, so this could be your problem.
You might have to clear the browser cache....

PS. I have an MT1300 here with 24.10.1 and Luci works just fine.

1 Like

Thanks for this... unfortunately I have tried both Chrome on Firefox just to make sure and I still can't access the web gui (I have confirmed it is trying to connect via http vs https and I did clear the cache as well). That being said, I am directly connected between one of the LAN ports on the MT1300 and my laptop via DHCP from the router. I don't have any type of WAN connection to the router right now.

Also, I have was able to capture a screenshot when trying to connect to the web GUI, so you can see how it tries to connect, but then nothing.

PS - here is the link to the firmware I installed:

Cookies and remembered redirects from the OEM firmware might still persist, in your browser. If you have a second browser installed you normally don't use, trying that might make sense - if not, you can first try an incognito browser session, if neither of that helps, deleting cookies and site data for your router should help.

Thanks for this... after trying a different Eth port on my laptop, I was able to connect via the web GUI!
So in the beginning, I had a USB <>Eth adapter and was able to ping and SSH, but couldn't not connect via web GUI. So then I tried going directly to the built in Eth port on my laptop and the web GUI worked :person_shrugging:

2 Likes

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks! :slight_smile: