Issues with --proxycertificatepassword Deadline Client 10.4.1.8

Deadline
1

Trying to install Deadline client silently using:

\path\to\installer --mode unattended --connectiontype Remote --proxyrootdir hostname:4433 --proxycertificate \path\to\Deadline10RemoteClient.pfx --proxycertificatepassword password

All seems to go well but when I run up monitor/worker for the first time it errors with:

The Monitor was unable to connect to the specified server (hostname:4433 (Deadline10RemoteClient.pfx)).

Error encountered when loading the configured Client Certificate (//path/to/Deadline10RemoteClient.pfx). It is likely either an invalid x.509 certificate, or the wrong passphrase was provided.

Full Error:
The specified network password is not correct.
at Deadline.Configuration.RepositoryConnectionSettings.d(a dhz, String dia, String dib, X509Certificate2& dic)
at Deadline.Configuration.RepositoryConnectionSettings.c(X509Certificate2& dhy)
at Deadline.Controllers.RemoteDataController…ctor(RepositoryConnectionSettings settings)
at Deadline.Applications.DeadlineApplicationManager.CreateDataController(RepositoryConnectionSettings connSettings)
at Deadline.Applications.DeadlineApplicationManager.Connect(RepositoryConnectionSettings connSettings, Boolean updateScriptManager)
at Deadline.Monitor.MonitorManager.Connect(RepositoryConnectionSettings connectionSettings, Boolean updateScriptManager)
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InvokeDirectByRefWithFewArgs(Object obj, Span`1 copyOfArgs, BindingFlags invokeAttr)

Annoyingly after I accept the error and put the password in manually it works.

Not sure if I am doing something wrong with the – switches?

Cheers

2

I’m also installing the DeadlineClient 10.4.1.8 silently on Linux and I’m not having issues whatsoever. I’m noticing some differences between your command and mine. Here is what I’m doing here:

DeadlineClient-${version}-linux-x64-installer.run --mode unattended --prefix $destination_path --connectiontype Remote --proxyrootdir $proxy_root_dir --tlsport $tls_port --enabletls true --proxycertificate $server_certificate --launcherdaemon true --daemonuser $daemon_user --slavestartup true

Some flags are not relevant to your issue, but here we specify --tlsport and --enabletls

In your case, --proxyrootdir seems to include the port, but not on my end. The port is specified with --tlsport

I hope this will help!

3

Hey sbissonnette0

Cheers for the suggestion!

Looks like it was down to the %Localappdata%\Thinkbox folder, once that was removed it no longer complained. Will do some more testing to confirm!

Cheers!