-
Notifications
You must be signed in to change notification settings - Fork 11
HINT can’t find gateway #84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just checked further and it does work on iPhone; just not my iPad. |
I’m having the same issue on my iphone. HiNT was working fine for several days, but today, it didn’t seem to be updating, so I closed it and reopened, and it couldn’t find the gateway. Next, I uninstalled and reinstalled it. It still can’t find the gateway. The IP address, username, and password all are correct. |
Found and fixed the problem by turning off VPN. HiNT is working fine now. Great app; thank you for developing it and making it available. |
Hello, I recently downloaded hint after an iPhone update prevented me from accessing the divices on my tmobile fast 5688w 5g gateway. It was saying no devices found despite being on the network. Up until 2 weeks ago, I could access my gateway away from home via cellular network thru hint, now it refuses to connect saying gateway not found. I can only connect when home, which doesn’t help me monitor attached devices such as pet cam and tv for my senior cat. When app does connect, it only gives the option to look, without the option to control connection for devices or anything else I have deleted and reinstalled to my iphone 11 operating ios 18, turned off vpn, and it still doesn’t work like it did when I first installed the app. What happened? I don’t have a side menu ect, not even the ability to turn snapshots off and on ect. |
HINT says it can’t find T Mobile gateway when I try to sign in. What do you suggest? I did the common things like trying to reboot the router, rejoin the Wi-Fi network that the routers on, and so forth. Nothing seems to work.
The text was updated successfully, but these errors were encountered: