Open anubisalpha opened 7 years ago
I too have this problem. Updated to the latest firmware (0.1.10 b160) and needed to reset to factory settings. Followed the instructions as outlined here (https://docs.onion.io/omega2-docs/factory-reset.html) - did the command line version first - on boot I could only see the "Index of /console/" web page in the browser. Then tried the "hold reset button for 10 seconds" approach which ended up with the same result.
I attempted to follow some of the instructions here (http://community.onion.io/topic/1385/resolved-console-shows-index-of-console-only-seems-like-it-reset-completely-but-didnt-complete/3) and managed to get the console installed again (opkg install onion-console-base) but this now just shows a blank console in the browser with no options.
Omega2+ with dock
Well that's not promising to hear. I just ran into the same issue. If I'm able to solve it I'll update. edit: Mine just started working about a day later. Didn't even restart the thing.
Windows internet Explorer seems to be the culprit here.. install Google Chrome and your problems is solved.
I was always using chrome. People are using IE that have the skills to use one of these things?
Cant be sure but Chrome did an about face for the Omega on my laptop running system 7. DougS
On Mar 26, 2017, at 9:57 AM, mikegustafson101 notifications@github.com wrote:
I was always using chrome. People are using IE that have the skills to use one of these things?
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Windows internet Explorer seems to be the culprit here.. install Google Chrome and your problems is solved.
Nope, I was using Chrome. I haven't used IE for years! Any suggestion or indications from @OnionIoT about maybe looking into this issue??
I was/am using Chrome too. Had the issue, and it just went away all by itself. I didn't even restart the onion. I may have closed Chrome itself, but Im sure you've already done that. Do you have a second onion? Can you attempt to connect to it?
Do you have a second onion? Can you attempt to connect to it?
No, I don't. However, I did a factory reset on a lower firmware version and it worked fine, which leads me to think that something isn't quite right in version 0.1.10 b160. A factory reset should be just that - taking everything back to how it was when it comes out of the factory - if I have to do some manual installation that involves trawling through issues that others have faced to fix, isn't a factory reset.
I have the same (or similar) problem. I get an error "xxx.xxx.1.55 refused to connect." But I can see the console using ssh. Also it stopped working after I did a factory reset.
EDIT: A few hours later and now it is working. Was using Chrome, tried Firefox and it worked. Then closed the Chrome page and a new page in Chrome is working fine.
Make sure ur on the same network. Even then its nothing to write home about. No better interface than the command line, i say!
On Mar 29, 2017, at 3:18 PM, jimgable notifications@github.com wrote:
I have the same (or similar) problem. I get an error "xxx.xxx.1.55 refused to connect." But I can see the console using ssh.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Well, my optimism was short lived. The web terminal is broken again. Just "xxx.xxx.1.55 refused to connect". Setup works fine. I am using SSH for good maybe. I'm worried about the other web interfaces, but I don't have those break-out boards yet. This is not working on Chrome or Firefox. On a Mac.
Definately an http:// address problem
On Mar 30, 2017, at 9:00 AM, jimgable notifications@github.com wrote:
Well, my optimism was sort lived. The web terminal is broken again. Just "xxx.xxx.1.55 refused to connect". Setup works fine. I am using SSH for good maybe. I'm worried about the other web interfaces, but I don't have those break-out boards yet.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I have the problem whether I use http://omega-ABCD.local or if I just use omega-ABCD.local. In fact it resolves to the latter anyway.
Should have http://192.168.2.1 or something similar
On Mar 30, 2017, at 1:11 PM, jimgable notifications@github.com wrote:
I have the problem whether I use http://omega-ABCD.local or if I just use omega-ABCD.local. In fact it resolves to the latter anyway.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I tried your alternative, but no go. Still can't get the web terminal to show. To be more clear, my problem is not connecting entirely. I can see the Settings page beautifully. Just something wrong with Terminal. Meanwhile I can use SSH to control the device. I would prefer if the web Terminal worked. Partly just because I don't understand what is wrong with it.
Have you tried using Putty, much easier and more stable.
Sent from my iPhone
On Mar 30, 2017, at 2:23 PM, jimgable notifications@github.com wrote:
I tried your alternative, but no go. Still can't get the web terminal to show. To be more clear, my problem is not connecting entirely. I can see the Settings page beautifully. Just something wrong with Terminal. Meanwhile I can use SSH to control the device. I would prefer if the web Terminal worked. Partly just because I don't understand what is wrong with it.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Without trying to sound negative here, has anybody actually investigated the firmware version, which clearly is not quite right? Surely jumping through hoops to get something working after a "factory reset" is not actually a factory reset, which is the bigger issue here. I suspect that @jimgable's issue is down to the console not working, which we all have mentioned above. Can somebody from Onion maybe look at this?
Just thought i'd let people know that i managed to fix my issue.
After quite a number of resets i decided to not bother with the web setup process and use ssh,
The best thing was for me to install the onion-console-base on command line, but it did take a bit of patience.
Thanks for all your thoughts and ideas..
Marc
Hi to all I posted my problem already in a new post so i am part of your team.
My omega was working fine until yesterday.
When i just too turn it on it connected to my home network i could ssh (putty), ftp and console without any problems.
Now my scenario cant reach it, no console, ftp or ssh get connection refuse , but if i connect to the omega wifi i can connect thru putty haven't tried ftp, console is working but if i go to terminal i also get a connection refused,
I have already factory reset, no fix for me.
many reset later it work but today same problem.
The omega is getting my home network fine so i don't think thats the problem.
Havent try to ssh command line. What i did yesterday i delete the wifi connections to my home network (2 routers) in the omega i think that made the difference but today i don't know what is the problem
Thank you
I am having a similar issue. I just got my Omega 2+ with Dock. I can get webpage to show color but there is no login area.
An excerpt from the book. I totally agree. GUI is fun but bigger headache!
On Apr 3, 2017, at 3:16 PM, leviweather notifications@github.com wrote:
I am having a similar issue. I just got my Omega 2+ with Dock. I can get webpage to show color but there is no login area.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Wonderful guide btw! Examples are exemplary!
On Apr 3, 2017, at 3:16 PM, leviweather notifications@github.com wrote:
I am having a similar issue. I just got my Omega 2+ with Dock. I can get webpage to show color but there is no login area.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Im assuming that you installed the uci commands from the command line. (Onion DOCS) at docs.onion.io
Sent from my iPhone
On Apr 3, 2017, at 3:16 PM, leviweather notifications@github.com wrote:
I am having a similar issue. I just got my Omega 2+ with Dock. I can get webpage to show color but there is no login area.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I have installed the uci commands but it still doesn't work.
A little vague. What is "it" that doesn't work. And what is "work" expectation? Computer work is very precise!
On Apr 7, 2017, at 10:53 AM, leviweather notifications@github.com wrote:
I have installed the uci commands but it still doesn't work.
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
The web console. Whenever I try to access it through the address: http://omega-0517.local/, I get a multicolored screen. I think there should be a login area but I can't find it.
When I tried my other computer, using Google, it connected and let me login!
This is a cookie issue. You solve it by deleting cookies with the name onion in them and go to the page again. That will solve this issue
Unsure of the cookie fix, didn't have to do that. Both of my omegas are working fine now. Patience, patience...
On Apr 11, 2017, at 10:08 AM, Johan Bernhardsson notifications@github.com wrote:
This is a cookie issue. You solve it by deleting cookies with the name onion in them and go to the page again. That will solve this issue
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Your cookies probably timed out then. I just did it on my Omega and that solved the problem immediately. So no waiting is needed :)
On April 11, 2017 18:16:12 dpsgithub notifications@github.com wrote:
Unsure of the cookie fix, didn't have to do that. Both of my omegas are working fine now. Patience, patience...
On Apr 11, 2017, at 10:08 AM, Johan Bernhardsson notifications@github.com wrote:
This is a cookie issue. You solve it by deleting cookies with the name onion in them and go to the page again. That will solve this issue
― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/OnionIoT/Onion-Console/issues/64#issuecomment-293315289
Omega2+chrome+upgrade --> Onion Console Not Loading. I go back and it still does not work. the other applications work
This is a cookie issue, When I did reset factory, console didn't ask me to reinstall it, I open it with different browser and everything is ok
I am getting problem In log in . Shows colored screen but not console
Only solution I know is to install and use through Google Chrome. Worked best for me!
On May 22, 2018, at 3:45 AM, DheerajSingh1107 notifications@github.com wrote:
I am getting problem In log in . Shows colored screen but not console
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Thank you very much I solved it. 192.168.3.1/setup-wizard and Boom it worked ;)
After having lots of issues setting it up with the upgrade failing and console not installing, it was just easier to use command-line to set it all up.
But after all that it seems ok but i am unable to access the console, it is just displaying a blank screen.
I have removed and reinstalled onion-console-base and still not working, anyone have any thoughts?
I am on FW 0.1.0.10 b160 Omega2+ with a basic expansion board.