Error! The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing. Cluster thru VLANS possible?

[MrEnergy64]

Hi Technitium members, we using, since a couple of time, two, independent, Technitium servers. One installed on a Windows Server 2022 and one used on a QNAP container. Both Technitium servers using self signed certs and on different VLANS. Today we upgraded both servers to 14.1 and tried to setup a cluster. Therefore we initiate the Windows Technitium server as primary server and tried to join a fresh docker container Technitium server to the pimary Technitium server. The VLANS are firewalled via OpenSense. We allowed ports like 53, 5380, 53443, 80 and 443 between those Technitium servers. However, if we tried to join the secondary, docker, Technitium to the main we get: "Error! The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing."
Also we used the setting: "Ignore Certificate Validation Errors", no chance.

For the primary node url we use: https://:53443, is this OK?

Is/are there any other port(s) we have to open? Thank you for your help in advance.

LOGS:

System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 30 seconds elapsing.
 ---> System.TimeoutException: A task was canceled.
 ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at TechnitiumLibrary.Net.Http.Client.HttpClientNetworkHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in Z:\Technitium\Projects\TechnitiumLibrary\TechnitiumLibrary.Net\Http\Client\HttpClientNetworkHandler.cs:line 501
   at System.Net.Http.HttpClient.GetStreamAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpClient.HandleFailure(Exception e, Boolean telemetryStarted, HttpResponseMessage response, CancellationTokenSource cts, CancellationToken cancellationToken, CancellationTokenSource pendingRequestsCts)
   at System.Net.Http.HttpClient.GetStreamAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
   at DnsServerCore.HttpApi.HttpApiClient.LoginAsync(String username, String password, String totp, Boolean includeInfo, CancellationToken cancellationToken) in Z:\Technitium\Projects\DnsServer\DnsServerCore.HttpApi\HttpApiClient.cs:line 178
   at DnsServerCore.Cluster.ClusterManager.InitializeAndJoinClusterAsync(IReadOnlyList`1 secondaryNodeIpAddresses, Uri primaryNodeUrl, String primaryNodeUsername, String primaryNodePassword, String primaryNodeTotp, IReadOnlyList`1 primaryNodeIpAddresses, Boolean ignoreCertificateErrors, CancellationToken cancellationToken) in Z:\Technitium\Projects\DnsServer\DnsServerCore\Cluster\ClusterManager.cs:line 1257
   at DnsServerCore.DnsWebService.WebServiceClusterApi.InitializeAndJoinClusterAsync(HttpContext context) in Z:\Technitium\Projects\DnsServer\DnsServerCore\WebServiceClusterApi.cs:line 479
   at DnsServerCore.DnsWebService.WebServiceApiMiddleware(HttpContext context, RequestDelegate next) in Z:\Technitium\Projects\DnsServer\DnsServerCore\DnsWebService.cs:line 1954
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddlewareImpl.<Invoke>g__Awaited|10_0(ExceptionHandlerMiddlewareImpl middleware, HttpContext context, Task task)

[MrEnergy64]

OK, change user in front of screen, the firewall rule was set to udp only, after we changed it to tcp, the cluster node joined perfectly.

[ShreyasZare]

Good to know that you found the issue.