Difficulty browsing to 192.168.1.1

[rparker-ppl]

Hello,

I'm not sure if anyone else has seen this or can help? Recently (like within the last month or so I think) I am having real issues browsing to the Rosetta when connected from my iPhone 7, or Samsung S10, or Samsung TabA8 or a Window 10 computer (via the Rosetta local wifi). When I open the default browsers and try to go http://192.168.1.1 it's coming up with "This site cannot be reached" and trying to redirect me to https://192.168.1.1 (https://192.168.1.1/index.cgi) even though I'm typing in http. In fact I'm using a bookmark that has historically worked. Sometimes I can get into the main home page but then when I click some of the buttons (like tracks and radar) it then tries to redirect me to HTTPS and I get the site cannot be reached error. Sometime when I click home, that's when I get the error. It's a bit sporadic

PilotAware is working when I connect from SkyDemon on my tablet and iPhone  and  "go flying" (which is great!!) but it was a real pain today as I was flying a different aircraft and I wanted to put the hex code into the profiles and it was very difficult between errors

I've tried clearing caches, manually typing in the full URL, etc., and like I say it's across a wide spread of devices. I'm guessing there's no port 443 connection on SSL but I don't know why it keeps trying to redirect in the first place

I'm using version 20200906 and my license doesn't expire until 2025

Thank you for any help and advice

Kind regards,


Richard

[steveu]

You say you have used the default browsers, which were? Have they been updated recently? This may have broken things.

Edge, Safari, something Samsung has meddled with in Android? Chrome still allows an IP address to be entered...

The mood within browsers is not not let you use insecure http anywhere, although how you get a certificate for a private network is a bit beyond me...

You may need to look in the browser for some setting to allow http?

Alternatively, with the Windows 10 PC, you can issue the command

Code: [Select]

arp -a
from the Command prompt and you should see 192.168.1.1 in the list?

If you then configure Win 10 networking to allow ping on the local network, you should then be able to

Code: [Select]

ping 192.168.1.1
If that works then the browser is doing something annoying.

You may also find that turning off mobile data solves the problem, as devices are sometimes confused by looking for a private network address on T'Internet.

[exfirepro]

Richard,

The problem is you are trying to access http://192.168.1.1 - which tells the device the URL is on the internet (which it isn’t) which is why the devices say they can’t connect to it.

Changes to iOS and Android have mad3 the issue worse by trying to direct you only to secure internet sites (prefixed https://)

The correct address for the PAW Screens is simply 192.168.1.1 without the http:// or the https://

Regards

Peter

[rparker-ppl]

Hello both,

Thank you for your responses and apologies for my delay in getting back to you.

I have checked connection from my laptop (via arp and ping, as well as telnet on port 80) and it all seems to be present and correct. I'm using (from Windows) Edge or Chrome 90.0.4430.93, and from my Samsung Galaxy TabA8.0 (my main device I use in the plane) I'm using Samsung Browser v14.0.1.62

I tried the cache clear and just entering 192.168.1.1 (without the protocol prefix) into the browser and sometimes it worked and sometimes it tried doing the redirect. It's like if it fails once, then it always tries the redirect (I guess until I clear the cache again?)

I do feel like this is something to do with the browsers trying to be "too smart" for their own good as opposed to a network issue, but I just wanted to check - and also, I guess if more browsers start to do this, it might become an issue for more PAW users. It is possible to create a self signed certificate in Linux and bind it to port 443 in Apache, but unless it's from a proper signing authority, the browser will still complain!

Kind regards,


Richard

[exfirepro]

Hi Richard,

Thanks for the update. Yes it can be a real pain. Both Apple and Android (as you are no doubt aware) introduced new ‘security’ improvements over the past few months, which caused major headaches - especially for the likes of SkyDemon, who had to develop ‘work-arounds’ until the software developers got round to fixing the issues they created. Of course many folks weren’t even aware of the issues until flying resumed.

I was chatting to one of the tech guys just the other day about the very issue you have raised. They are working on potential long-term solutions - until Apple/Google change everything again of course 

Regards

Peter

[neilmurg]

........
Thank you for your responses and apologies for my delay in getting back to you.
........

Hi, Are you double checking that your devices are using the Pilotaware WiFi signal before looking for 192.168.1.1 ?
If there's another WiFi around that they like, they may not automatically jump to the Pilotaware one. And you should tell the devices to select the Pilotaware WiFi automatically when present.
All the Best!