v6.7.1: n3dr repositoriesV2 --upload ... -- net/http: TLS handshake timeout

[3eka]

What happened: Failure to upload maven repository to empty nexus instance

What you expected to happen: To successfully upload

How to reproduce it (as minimally and precisely as possible): a) Create empty instance of Nexus3 (free version), and create empty releases repository (type maven2, hosted "Validate that all paths are maven artifact or metadata paths" Permissive) b) try to upload to that release repository (data are retrieved from existing one, with n3dr repositories --backup ... --directory-prefix=/path command c) upload command is n3dr repositoriesV2 --upload ... --directory-prefix=/path

Anything else we need to know?: If that is important, source nexus instance does not run under https, destination (new) one does

Environment:

• nexus version: Sonatype Nexus Repository Manager OSS 3.39.0-01 (both source and destination instance)
• n3dr version (use n3dr -v):

:; n3dr --version
n3dr version 6.7.1

• OS (e.g: cat /etc/os-release): OpenIndiana Hipster 2021.10 (powered by illumos)
• Kernel (e.g. uname -a):

:; uname -rosv
SunOS 5.11 illumos-f3ba9b4e08 illumos

• Others: n3dr was build with

:; go version
go version go1.18.4 illumos/amd64

Example of failure:

ERRO[0019]/n3dr/internal/artifactsv2/upload/upload.go:283 github.com/030/n3dr/internal/artifactsv2/upload.(*Nexus3).ReadLocalDirAndUploadArtifacts.func1.1() http status code not found in error message: 'Post "https://destination.mydomain.com:8443/service/rest/v1/components?repository=releases": net/http: TLS handshake timeout'
2022/07/29 09:38:13 io: read/write on closed pipe
2022/07/29 09:38:13 io: read/write on closed pipe

Even if I add --debug switch, error message does not change.

https://destination.mydomain.com:8443 has enabled both TLSv1.2 and TLSv1.3 protocols

On google, we can find plenty of net/http: TLS handshake timeout problem causes... Regards.