Can no longer log into System Blue Controller, Web Brouser Interface
#1
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
Stations: 2110
Reply
#2
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"
Stations: 2110
Reply
#3
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.
Stations: 2110
Reply
#4
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?



(Today, 01:32)W2PJ-WX Wrote: 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
Regards,
Jarek R,

Station: 2527
Reply
#5
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...)


Stations: 689, 791, 1439, 3020
Reply
#6
(2 hours ago)cutty Wrote: 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)...


Stations: 689, 791, 1439, 3020
Reply
#7
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?
Stations: 2110
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Does the System Blue Basic take the same Firmware as System Blue? DrFX 3 3,759 2025-04-19, 23:25
Last Post: DrFX
  Question about web interface williammurdock 3 3,786 2024-08-10, 08:33
Last Post: DelandeC
  Can't Log In k2ors 2 4,551 2024-07-18, 19:32
Last Post: cutty
  cannot log in opadavis2 5 27,702 2019-09-16, 13:19
Last Post: cutty
  System blue web page fails EA3BNF 5 32,340 2017-06-03, 06:55
Last Post: EA3BNF

Forum Jump:


Users browsing this thread: 9 Guest(s)