@Lex-Slaghuis
The installer has installed everything correctly. It is so specifically conceived that when entering on 192.168.3.1, Onion OS was opened because Onion console is not installed in new Omega2 during installation. To fix this, you may need to edit the file /www/index.html

@Lazar-Demin thanks for your swift answer. Unfortunately the update command does not work:

Downloading https://repo.onion.io/omega2/packages/core/Packages.gz
*** Failed to download the package list from https://repo.onion.io/omega2/packages/core/Packages.gz

both http and https don't work

EDIT :

Nevermind, I've found the root of my problem, the omega2 does not seem to like network SSIDs that contain special characters. I changed my network's SSID and now all is fine. Thanks for your help

Hi,
Check out the post "Unable to access Legacy Console" you will be able to get the old console with the newest firmware.
Cheers

have you tried 192.168.3.1?

YES IT WORKED! IT WORKED!! Thanks so much! Oh, shoot the apps won't open again.

First clear your browser cache. Then you may need to re-install the web console.

Generally it is better to be using a serial connection.

@Gene-Liverman
Have you read this topic yet?

@Zheng-Han said in How to disable AP?:

You can't just disable the AP and keep wifi client. You will have to disable wifi all together or make AP SSID hidden

@WereCatf said in How to disable AP?:

@Zheng-Han I'm curious, is this actually hard-coded in the driver, or are you just talking about your WiFi-configuration tools not being to do this? If it's actually hard-coded in the driver..... :confounded:

@Zheng-Han said in How to disable AP?:

It's hard coded in the MediaTek driver :(

There is an opensource version of the wifi driver, however it's very buggy we haven't being able to get it working reliably

@Don-DeGregori Happy to hear you got it sorted!