Fresh installation of Ekahau AI Pro on macOS, company issue laptop, running the usual pre-installed security software suite, including Zscaler.
Ekahau installed fine
However, attempting to launch ekahau throws an error.
"There was a problem while connecting to Ekahau Cloud. Please check your internet connection. Contact helpdesk support in case the problem persists."
- Tried restarting the laptop
- Tried uninstalling Ekahau, re-installing
But met with the same error
We looked at the log file:
~/USER/Library/Ekahau AI Pro/logThe Library folder is hidden by default, you should load Finder, click 'Go' hold option that way Library reveals itself.
Examination of the logs reveals
This indicates that Ekahau is looking to connect to the cloud, but is getting redirected to the local proxy.
The important line:
2024-01-29 15:20:53,592 [JavaFX Application Thread] INFO com.ekahau.x.Dj - Using proxy server for "https://ekahau.com": http = 127.0.0.1:9000Long story short, this Ekahau failure to launch / activate is caused by proxy settings within macOS
from Ekahau support page:
We can download system.properties file which should be placed into
~/USER/Library/Ekahau Pro/.settings/This directory is hidden, you can show / reveal hidden files within Finder using the keyboard shortcut command + control + period
Check within macOS System Settings
System Settings > Network > active Network > Details > ProxiesMake a note of the URL
Next, you need to edit the downloaded system.properties file
Copy the URL from System Settings and add it to the ekahau.proxy.customUrl= field.
Change from:
ekahau.proxy.defaultTrustStore=false
glass.win.uiScale=NaN
ekahau.proxy.authorization=haxx0r\:swordfish
ekahau.proxy.disable=false
ekahau.proxy.customUrl=localhost:8080
ekahau.proxy.skipAuth=falseto:
ekahau.proxy.defaultTrustStore=false
glass.win.uiScale=NaN
ekahau.proxy.authorization=haxx0r\:swordfish
ekahau.proxy.disable=false
ekahau.proxy.customUrl=127.0.0.1\:9000/localproxy-edc301a6.pac
ekahau.proxy.skipAuth=falseFinally, quit Ekahau if it is still running, then try again.
This worked for Danny Ruiz and I, while on a customer site in February 2024, with help from Ekahau Support.