Updated firmware to most recent (2.3.3??) yesterday. Update screen went through normal screens (downloading, verifying, updating, etc) but never rebooted device. Here's other info that may help:
Green LED is illuminated on box (thus the "bricked" in quotes)
I can ping IP address
I can access ipaddress:8081 and it shows the following:
Edit: More info... Did an nmap on the IP address and only 8081 was responsive:
Starting Nmap 7.92 ( https://nmap.org ) at 2022-07-01 12:59 EDT Nmap scan report for unknown34e1d18082ea.attlocal.net (192.168.2.132) Host is up (0.0039s latency). Not shown: 993 closed tcp ports (conn-refused) PORT STATE SERVICE 22/tcp filtered ssh 80/tcp open http 111/tcp filtered rpcbind 443/tcp open https 8080/tcp open http-proxy 8081/tcp open blackice-icecap 8443/tcp open https-alt
No worries, I'm not about to provide anything meaningful, only to poke BobbyD who can hopefully help you from here, which seems like you need some additional help, so hopefully this has sped that up.
Re: Safe Mode -- no luck. Rebooted and still cant access ipaddress:80 or :8080. Here's something odd, I had "ping" running in a window showing this:
PING 192.168.2.132 (192.168.2.132) 56(84) bytes of data. 64 bytes from 192.168.2.132: icmp_seq=1 ttl=64 time=1.39 ms From 162.203.196.222 icmp_seq=2 Redirect Host(New nexthop: 132.2.168.192) 64 bytes from 192.168.2.132: icmp_seq=2 ttl=64 time=1.32 ms From 162.203.196.222 icmp_seq=3 Redirect Host(New nexthop: 132.2.168.192) 64 bytes from 192.168.2.132: icmp_seq=3 ttl=64 time=1.44 ms From 162.203.196.222 icmp_seq=4 Redirect Host(New nexthop: 132.2.168.192) 64 bytes from 192.168.2.132: icmp_seq=4 ttl=64 time=1.35 ms From 162.203.196.222 icmp_seq=5 Redirect Host(New nexthop: 132.2.168.192) 64 bytes from 192.168.2.132: icmp_seq=5 ttl=64 time=1.35 ms
but after attempted reboot to safe mode starting showing it as:
64 bytes from 192.168.2.132: icmp_seq=1 ttl=64 time=1.47 ms 64 bytes from 192.168.2.132: icmp_seq=2 ttl=64 time=1.29 ms 64 bytes from 192.168.2.132: icmp_seq=3 ttl=64 time=1.29 ms 64 bytes from 192.168.2.132: icmp_seq=4 ttl=64 time=1.40 ms
I took the liberty of looking up the hub by your community address, and it "pinged" the cloud while booting 2.3.0.124 about 20 minutes ago. It does not respond to the support tool requests, though. Can you try switching to 2.3.2 again?
It's up and running, and responding to support tool requests now.
Now, there are entries like these in the logs: rejected HTTP connection from <redacted IP address>
Are you accessing the hub through port forwarding or from a different network segment?
Maybe?? I have AT&T fiber and my desktop PC has a public IP address. Uncertain what network stuff is going on in the router. Let me switch to DHCP locally and see what happens....
I've been using my C7 since... well... forever using a public IP and I've never had an issue before. Shrug. I switched to a DHCP address and all is well. HOWEVER, I can still access the device on port 8081 using my public IP.. how is that working?
Port 80 is blocked from port redirection by design in a late version of 2.2.x. Eventually 8081 will be as well.. This is for security.. That said you shouldn't be port redirecting anything, that's a pretty big gaping hole in most cases unless you have certain protections in place.
