Guys, this one is closed. I am just an idiot and didn't properly follow through with some of the pre-existing solved threads. Thanks for helping me and making me realize that I might be able to fix this myself!

@Chris-Parker I think I have found a solution, or more specifically, I personally have found a solution that works for me and solves my variant of the issue that you had.

We both had the same problem, namely that in Chrome we were able to access Console Editor but unable to access Console Terminal (and in my instance, Console Webcam). My solution came in an unexpected way, namely by using another web browser to access Console. So, I temporarily abandoned my beloved Chrome and hopped on Microsoft Edge (I am running Win10. Perhaps you might use Firefox or other browser). Because I couldn't get the "http://omega-XXXX.local/" to run, I used "192.168.3.1" to access terminal.

Upon logging in, I selected Console Terminal, and voila, it prompted me to install it! Turns out that what you and I are seeing is where the Console Terminal isn't installed, and for some reason it's not prompting us to do so, just showing a page stating that the IP address refused to connect!

Hope this solves your issue!

Update: After restart Console Terminal is a blank white screen, and Console Webcam doesn't work again. Might not be the solution needed...

^^I'd like to bump this issue as well. Same problem, on Chrome. Editor works fine, I can SSH but can't successfully run the "opkg onion-console-terminal" and "opkg onion-console-webcam" commands in PuTTY.

Guys, this one is closed. I am just an idiot and didn't properly follow through with some of the pre-existing solved threads. Thanks for helping me and making me realize that I might be able to fix this myself!

@Christopher Spot on, running that command gave me exactly what you predicted.

I tried running "opkg" but it wasn't happy with that, and broke out a bunch of options for commands. I tried running "update" but that wasn't successful.

Any advice? Making progress, but still a touch lost.

@José-Luis-Cánovas Upon connecting via SSH and accessing BusyBox (v1.26.2), my commands are prefixed with "root@Omega-XXXX:~#"

Somehow in the process of trying to fix a problem I've caused an even bigger one. My Omega2+ has two entries listed when I run the " ls -all" command in SSH. This could potentially explain why whenever I attempt to connect via console the only thing that happens after logging in is watching the gear icon spin into oblivion (aka a white screen). Any advice?

Also, apologies in advance, I am about to go to sleep and then work after, so I won't respond to anything until about 16:30 MDT.