8 hours ago
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.
? 5. Firmware Recovery Option
If the reset doesn’t help and the controller is unresponsive to HTTP but still pings:
? 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
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).
? 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.
? 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