![]() ![]() Server so nothing specific to setup here. Let's Encrypt's CA, which is the one that emits the https certificate of our authentication The JVM embedded in Conduktor (Java 13+, if you are using the classic installation process) trusts Proxy returns Go to the settings, setup your proxy manually instead of the system proxy and and add an exception for *.conduktor.io This can causes some troubles such as: Unable to tunnel through proxy. By default, Conduktor uses your system proxy.You may have to add to some allow-list or something. Ensure you don't have an antivirus or a firewall blocking communications.Using ZScaler ? Download the ZScaler certificate and import it into Conduktor.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.).The last step of our identification flow is a call to a local temporary http server ( so if something in the browser forces a redirect from http to https, the flow will never complete. Browser plugins can redirect http calls to httpS.You may need to add a trusted certificate to Conduktor:.Are you running Conduktor from your enterprise network?.That means that something is either preventing Conduktor to contact our authentication server ( ) 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. ![]() When you login, you can stumbled upon this error in your browser. If you are running behind a VPN, your VPN client may prevent such connection, please look at its options.You probably have a networking tool on your system preventing this connection. The browser tries to contact our software Conduktor on localhost:8085 to provide the authentication information, and it fails to do so.Connection Refused: no further information.if nothing works, try to restart Conduktor Desktop and login (to start fresh).you hit the "back button" in your browser and tried to come back.ensure you don't have some funny extension in your browser that could alter the url for some reasons.You may try to open the same link (it will be something like ) in a private tab (where behavior can be different and cookies allowed temporary) your browser is blocking cookies: our identity provider, Auth0, needs its cookies □.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. For organizations with restricted Internet access, we now offer offline licenses to bypass this requirement. ![]() Therefore, an online access is mandatory. Will Conduktor work offline? Ĭonduktor use Auth0 to register/login our users, and validate their license if any. If for some reasons, you need to configure another proxy, see the Using an Internet Proxy. Login Troubleshooting & FAQ I have an internet proxy, how do I configure it? īy default, Conduktor detects the system proxy and use it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |