Can no longer log into System Blue Controller, Web Brouser Interface

[W2PJ-WX]

Blitzortung Community:

I ran into an unexpected problem today.  While trying to fine tune gain and threshold settings I lost the ability to log into the user interface of my System Blue controller using edge.
Station ID: 2110
Controller:  19.3
I have FW version 11.0b3

I lost the ability to log into the controller after a system blue reboot.
Anyone seen this behavior before?

The address I was using stored in my favorites was "http://192.168.1.110/index.cgi?action=status    

Trying to log in I get this message on my Edge Brouser and Firefox Brouser:
192.168.1.111 


After trying several times and getting confused... I rebooted manual system blue with the on off switch.  No Luck.
Then rebooted the router.  No luck.

Checked the IP address of System Blue on my LINKSYS router.  I could not find Blitzortung, so I performed a clear network map and another reboot of the router.

This time the router saw Blitzortung (new address  192.168.1.111).  Tried that.  No Luck.

Pinged address from a command window and got the following response:

C:\Users\Owner>ping 192.168.1.111 refused to connect

Pinging 192.168.1.111 with 32 bytes of data:
Reply from 192.168.1.111: bytes=32 time=1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
Reply from 192.168.1.111: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.1.111:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Rebooted computer.  No Luck.

Does anyone have an idea of what my next step might be to resolve this problem?

I read on chat GPT an option to do the following (Steps 4 and 5 below) , but I do not trust it unless there is documentation from Blitzortung with specific instructions and it is the recommended next step.
I hope an expert on the forum can recommend the correct next steps, and if they are complex references to needed documentation, or another thread that explains the next steps in detail.


From Chat GPT:
4. Force a Factory Reset (if needed)
If all else fails, your controller’s web server might have misconfigured settings or crashed.

• Hold down the reset button on the System Blue controller (you may need a paperclip) for 10–15 seconds during power-up.
  
• This should restore default network settings (DHCP enabled).
  

Then recheck your router for the new IP assignment and try again.

---

? 5. Firmware Recovery Option
If the reset doesn’t help and the controller is unresponsive to HTTP but still pings:

• Connect to the controller via USB and use the Blitzortung update tool from their site.
  
• This lets you reflash or repair the firmware manually.
  

Blitzortung firmware + tools are available at:
? https://www.blitzortung.org/en/compendium.php


Maybe step 4 or 5 can be performed remotely as I have the FW version that supports remote / auto firmware updates?  Maybe re-load FW version " 11.0b3"?
Thoughts or recommendations? 


Best regards and thanks in advance.

Pete - W2PJ

[W2PJ-WX]

Note:  The message I get when I enter the address into my browser(s) is:   "Hmmm... can't reach this page 192.168.1.111 connection refused"

[W2PJ-WX]

Also please note that my System Blue continues to detect and report signals and strokes, but I can no longer change any of the current setting for gains and thresholds and or filters as well as observe real time channel stats, noise level and see signals as I cannot log into the controller user interface!  Again, any help would be appreciated.  

If the solution is a firmware update, now might be a would a good time to give the automatic Update triggered by the Server a try??!!
Again, I have FW version 11.0.b3 installed.

[Station_Roko]

Hi,
First you need to make sure that the IP address you are pinging is the IP address of your blitzordung. It would be best to use a port scanner or simply disconnect the Ethernet device while pinging. The second step is to scan for open ports on the identified address to make sure that the http port (80) is open. I suspect that you may have simply disabled the web server while setting something else up.
Cheap routers like Linksys etc. also tend to get confused when using DHCP and IP/MAC relationships etc. Maybe you're also setting up a static IP/MAC mapping?

Blitzortung Community:

I ran into an unexpected problem today.  While trying to fine tune gain and threshold settings I lost the ability to log into the user interface of my System Blue controller using edge.
Station ID: 2110
Controller:  19.3
I have FW version 11.0b3

I lost the ability to log into the controller after a system blue reboot.
Anyone seen this behavior before?

The address I was using stored in my favorites was "http://192.168.1.110/index.cgi?action=status    

Trying to log in I get this message on my Edge Brouser and Firefox Brouser:
192.168.1.111 


After trying several times and getting confused... I rebooted manual system blue with the on off switch.  No Luck.
Then rebooted the router.  No luck.

Checked the IP address of System Blue on my LINKSYS router.  I could not find Blitzortung, so I performed a clear network map and another reboot of the router.

This time the router saw Blitzortung (new address  192.168.1.111).  Tried that.  No Luck.

Pinged address from a command window and got the following response:

C:\Users\Owner>ping 192.168.1.111 refused to connect

Pinging 192.168.1.111 with 32 bytes of data:
Reply from 192.168.1.111: bytes=32 time=1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
Reply from 192.168.1.111: bytes=32 time<1ms TTL=255
Reply from 192.168.1.111: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.1.111:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Rebooted computer.  No Luck.

Does anyone have an idea of what my next step might be to resolve this problem?

I read on chat GPT an option to do the following (Steps 4 and 5 below) , but I do not trust it unless there is documentation from Blitzortung with specific instructions and it is the recommended next step.
I hope an expert on the forum can recommend the correct next steps, and if they are complex references to needed documentation, or another thread that explains the next steps in detail.


From Chat GPT:
4. Force a Factory Reset (if needed)
If all else fails, your controller’s web server might have misconfigured settings or crashed.

• Hold down the reset button on the System Blue controller (you may need a paperclip) for 10–15 seconds during power-up.
  
• This should restore default network settings (DHCP enabled).
  

Then recheck your router for the new IP assignment and try again.

---

? 5. Firmware Recovery Option
If the reset doesn’t help and the controller is unresponsive to HTTP but still pings:

• Connect to the controller via USB and use the Blitzortung update tool from their site.
  
• This lets you reflash or repair the firmware manually.
  

Blitzortung firmware + tools are available at:
? https://www.blitzortung.org/en/compendium.php


Maybe step 4 or 5 can be performed remotely as I have the FW version that supports remote / auto firmware updates?  Maybe re-load FW version " 11.0b3"?
Thoughts or recommendations? 


Best regards and thanks in advance.

Pete - W2PJ

[cutty]

Pete,
I'd suggest a thorough reading of
https://docs.lightningmaps.org/station-o...e/#network ... what stuff does.
https://docs.lightningmaps.org/station-o..._recovery/  attempts to fix.

One possible very simple 'glitch'.... Your browser may assume you want an SSL connection, which will be refused. Make sure you're attempting to connect at HTTP://192.1.x.xxx"  NOT https://  My browser started that 'thinking for the operator' crap with a recent update...
OTHERWISE:
It appears that your only recourse is a factory reset. Especially if you've inadvertently disabled the webserver.
For this you'll need physical access to the controller so you can push some buttons.
once accomplished,
The factory default address will be 192.168.1.235, and all settings will return to factory fresh. 
If you still can't find it after all the options, including security, passwords, etc are 'factory', you may have to look outside the Blitzortung system for the issue.
Those links above give suggestions, info, and procedures for possible scenarios re: can't connect, etc, (including using the rarely mentioned enter "http://blitzortung" in the browser, which might not work in all network setups . May not work if have more than one BT  system active on your network...)

[cutty]

Pete,
I'd suggest a thorough reading of
https://docs.lightningmaps.org/station-o...e/#network ... what stuff does.
https://docs.lightningmaps.org/station-o..._recovery/  attempts to fix.

One possible very simple 'glitch'.... Your browser may assume you want an SSL connection, which will be refused. Make sure you're attempting to connect at HTTP://192.1.x.xxx"  NOT https://  My browser started that 'thinking for the operator' crap with a recent update...
OTHERWISE:
It appears that your only recourse is a factory reset. Especially if you've inadvertently disabled the webserver.
For this you'll need physical access to the controller so you can push some buttons.
once accomplished,
The factory default address will be 192.168.1.235, and all settings will return to factory fresh. 
If you still can't find it after all the options, including security, passwords, etc are 'factory', you may have to look outside the Blitzortung system for the issue.
Those links above give suggestions, info, and procedures for possible scenarios re: can't connect, etc, (including using the rarely mentioned enter "http://blitzortung" in the browser, which might not work in all network setups . May not work if have more than one BT  system active on your network...)

Interestingly, CHAT GPT may give some strange responses... not all are valid, or even factual... I played a 'game' with her, and she was so screwy, we had a system finally that would ONLY work properly in intense radiation environment on Jupiter, with communications through Voyager One... (well, not really, but equally as absurd)...

[W2PJ-WX]

Thanks for the inputs guys.

1) I was never in the area that allows you to select anything having to do with the web browser.
2) tried explicit http://192.168.1.111  No Luck.

Disconnected the controller form the network and ping 192.168.1.111 from a command window.  As expected, "Reqeust timed out".  So I do have the correct address for the Blitzortung controller.

Cutty and team:
Any thought on trying the remote server download and update of the firmware?

[Art_Brown]

Hi everyone,

This happened to me in November 2022 on System Blue version 9.5b1, and my station still responds with "192.168.1.235 refused to connect." as of today, using the  http://192.168.1.235/index.cgi?action=login address. The station otherwise continues to operate 'normally', detecting and sending data to the servers.

The change magically happened overnight when no one was adjusting the station, and it was, and still is, powered via a 2KVA UPS, and no power outages nor fluctuations were logged prior to the event. When the UPS has kicked in, the station (and my PC) continue to operate normally durring the power event.

I did add voltage dividers to the two outdoor H-field loop antennas so I can attenuate them at my desk (10 turn pots), thus I do have operational control over sensitivity (just turn a knob and watch my station's real-time signals on Lightningmaps.org), but no chance of changing station gains, thresholds or any other settings. This antenna configuration is actually faster to adjust than using the keyboard and mouse, and has continuous adjustment steps over the full antenna signal, limited only by the potentiometer adjustment resolution. It is fun to use, and you don't need a damaged station to adopt this type of adjustable antenna configuration (no changes to the station are made).

Also, I changed my e-field antenna to use variable length pull-out segmented stainelss steeel antennas like portable radios have, so I get my exercise walking out to that antenna if I want to adjust its sensitivity by making it longer or shorter.

I am concerned that updating the firmware might make the station non-operable, and possibly unreplaceable given the manufacturing problems the BO Team has been facing, and those are far bigger problem than not having keyboard access, so I am living with the current situation.

Comments and suggestions are welcome.
Regards,
Art Brown
San Ramon, CA, USA

[cutty]

Thanks for the inputs guys.

1) I was never in the area that allows you to select anything having to do with the web browser.
2) tried explicit http://192.168.1.111  No Luck.

Disconnected the controller form the network and ping 192.168.1.111 from a command window.  As expected, "Reqeust timed out".  So I do have the correct address for the Blitzortung controller.

Cutty and team:
Any thought on trying the remote server download and update of the firmware?

Just won't grant access on network, or can't find on network, or request denied. ?
Doesn't matter... Do the factory reset.

 I assume you had already had upgraded to latest firmware 11x? 
   If I understand, it was fine until you rebooted ?
    It that is true, then Messin' with firmware should be a last resort... and a PITA
     I find it hard to believe it got corrupted after successful upgrade, and previous functionality demonstrated. 

Didn't you say somehow it had switched address from 110 - 111 by router?
That's not firmware.
Who knows what it is now? Router could send it anywhere I suppose.

I also understand that the web gui page won't open at all...
but ... Even if it's asking for 'login'credentials:
 
Let's get this simple.  Before doing anything else, ....
Physically remove the power.  Disconnect everything. 
A minute or two, then
Connect GPS only. 
Apply power. 
Let it boot up and get 1PPS flashing.
That should clear everything 'temporary'
NOW
Do the factory reset to hard-coded settings. Not a reboot to saved settings. Since you can't access the tools GUI page, you MUST RESET with the manual method -- the button combos.
 Let it reboot, GPS 1PPS flashes, etc.
Good
Physically remove the power. 
Reconnect EVERYTHING. 
Apply power. Let Boot up & start.

GUI should work by accessing at http://192.168.1.235

about everything internal is now as it came off Egon's setup bench before leaving Germany, except for your locally loaded firmware.  Everything else is square one.

I now should be able to connect it into my network just like a brand new system... if my network, browser/device etc is normal. I even had a case of a machine driving another network configuration that wouldn't connect because the NETWORK it was set to use did NOT include the Blitzortung system, OR and the url could NEVER be correct on that device!  Reset the Windows Network on that machine.  Voila!  There she is!

Other than this, that's all I offer at least at the moment... .