No connection to port 80 after update to 2.3.4.150

I did the update to 2.3.4.150 tonight on my C-7 and after that the hub is no longer accepting connections on port 80. I am able to get to 8081. Rolled the firmware back to 2.3.4.138, safe mode, soft reset, nothing I've done has resolved the issue. Looking for any additional suggestions if anyone has any. Thank you

Starting Nmap 7.91 ( https://nmap.org ) at 2023-02-16 10:27 MST
NSE: Loaded 123 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 10:27
Completed NSE at 10:27, 0.00s elapsed
Initiating NSE at 10:27
Completed NSE at 10:27, 0.00s elapsed
Initiating ARP Ping Scan at 10:27
Scanning 10.10.20.22 [1 port]
Completed ARP Ping Scan at 10:27, 0.06s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 10:27
Completed Parallel DNS resolution of 1 host. at 10:27, 0.02s elapsed
Initiating SYN Stealth Scan at 10:27
Scanning 10.10.20.22 [65535 ports]
Discovered open port 8081/tcp on 10.10.20.22
Completed SYN Stealth Scan at 10:27, 3.24s elapsed (65535 total ports)
Initiating OS detection (try #1) against 10.10.20.22
NSE: Script scanning 10.10.20.22.
Initiating NSE at 10:27
Completed NSE at 10:27, 0.01s elapsed
Initiating NSE at 10:27
Completed NSE at 10:27, 0.00s elapsed
Nmap scan report for 10.10.20.22
Host is up (0.00080s latency).
Not shown: 65533 closed ports
PORT STATE SERVICE
22/tcp filtered ssh
8081/tcp open blackice-icecap
MAC Address: REMOVEDFORPOSTING (Ieee Registration Authority)
Device type: general purpose
Running: Linux 3.X|4.X
OS CPE: cpe:/o:linux:linux_kernel:3 cpe:/o:linux:linux_kernel:4
OS details: Linux 3.2 - 4.9
Uptime guess: 198.839 days (since Mon Aug 1 15:19:13 2022)
Network Distance: 1 hop
TCP Sequence Prediction: Difficulty=263 (Good luck!)
IP ID Sequence Generation: All zeros

NSE: Script Post-scanning.
Initiating NSE at 10:27
Completed NSE at 10:27, 0.00s elapsed
Initiating NSE at 10:27
Completed NSE at 10:27, 0.00s elapsed
Read data files from: /usr/bin/../share/nmap
OS detection performed. Please report any incorrect results at Nmap OS/Service Fingerprint and Correction Submission Page .
Nmap done: 1 IP address (1 host up) scanned in 5.07 seconds
Raw packets sent: 65559 (2.885MB) | Rcvd: 65549 (2.623MB)

I rolled it all the way back to 2.3.3.140. Still unable to get anything on port 80. I'm stumped. Looking for some other solution or suggestions on a better replacement option.

Maybe notify @Hubitat_Staff as it seems you are not the only one.

This link might also provide a solution

Have you tried downloading a backup, then soft reset WITHOUT restoring a backup?
Also have you ever pulled power and waited 10 seconds before plugging back in?
Does LED even go green or is it stuck on blue?

1 Like

Light is stuck on blue. I've pulled power several times. When doing a soft reset it never gives the option to do it without restoring a backup. Actually when I do a soft reset it tells me the hub is rebooting, and never comes back with anything after, hangs there.

Always nice to see someone chip in to help with good advice. Hope you dont mind me linking to your earlier post @jtp10181 Jeff.

1 Like

Soft reset itself does not say anything about a restore, it only asks for the restore after rebooting, which you can skip. Was just curious if the soft reset without a restore would bring back the UI.

1 Like

Just did anther soft reset. I get this screen and nothing else. Hub light went out for a few seconds and then back to blue. Page never changes. Refresh the page and I'm back to the standard menu.

image

1 Like

So something seems wrong with the Hubitat OS layer.
Similar to the post i linked. Maybe reach out to @bobbyD.

A factory reset would be a very very last resort, and only then if Hubitat Support gives that as an optional solution i guess

1 Like

I'm at 30+ devices on this hub. A factory reset might push me in another direction. That is a lot of work to set back up.

And thats why i mention it as a last resort only and ONLY after contacting staff and them pointing you to it

I've sent a private message to support. I've never had to contact them so I have no experience with the turn around time they have. Hopefully it isn't too bad. Thank you both for the input you have provided so far.

2 Likes

I totally agree that would be a catastrophic event to reset everything, and don't blame you from getting worried. There is no reason for such a radical measure. Can you go to the Diagnostic Tool and select "Set hub date and time" then hit "Set time" to see if that resolves the problem?

2 Likes

I've set the time a few times now. Doesn't change anything.

@gopher.ny and @bobbyD set me up with some instructions on a FactoryRecovery and the new 2.3.4.153 version. Hub is operational again.

Thanks to everyone that chimed in on this today with the suggestions!

5 Likes

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.