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.
Restricted access
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
-
Pierre MARION
- Messages: 2
- Registration: Nov 09, 2017 - 03:43
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?
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?
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
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.
