W8ADA
This is the EXACT same behavior I am experiencing. There has got to be a bug in the firmware somewhere. I have been working with the team here and have firmware version v54 and still no resolution.
W8ADA
I might add to be fair, I have been working extensively with Norbert with regard to the firmware, who has been pretty good about it considering my frustration. I may have an additional hardware issue and they are going to exchange the unit. That's good business; I just fear the issue with the OS2 dropping the Internet browser(s) until you unplug it and plug it back in is in the firmware...
K3SLS
This is the EXACT same behavior I am experiencing. There has got to be a bug in the firmware somewhere. I have been working with the team here and have firmware version v54 and still no resolution.
I'm also seeing the identical behavior, but starting with the V54 firmware update. Previous firmwares always allowed hitting browser refresh, the try again button, or worst case using sharkrf.link for resolution. With V54 I've had to cycle the power on each OS2 to gain http access. The devices behave fine other than browsing...that is they continue to transmit and receive normally.
HA2NON
The recommended way to open the web interface is to use sharkrf.link
G4TKO
Even using RF link will not restore only way is to power off and then it reboots!!
K3SLS
Even using RF link will not restore only way is to power off and then it reboots!!
Agree! There seems to be a timeout issue when one has left the OS2 page and attempts to return sometime later. The OS2 is clearly working because I can transmit to the target room and I can hear all QSOs without issue. It just won't allow a browser connection to the IP (Safari, Chrome, Firefox all have the issue). sharkrf.link finds the UID, but when selected and attempts to go to the IP...same result. It's like port 80 was closed after some period of time.
k7cet
Just now :
First time :
Using sharkrf.link brings up uid input then resolves internal ip ( 192.168.1.2 ) and then stays on loading page .
Second time :
Went back to sharkrf.link ( backspace ) this time after uid it goes to login page - after login it momentarily shows status page then goes to timeout screen .
Third time :
Went back to sharkrf.link ( backspace ) this time after uid it goes to login page in address link ( 192.168.1.2/#login ) but it hangs at a blank page ( no loading message ) - hit refresh and login page comes up - after login - momentary status page then timeout page again .
Refreshing browser while on
http://192.168.1.2/#status
just keeps showing loading message on blank page - sometimes it goes to timeout and sometimes it just hangs there ...
K3SLS
A possible contributing factor is I appear to lose browser connection when a severely over-driven DMR radio lands in a FCS room I'm monitoring with a C4FM radio. That situation seems to cause the OS2 to drop connection to the FCS server and get into a disconnect/reconnect cycle. After a number of cycles, the browser connection freezes.
k7cet
Oh - OK - I understand that you are probably addressing the previous posting where someone said their OS2 lost the WiFi connection . At first I was confused as to how WiFi configuration would possibly contribute to the browser disconnect / login failures when OS2 connection to radio and WiFi continued to operate normally .
As a test - I left my browser logged out - and left the OS2 going for 12 hours . Then I tried login from browser . Good login and it goes to status page .
I will do more test and ask other people to do same test . Leave OS2 going for hours and have browser logged out . Then after many hours, try logging in .
If this test continues to show that browser to OS2 connection only goes bad when browser remains logged into OS2 - then that would indicate that it is problem with OS2 communicating with browser over long time period .
If the browser fails to login after not being connected then the problem would seem to be some core process in OS2 . If the browser ONLY fails connection and logins when connected to the browser for long periods of time then it probably has to do with browser connection interface processes etc . It may be specific to only being connected for long periods to the status page ...
So, do two tests -
Test one - leave browser LOGGED IN and see when it disconnects and not able to log back in to OS2 .
Test two - leave the browser LOGGED OUT and when OS2 has been running for a long time ( 10 hours or more ) occasionally try to log in to OS2 and see if there are times when you are not able to log in and get to the status page and other pages .
If it only happens that login and page access is not affected EXCEPT when browser is logged in and connected for several hours - THEN I think that would show that WiFi is not causing a trouble and indicates that OS2 firmware is having problem with continuous connection / communication with browser .
Also, I just thought of another test - leave browser logged in but NOT on status page .
If just being logged in and not on status page does not cause trouble and only when logged in and on status page causes disconnect and problem of not being able to login again - would indicated that problem is with OS2 connection / communication with status page .
Otherwise if disconnect and login fails happen anytime browser is left logged in and not necessarily on status page would indicate it is problem with connection / communication to web browser no matter what page is accessed .
k7cet
14 hours later - after leaving browser NOT logged in .
I am able to login with no trouble .
I will leave browser logged in on connections page and see if it disconnects and has login failures after many hours .
k7cet
14 hours later - after leaving browser NOT logged in .
I am able to login with no trouble .
I will leave browser logged in on connections page and see if it disconnects and has login failures after many hours .
After several hours - browser is stuck on blank page with loading...
Cannot get to login or any page - stays on blank page .
Go to UID and enter ID - goes to blank page - no login possible .
The problem definitely appears to be associated with the browser being logged in to OS2 for some hours time then disconnect and inability to log in until hardware restart .
In one case, I was able to go to UID and the get to login page - but not beyond that .
In other case, I was able to go to UID, but completing that - would not go to login page - just goes to blank page . ( edit ) After a few minutes, I went back and tried UID page again - this time it did go to the login page and after login got momentary status page then timeout again .
k7cet
I have IPV6 enabled on my router and computer .
Is that the case for everyone else having this trouble ?
I might try disabling that and see if anything changes .
k7cet
After disabling IPV6 - left browser on status page .
Later, found it on login page . Cannot login - hung with busy circle graphic .
Went to UID page . It gave timeout .
That is the first time I have seen that . It usually gets through the UID page and then sometimes gets through the login before hanging or timeout .
G4TKO
it would appear to be a time out issue as if i log in for a few hrs and then log out no problem but if i s
tay log in all day then it will hang up
KI7UBQ
Hello all, just want to say thank you to all the guys that are trying to figure this out as I’m having the same issue also.
Thanks again
k7cet
Hello all, just want to say thank you to all the guys that are trying to figure this out as I’m having the same issue also.
Thanks again
Yes, I also appreciate everyone working on this issue .
It seems that some of the indications have changed for me - I used to get a status page that just hangs there with no response - or sometimes a blank page .
Now I am seeing it at a login page after leaving it on the status page for some time . When I find it on the login page - it will not log in .
Also at times in the past, after a disconnection to the web browser issue, I was able to go to the UID page and it would go to the login page and then after that it would hang and not be able to log in again . Now the UID page never works after timeout issue .
rb95403
I, too, have this problem.
Any help, thanks!
Bob
K3SLS
After wasting a lot of time watching the log without catching a disconnect, I took a different route. Of my three OS2 devices, only the one connected to FCS04/022 (American Ragchew) was consistently causing browser disconnects. Watching the connection activity showed a lot of "dirty data" flowing through that reflector, almost all sourcing from DMR cross-mode connections. Watching the stats showed BER issues, missing and out-of-order packets, and listening demonstrated hot mics/distorted audio. I suspect the "dirty data" has something to do with the disconnects because the OS2 would reboot in the worst cases or disconnect/reconnect to the FCS server. It's also possible the FCS server has issues. Obviously you never want data affecting code integrity!
I switched the offending room to a Wires-x PDN installation which tolerates the "dirty data" better than the OS2. I still hear the audio issues, but no undesired effects on the host machine. The OS2 is now linked to the room (Carolina Link) previously on the Wires-x machine and has not dropped a browser connection.
One additional consideration...since this affects multiple browsers (in my case Chrome, Firefox, and Safari), it should be pretty clear the OS2 is having difficulty with its on-board web server and may very well be related to the data stream.
PS: The log function of the OS2 needs a way to redirect the output to a text file on the connected computer. I tried piping the output of Mac Terminal (both bash and zsh), but that only created a zero length file.
k7cet
Also at times in the past, after a disconnection to the web browser issue, I was able to go to the UID page and it would go to the login page and then after that it would hang and not be able to log in again . Now the UID page never works after timeout issue .
This time after leaving OS2 connected to status page - when I return I am seeing HARDWARE ERROR - red LED indication .
I believe a replacement OS2 may be needed .
Upon rebooting, the OS2 went to Upgrading Wi-Fi module firmware : LED indication for a short period of time . It seemed strange that it only stayed on that LED indication for about half the time that it usually takes to do an upgrade .
I have worked with computer hardware and software for 35 years so it seems probable that it wasn't dong an upgrade and only doing a quality control checksum validation or something .