Troubleshooting the Omega Setup
-
Hi Team,
I'm having a problem connecting to the Omega via my web browser (Chrome) from a Windows 10 machine. After I've entered omega-ABCD.local (with ABCD as my Omega's SSID numbers) into the url field it just shows a Server Not Found page.
I can communicate with it over a terminal through my USB to Serial Connection.
I have two Omegas and I have run through the steps listed on https://onion.io/getstarted/ with both and the GUI setup didn't work for either.
What can I do to troubleshoot or resolve this issue?
Cheers,
Jeremy
-
If you can get into it via usb cable, you can run "wifisetup" in the terminal to set the omega's setting to work on your router. Then you will have access to the GUI.
Hope this helps.
-
Hi Jeremy,
Here's a couple things you can try out:
- Add http:// before omega-ABCD.local. Sometimes your browser may not recognize that you are actually entering in an URL, and treat it as a search string instead.
- Try to setup by the Omega by going to http://192.168.3.1 instead. This explicitly tells your browser to connect to the IP address of the Omega instead of doing it through an alias.
Please let us know if these help, or if you have any other questions.
Cheers!
Boken.
-
I had the same problem and after asking for help got basically the same reply.
I can confirm that using http://192.168.3.1 worked for me.
However, note that you shouldn't use Firefox - it doesn't handle the response properly. I had to use Chrome or Microsoft Edge
-
@Kit-Bishop The bug with firefox seems to be caused by a bug in the Javascript framework we are using. We have been working on a fix for it. We will include that in the next console release later this week.
-
Thanks - no rush - I'm happy using Chrome
-
I think you should include the 192.168.3.1 option throughout your documentation on setup. It is only found one place in your docs I think.
-
@Onion-Rings Updated!
-
See it
That was quick Thanks
-
@Boken-Lin Does this also apply to the Safari browser on the iPad? I managed to connect to my Omega and it displayed the Omega Setup Wizard, but the line below was all gray and nothing happened.
-
I couldn't connect with Safari, everything worked great once I ran it in Chrome though
-
@Derek-Law, @Tim-Smith Yes, this will fix the bug in Firefox as well as Safari
-
@Boken Lin can you tell me the chipsets used in the expansion boards Im just building my kernel and I want to make sure I include the support compiled in for the different expansion boards chips like the ethernet chipset. That way I dont have to just select everything in modules.
-
@Andrew-Moore When you are in the menuconfig, if you have selected your target as the Onion Omega, it should automatically load all the kernel modules to make sure all expansions can be recognized by the Omega.
-
Ok Cool I did see some pre selected but I didnt see the ethernet controller so I wasnt sure if the expansions were included, I must have missed it. Is it a module or loaded in the kernel? Sorry I dont have the Onion yet just getting ready.
Thanks
-
@Andrew-Moore Ethernet expansion should be supported by the default configuration, so you don't need to select additional modules for it to work.
-
Directing to http://192.168.3.1 worked great! Thanks Boken for the quick response
-
@ Kit Bishop said:
you shouldn't use Firefox - it doesn't handle the response properly. I had to use Chrome or Microsoft Edge
I was just add that Opera too seems to work ok.
-
@T-NT said:
@ Kit Bishop said:
you shouldn't use Firefox - it doesn't handle the response properly. I had to use Chrome or Microsoft Edge
I was just add that Opera too seems to work ok.Support for Firefox and Safari will be added starting from next console release. Stay tuned
