Resolved with wifisetup
Connected to PuTTy via USB and did wifisetup
Everything is back to normal, except for DNS issues.
It does not recognize omega-xxxx.local. I have to enter IP addresses. I can live with that for now.
My mistake. I really meant something like Linux Gedit editor, which is in Mint or Ubuntu, and most other distros. It just shows up as Text Editor. And of course Terminal is in all versions of Linux. And nano I use all the time. I guess I was just frustrated with Omega2+ in general. PuTTY is just fine. And Omega2+ is getting better. And the rain has stopped and the Sun is out.
Yes this is the workaround, ssh ... the console tool is not really a part of the onion os ... so you have to search in internet for the tools website and look there if it has a workaround yet. We had the same issues already with omega1..
@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...