I recently got the Flint 3 and it arrived with firmware version 4.7.13.
I am having the problem accessing the web gui/luci using mozilla/Google chrome (it just shows a white page and sometimes just 'loading' until connection fails). I tried factory reset the router and it worked after a few minutes but with no luck after. I downloaded the stable firmware 4.7.11 and it worked for a day and the issue persisted. I cleared cache and cookies from web browser with no luck. I tried using HTTP/S to access web gui with no luck. The GL app works pretty well. I just wanted to bring this to your attention to see if this can be fixed in the future stable version firmware or if others are having the same issue.
Do you use any anti virus software on your PC? Try to disable it, since the TLS cert of the router will always be invalid - this might raise some alerts or cause this issues.
I do have anti-virus installed. I uninstalled it, restarted computer and issue still persists. I never had this issue with the anti-virus installed with the Flint 2. Upgraded to Flint 3 for WiFi 7.
Yes, I am able to get an ip from my router. I've been trying to connect via phone(wireless), desktop(ethernet) and laptop(wireless) to no avail.
I will send you a PM when I figure this out. This is my first time in the forum
Strange... very strange. Okay, let's skip the GUI aspect for the moment. IDK what OS you're on but if Windows, you're going to need a SSH client. I reccomend MobaXterm. It's free.
Switch to Ethernet & ssh [email protected]. You should see something like this:
Yes, I can connect to the router via SSH and it works. Im currently using Flint 3 and everything is working but I cannot access the web gui. When I factory reset router, it works for a few minutes then it gives me a timeout.
dropbear is the ssh server you're using. nginx.conf -g would tell us the nginx web server for the GL.iNet web ui is at least running. uhttpd would indicate a seperate web gui for the underlying OpenWrt, LuCI, is running.
Okay, the processes look as expected. Let's see if anything is being served by nginx. You'll need to opkg update && opkg install curl first. Then run curl -k https://127.0.0.1:443. You should have output similar to:
curl -k https://127.0.0.1:443
<!DOCTYPE html><html lang=""><head><meta charset="utf-8"><meta http-equiv="Cache-Control" content="no-cache,no-store,must-revalidate"><meta http-equiv="pragma" content="no-cache"><meta http-equiv="expires" cont
ent="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.i
co"><title>Admin Panel</title><link href="/js/app.6d7e8027.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 t
o continue.</strong></noscript><div id="app"></div><script src="/js/app.6d7e8027.js"></script></body></html>
Then test curl -k https://192.168.8.1:443. The results should be the same. Both are for the GL.iNet Web GUI server.
Also try to load up https://192.168.8.1/cgi-bin/luci via your preferred web browser, in private mode. That should get you to LuCI.
I'm wondering if the GL.iNet's reliance on so much JavaScript isn't causing an issue/crashing your web browser from properly rendering pages. Stranger things have happened.
Very strange. LuCI is more light weight than the GL GUI. I'd expect it to load.
Do you get anything with curl -k https://127.0.0.1:8443/cgi-bin/luci &/or curl -k https://192.168.8.1:8443/cgi-bin/luci? The result should be the same.