Tranquil IT Forum

Hello,

I'm currently encountering a "Restricted access" error when trying to install packages on a client machine from an administrator account, but I keep getting the dreaded error message. I can confirm that the package is indeed being sent from the server because when I run an upgrade from the client machine, it installs the packages.

I realize this issue has already been discussed on the forum, but none of the suggested solutions have resolved my problem.

Here's a list of what I've tried:
-ipconfig /flushdns followed by ipconfig /renew
-wapt-get update then wapt-get upgrade
-netsh advfirewall firewall delete rule "waptservice 8088" followed by net stop waptservice and net start waptservice
- The command netsh advfirewall show rule "waptservice 8088" returns the correct settings
- Firewalls are disabled, ports are fully open, and my DNS settings are correct
- Pings are successful in all directions (from client to server, from server to client, from client to admin, from admin to client, from admin to server, from server to admin)
- During installation, "detect DNS" is not checked; I enter the addresses manually (and there are no typos; I proofread beforehand)
- The wapt-get.ini file is correctly configured

I hope you can help me because I've been tearing my hair out over this problem for over a week now.
Thank you in advance.

Hello,

we hope to release version 1.5 of WAPT soon, which will switch to a WebSocket operating mode.

This mode should resolve the issue.

After reviewing the diagnostics, I have no further ideas. You can perform a telnet command from the WAPT server to the client to verify the communication. For example: telnet 192.168.1.123 8088.

Alternatively, you can verify that WAPT is indeed listening on port 8088:

https://www.wapt.fr/fr/doc/Frequent-pro ... re-service

Thanks for the info.
I forgot to mention that I've already checked and it is indeed Wapt listening on the port.
So I think I'll wait for version 1.5. Any idea when it will be released?

Hello,

we are presenting the new version to JRES https://www.jres.org/programme.

The new version is ready; however, we need to write several procedures for the upgrade.
Indeed, there are significant changes:

- Switching from MongoDB to PostgreSQL
- Switching from SHA1 to SHA256 signatures in packages
- Requirement to set a password for the private key!
- ...

Therefore, we need some time to write the cleanest possible procedure.