Hello,

I understand your need for security, but unfortunately I don't think it's possible this way. You can still try entering the following address for the server (source) in your console to check if it's valid, recognized, and working:

<user>:<password ...

Hello,

thank you for your feedback. It's not very reassuring, but I suppose my habit of waiting a bit before updating has paid off this time! Let's hope this problem is fixed soon, because in the meantime I can't do any upgrades. The old 2.2.3.12463 version is no longer available...

Hello,

For context:
Ubuntu 20.04.5 LTS
WAPT Enterprise 2.2.2.12388

I am trying to migrate waptserver to the latest version reported by my console (v2.2.3.12463), however the following error occurs:

$ sudo apt update
$ sudo apt upgrade -y
> [...]
> E: Failed to ...

Hello,

thank you for your reply. It's a shame that it's not possible yet, but is it something that could be implemented in a future version? For example, via a function that could be implemented in the package?

Best regards

Hello,

I'm running a WAPT Enterprise 2.2.2.12388 server on Ubuntu.

My question concerns the upgrade_package functionality available in WAPT packages. I understand that this function allows you to define how the package should be updated; however, I can't figure out how to...

Thanks Florian.

Unfortunately, even modifying the package didn't have the desired effect. I had to adapt the code using the following approach for it to finally work (without removing the parameters and the "default_global" section); my packages are installed, but the configuration file...

Yes, it's only available with an enterprise license. If the menus aren't grayed out in the console, that's an error; we must have missed that during the merging of the enterprise and community code into a single binary.


So, as someone with the Enterprise version, I'd be interested to know if my...

Great, I'll add testing the DNS fallback removal to my to-do list, thanks for the tip

In your network configuration, at the DNS level, is there no fallback to 8.8.8.8, for example?


I do have a fallback to an external DNS server, but not for ".local" addresses, which are resolved internally. That said, I migrated to version 2.2.2 and deployed the new agents this week...

Hello,

I have a similar problem, though perhaps not 100% identical (WAPT 2.2.2 Enterprise version). I'll still report it here: when I deploy a copy of tis-wapt-conf-policy with the following content, the deployment goes smoothly:

def install():
print ...