​
Login Troubleshooting & FAQ

​
I have an internet proxy, how do I configure it?

By default, Conduktor detects the system proxy and use it. If for some reasons, you need to configure another proxy, see the Using an Internet Proxy.

​
Will Conduktor work offline?

Conduktor use Auth0 to register/login our users, and validate their license if any. Therefore, an online access is mandatory. For organizations with restricted Internet access, we now offer offline licenses to bypass this requirement.

​
Oops!, something went wrong!

When you login from Conduktor Desktop and get this error in the browser, instead of having the classic login screen, this may due to several reasons.
  • your browser is blocking cookies: our identity provider, Auth0, needs its cookies 🍪. You may try to open the same link (it will be something like https://auth.conduktor.io/u/login?state=xxx) in a private tab (where behavior can be different and cookies allowed temporary)
  • ensure you don’t have some funny extension in your browser that could alter the url for some reasons
  • you hit the “back button” in your browser and tried to come back. Please relogin properly from Conduktor.
  • if nothing works, try to restart Conduktor Desktop and login (to start fresh)
  • Connection Refused: no further information
    • The browser tries to contact our software Conduktor on localhost:8085 to provide the authentication information, and it fails to do so. You probably have a networking tool on your system preventing this connection.
    • If you are running behind a VPN, your VPN client may prevent such connection, please look at its options.

​
Oh no! Authentication has failed…

When you login, you can stumbled upon this error in your browser. That means that something is either preventing Conduktor to contact our authentication server (https://auth.conduktor.io) or the other way around, something is preventing our authentication server to contact Conduktor Desktop on your computer (outside of our control) to finish the identification flow. This can happen due to many reasons. Here are a few:
  • Are you running Conduktor from your enterprise network?
  • Browser plugins can redirect http calls to httpS. The last step of our identification flow is a call to a local temporary http server (http://localhost:5xxx), so if something in the browser forces a redirect from http to https, the flow will never complete.
  • If you’re using a VPN, you may have to configure it to not alter communication to *.conduktor.io or add a certificate into Conduktor (if you VPN adds its own security layer with a self-signed certificate..)
    • Using ZScaler ? Download the ZScaler certificate and import it into Conduktor
  • Ensure you don’t have an antivirus or a firewall blocking communications. You may have to add https://auth.conduktor.io to some allow-list or something.
  • By default, Conduktor uses your system proxy. This can causes some troubles such as: Unable to tunnel through proxy. Proxy returns Go to the settings, setup your proxy manually instead of the system proxy and and add an exception for *.conduktor.io
The JVM embedded in Conduktor (Java 13+, if you are using the classic installation process) trusts Let’s Encrypt’s CA, which is the one that emits the https certificate of our authentication server https://auth.conduktor.io so nothing specific to setup here.

​
Other misc errors

  • Unexpected end of file from server: something on your network prevents Conduktor to request our identity provider, auth0 (Conduktor —> auth.conduktor.io)

​
My organization manage its own certificates / PKIX path building failed

If your organization has its own self-signed CA and certificates, you can add trusted certificates within Conduktor from the welcome screen. Check our dedicated page: Certificates FAQ

​
Login Callback is HTTP_S_ instead of HTTP

In some cases, enterprise network policies force the login callback form http to https. As a workaround it is possible to allow insecure localhost call in google chrome : chrome://flags/#allow-insecure-localhost

​
I need to configure custom JVM options

Create the file conduktor.vmoptions in your Conduktor personal folder and add as many “-D” as you want (only -D, no -XX), to set them when Conduktor starts (only on startup, it’s not taken into account after):
  • MacOS: /Users/<user>/Library/Application Support/conduktor/conduktor.vmoptions
  • Windows: C:\Users\<user>\AppData\Local\conduktor\conduktor\conduktor.vmoptions
  • Linux: /home/<user>/.config/conduktor/conduktor.vmoptions (or XDG Config path if set)
Example: 
-Djava.net.preferIPv4Stack=false
-Dhttp.proxyHost=1.2.3.4
-Djava.security.auth.login.config=/tmp/kafka_jaas.conf

​
Failed to launch JVM

On Windows, it’s possible to get this error “Failed to launch JVM” in certain rare cases.
  • Conduktor can not work if you have special characters in your Windows username like “ö”
  • Check if you have some environment variables configured: _JAVA_OPTIONS or JAVA_TOOL_OPTIONS if that’s the case, then unset them.
Some software adds them for their own need, but this is taken into account by all the Java programs running on your system. This may be dangerous and causes issues (like here). Example: Micro Focus UFT Unified Functional Testing (formerly QTP)

​
My issue is not addressed here

Please send us an email