Cant connect to RCS

Trying to install for first time… seem to have everything followed correctly to install repo on server…
When i try to change the repo to the RCS however, it fails… can’t find the RCS
only thing i can see in the logs on the RCS is:
“Listening for https requests on 0.0.0.0 port 4433 loopbackOnly False…”
When changing monitor to RCS, it errors with:
“The Monitor was unable to connect to the server listed at /ip/:4433 (/servername/.pfx)”
Failed to establish connection to IP:4433 due to communicatiion error…

Copy of RCS Log…:
2021-08-13 10:26:50: BEGIN - SHOVESERVE01\Shoveserve01
2021-08-13 10:26:50: Operating System: Windows 10 Pro
2021-08-13 10:26:50: CPU Architecture: x64
2021-08-13 10:26:50: CPUs: 48
2021-08-13 10:26:50: Video Card: NVIDIA Quadro K4200
2021-08-13 10:26:50: Deadline Remote Connection Server 10.1 [v10.1.17.4 Release (d3559fe75)]
2021-08-13 10:26:50: Connected to “S:\Deadline”
2021-08-13 10:26:50: Turning off Kestrel logging
2021-08-13 10:26:50: DEBUG: The RCS is capable of sending responses compressed with :br
2021-08-13 10:26:51: Using ASP.Net Core server.
2021-08-13 10:26:51: Listening for https requests on 0.0.0.0 port 4433 loopbackOnly False…
2021-08-13 10:26:51: Counters: http-process-calls-current=0 http-process-calls-count=0 http-process-slow-calls-count=0 http-process-last-slow=none http-process-histo: ApxMean=NaN P99=NaN BoundsMs=0 Counts=0
2021-08-13 10:27:50: INFO: [SecretsManagement] User(23-38-EE-35-A5-E3-FC-D8-D9-F0-C2-AB-F0-3B-72-D5-56-13-1B-03-E1-A1-52-7D-AE-98-1F-E8-42-EB-2F-9E) User is not registered. (23-38-EE-35-A5-E3-FC-D8-D9-F0-C2-AB-F0-3B-72-D5-56-13-1B-03-E1-A1-52-7D-AE-98-1F-E8-42-EB-2F-9E) Result=False
2021-08-13 10:27:50: [SecretsManagementKeyRotationService] OnTimer threw an exception: User is not registered. (23-38-EE-35-A5-E3-FC-D8-D9-F0-C2-AB-F0-3B-72-D5-56-13-1B-03-E1-A1-52-7D-AE-98-1F-E8-42-EB-2F-9E)
2021-08-13 10:27:50: at Deadline.Controllers.SecretsManagementControllerBase.LogAuditAndThrowException(AuditInfo auditInfo, String errorMessage)
2021-08-13 10:27:50: at Deadline.Controllers.SecretsManagementControllerBase.ValidateUser(String userId, String expectedRole, AuditInfo auditInfo)
2021-08-13 10:27:50: at Deadline.Controllers.SecretsManagementControllerBase.ValidateServerUser(String userId, AuditInfo auditInfo)
2021-08-13 10:27:50: at Deadline.Controllers.SecretsManagementServerController.RotateMasterKey(String serverUserId)
2021-08-13 10:27:50: at Deadline.RemoteConnectionServer.SecretsManagementKeyRotationService.a(Object atj)
2021-08-13 10:27:51: Update timeout has been set to 30 seconds
2021-08-13 10:27:51: Stdout Redirection Enabled: True
2021-08-13 10:27:51: Stdout Handling Enabled: False
2021-08-13 10:27:51: Popup Handling Enabled: False
2021-08-13 10:27:51: Using Process Tree: True
2021-08-13 10:27:51: Hiding DOS Window: True
2021-08-13 10:27:51: Creating New Console: False
2021-08-13 10:27:51: Running as user: Shoveserve01
2021-08-13 10:27:51: Executable: “C:\Program Files\Thinkbox\Deadline10\bin\deadlinecommand.exe”
2021-08-13 10:27:51: Argument: -RunCommandForRepository “Repository” “S:\Deadline;S:\DeadlineDB\Deadline10Client.pfx” -DoHouseCleaning True False True
2021-08-13 10:27:51: Full Command: “C:\Program Files\Thinkbox\Deadline10\bin\deadlinecommand.exe” -RunCommandForRepository “Repository” “S:\Deadline;S:\DeadlineDB\Deadline10Client.pfx” -DoHouseCleaning True False True
2021-08-13 10:27:51: Startup Directory: “C:\Program Files\Thinkbox\Deadline10\bin”
2021-08-13 10:27:51: Process Priority: BelowNormal
2021-08-13 10:27:51: Process Affinity: default
2021-08-13 10:27:51: Process is now running
2021-08-13 10:27:51: Counters: http-process-calls-current=0 http-process-calls-count=0 http-process-slow-calls-count=0 http-process-last-slow=none http-process-histo: ApxMean=NaN P99=NaN BoundsMs=0 Counts=0
2021-08-13 10:27:54: Performing house cleaning
2021-08-13 10:27:54: Performing Job Cleanup Scan…
2021-08-13 10:27:54: Job Cleanup Scan - Loading completed jobs
2021-08-13 10:27:54: Job Cleanup Scan - Loaded 0 completed and 0 active/pending jobs in 34.488 ms
2021-08-13 10:27:54: Job Cleanup Scan - Done.
2021-08-13 10:27:54: Purging Unsubmitted Jobs
2021-08-13 10:27:54: Unsubmitted Job Scan - Loading unsubmitted jobs
2021-08-13 10:27:54: Unsubmitted Job Scan - Loaded 0 unsubmitted jobs in 862.900 µs
2021-08-13 10:27:54: Unsubmitted Job Scan - Done.
2021-08-13 10:27:54: Purging Deleted Jobs
2021-08-13 10:27:54: Deleted Job Scan - Loading deleted jobs
2021-08-13 10:27:54: Deleted Job Scan - Loaded 0 deleted jobs in 794.700 µs
2021-08-13 10:27:54: Deleted Job Scan - Done.
2021-08-13 10:27:54: Purging Obsolete Workers
2021-08-13 10:27:54: Obsolete Worker Scan - Skipping because it is disabled in the Repository Options
2021-08-13 10:27:54: Purging Obsolete AWS Portal Workers
2021-08-13 10:27:54: Obsolete AWS Portal Worker Scan - Loading Worker states
2021-08-13 10:27:54: Obsolete AWS Portal Worker Scan - Loading 1 Worker states in 26.694 ms
2021-08-13 10:27:54: Obsolete AWS Portal Worker Scan - Purging offline/stalled Workers older than 5 days, 0 hours
2021-08-13 10:27:54: Obsolete AWS Portal Worker Scan - Purged 0 obsolete AWS Portal Workers in 57.900 µs
2021-08-13 10:27:54: Obsolete AWS Portal Worker Scan - Done.
2021-08-13 10:27:54: Purging Old Worker Reports
2021-08-13 10:27:54: Worker Report Scan - Loading Worker report collections
2021-08-13 10:27:54: Worker Report Scan - Found 1 report collections and 0 job state objects in 10.744 ms
2021-08-13 10:27:54: Worker Report Scan - Loading Worker IDs
2021-08-13 10:27:54: Worker Report Scan - Loaded 1 Worker IDs in 4.304 ms
2021-08-13 10:27:54: Worker Report Scan - Purged 0 report collections, 0 job state objects, and 0 licensed Worker stubs in 0
2021-08-13 10:27:54: Worker Report Scan - Done.
2021-08-13 10:27:54: Purging Timed Out Workers in Throttle Queue
2021-08-13 10:27:54: Purging Old Statistics
2021-08-13 10:27:54: Old Statistics - Skipping job statistics because the option to purge them is disabled in the Repository Options
2021-08-13 10:27:54: Old Statistics - Purging Worker statistics that are older than Apr 15/21 10:27:54
2021-08-13 10:27:54: Old Statistics - Purged old Worker statistics in 1.900 ms
2021-08-13 10:27:54: Old Statistics - Purging repository statistics that are older than Apr 15/21 10:27:54
2021-08-13 10:27:54: Old Statistics - Purged old repository statistics in 878.500 µs
2021-08-13 10:27:54: Purging expired Remote Command Tokens
2021-08-13 10:27:54: Purging Deleted Document Stubs From Database
2021-08-13 10:27:54: Deleted Document Stubs - Deleting stubs that are older than 3 days
2021-08-13 10:27:54: Deleted Document Stubs - Deleted 0 stubs in 855.200 µs
2021-08-13 10:27:54: Triggering house cleaning events…
2021-08-13 10:27:54: Process exit code: 0

It looks like you need to register the client in Secrets Management so it’s permitted to connect, steps on that here - Getting Started With Deadline Secrets Management — Deadline 10.1.17.4 documentation

Give that a shot and let us know if your client is able to connect now.

Thanks for reply Justin.
Have tried setting the RCS in monitor, but same old problem, either on the main server, or a client…
I’ve tried re-installing the RCS, to start afresh… However am getting errors on creating the certs… It warns that certs were not created succesfully, and to check the log (load of text that doesnt mean a lot to me), then it say after install you’ll need to run “deadlinecommand Secrets ConfigureSecretServermachine”
, which i’ve done, but that errors with " [secrets management] required parameters do not match"??