Tranquil IT Forum

Hello,

I made the DNS changes following the previous response, but I'm encountering several other errors randomly.
I can't figure out where these problems are coming from because some consoles work correctly while others don't, even though I've used different settings. Here's

a summary of the errors I'm encountering:
- Repository access error. Socket Error Host not found / Server access error: Socket #110XX Host not found in the local WAPT Configuration window.
- Unable to get https server certificate for url https://wapt.xxxxxx.xxxx gairror: [Errno 11004] getaddrinfo failed when retrieving the certificate in the local WAPT Configuration window.
- An unhandled exception has occurred ConnectTimeout: HTTPSConnectionPool(host='wapt.xxxx.xxx',port=443): Max retries exceeded with url: /wapt/Packages (Caused by ConnectTimedError(
- An unhandled exception has occurred: New connectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x100552B0>: Failed to establish a new connection: [Errno 11004] getaddrinfo failed during packet import.
- WAPT server error: Socket Error # 11004 when opening the WAPT console.
- WAPT server error: Socket Error # 11001 Host not found when reconnecting to the console following an error while deleting a packet.
- Timeout error.

There are certainly errors due to DNS problems, but I don't understand why it's not stable.
Is there anything I can do to improve console stability?

I also get the error "Unable to retrieve action. Error on server: Timeout, client did not send result within 5.0 s99" when installing packages from the console.

I also encounter this problem when manually launching package installations.
I start the installations, and in the popup that appears, there are no launched actions, no errors, no skipped actions, and no server errors. My package doesn't appear in the General tab, even though it's in the machine inventory.
How can I force the installation?

Thank you in advance.

Anne-Laure

Good morning,

alf wrote: ↑May 25, 2018 - 09:50 I'll give you a rundown of the errors encountered.
- Repository access error. Socket Error Host not found / Server access error: Socket #110XX Host not found in the local WAPT Configuration window
....

When DNS isn't working, very little works correctly. Could you try using an IP address instead of a machine name in the c:\program files\wapt\wapt-get.ini file? Modify the file, then restart the service, and see if you still have problems. Just in case, do you happen to have a domain name that ends in .local?

Sincerely,

Denis

PS: Could you please give the post a more precise title? The title "multiple errors" is really too vague.