Repository access error

[alf]

Hello,

I would like to know what this error means: "
Repository access error. Socket Error Host not found / Server access error: Socket #110XX Host not found" in the local WAPT configuration window.

Sincerely,

Anne-Laure

[dcardon]

Hello Anne Laure,

I would like to know what this error means:
Repository access error. Socket Error Host not found / Server access error: Socket #110XX Host not found in the local WAPT Configuration window.

It's stated directly in the message: "host not found". If I remember correctly, you've already had quite a few problems with your DNS. Did you replace the DNS name in the wapt-get.ini configuration with an IP address?
There's no point in trying to debug WAPT if your Windows DNS layer isn't already working properly.

Sincerely,

Denis Cardon

[alf]

Hello,

I agree that there are DNS issues because, as the error message indicates, it can't find the host.
The documentation clearly states that IP addresses should not be used.
You suggested adding the IP address to the configuration file; is this for testing purposes, or can I leave it as is, knowing that my DNS is indeed unreliable?

Sincerely,

Anne-Laure

[dcardon]

Hello Anne Laure,

I completely agree that there are DNS issues because, as the error indicates, it can't find the host.
It's clearly stated in the documentation that IP addresses shouldn't be used.

Indeed, the use of DNS names is emphasized. It's more practical for long-term management, and it's a prerequisite for using certificates (unless you're using...) SubjectAlternativeName and to have an internal board of directors at least...)

So yes, it's much better to use DNS names, but if there are DNS problems on the local network, using an IP address is preferable. In terms of security, you can always use certificate pinning in WAPT to validate the HTTPS connection, and furthermore, regarding packets, the signature is always validated after downloading, whether via HTTP or HTTPS.

You suggest I put the IP address in the config file, is this for testing purposes or can I leave it as is knowing that my DNS is indeed unreliable?

This is primarily to validate that it resolves all the different problems you have reported, and to generalize this solution to all workstations while waiting to find out why your DNS environment is causing problems (but that is outside the WAPT topic).

Sincerely,

Denis