Page 2 of 2
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 09:16
by sfonteneau
We were able to reproduce the problem.
In our tests, there were no issues since we followed the documentation:
https://www.wapt.fr/fr/doc/Installation ... du-serveur. The
`/etc/hostname` and `/etc/hosts` files should return the server's FQDN: srvwapt.mydomain.lan.
In your case, the name displayed must be a short name, I assume.
We'll implement a fix anyway.
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 09:20
by Imp83
That's it!!! Everything is working again at my place!
Thank you so much!
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 09:21
by Anthony Jimenez
No short name, I do have the FQDN name in both files
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 09:24
by sfonteneau
Anthony JIMENEZ wrote: ↑March 28, 2018 - 09:21
No short name, I do have the FQDN in both files
Perhaps you could post in a different topic because your problem is clearly different.
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 11:44
by joris.remandet
It's working again, however I'm getting errors when running WAPTDeploy
Code: Select all
X:\WAPT>waptdeploy --hash=c5cf5fc9790cbeea7ec06fe4655cdcb8f6d4e90183c5877d08cb48a50e20305f --minvers
ion=1.5.1.22 --wait=15 --force
WAPT version:
WAPT required version: force
Wapt agent path: C:\Users\ADMINI~1.AV3\AppData\Local\Temp\waptagent.exe
Wget new waptagent from https://wapt-srv.lmaccassin.loc/wapt/waptagent.exe
Trying to reach https://wapt-srv.lmaccassin.loc/wapt/waptagent.exe...
Reachable, downloading...
Done.
Cleanup...
An unhandled exception occurred at $004161A8:
EFOpenError: Unable to open file "C:\Users\ADMINI~1.AV3\AppData\Local\Temp\waptagent.exe"
$004161A8
$00416050
$0043FBE6
$0040438C
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 12:14
by sfonteneau
In my opinion, it will work better if we execute it with the argument:
Code: Select all
--waptsetupurl=http://wapt.mydomain.lan/wapt/waptagent.exe
Note that you must specify http and not https
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: March 28, 2018 - 12:40
by joris.remandet
Despite using the --waptsetupurl parameter, I'm still getting the same error. It manages to download, but it's as if it can't complete a task. Visually, it seems to crash when the service tries to register with the server (since the IP address is the client's localhost)...
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: April 5, 2018 - 6:51 PM
by htouvet
At the end of the installation, waptdeploy sends a request to
http://127.0.0.1:8088/update to force the local wapt service (which has started by this point) to retrieve the index of available packages.
The error is likely due to this; that is, the service hasn't fully started yet, and waptdeploy isn't waiting long enough.
You can try with waptdeploy version 1.5.1.23:
https://wapt.tranquil.it/wapt/releases/ ... deploy.exe
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: April 6, 2018 - 9:18 AM
by joris.remandet
I probably also had some machine issues, because I tried again on new machines, and it worked without any problems. So, on the older ones, what I usually do is delete the WAPT client and reinstall it manually (this is quite rare because I use the --force parameter, which works very well).
I'll manage, because our organization has decided to change our deployment solution to an all-in-one (the KACE solution from Qwest). It's a shame because I was really starting to get used to WAPT (even creating packages).
Re: WAPT 1.5.1.22 No longer able to connect to WAPTConsole
Published: April 9, 2018 - 11:42 PM
by vcardon
joris.remandet wrote: ↑Apr 6, 2018 - 09:18
I'll make do because our community has decided to change our deployment solution to an all-in-one (KACE solution from the publisher Qwest). It's a shame because I was really starting to get used to WAPT (even creating packages).
Good luck, our emotions are with you.
There's room for those who deliver and room for those who make promises. Your bosses needed to make a quick decision, that's all. They saw it, it's a good brand, so they went for it, right? The elected officials don't understand and they're bombarded by salespeople from other companies.
Keep learning and training on WAPT, it's the thing that's going to emerge, so your answers to your bosses will very soon become your own, very effective and very relevant.
Vincent