Package xxx: Restricted access

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
angelshurikan
Messages: 9
Registration: Sep 22, 2015 - 08:47

January 26, 2016 - 09:01

Hello,

In the WAPT Console, if I remove or apply a package to a machine, I get the message "Package xxx: Restricted access".

Could someone please help me, as I don't know how to resolve this issue?

Sincerely,
rylo
Messages: 8
Registration: Apr 26, 2016 - 10:14

April 26, 2016 - 10:27

Hello everyone,

I'm trying to use WAPT, which I installed on a Debian server, but I keep getting a "restricted access" error. I'm the administrator of all the workstations and the domain. There's no proxy; I've configured the domain's DNS settings. I can't figure out what's wrong. Sometimes I manage to install a package, but when I uninstall it manually and try to reinstall it through WAPT, I still get the "restricted access" message and can't install it. I see you haven't replied to the previous post. Should I assume the solution is simple? Or is it explained on the WAPT website?

If someone could shed some light on this, I'd really appreciate it because I'm completely stuck. I've been working on this for two days and haven't found anything online (even though I've done quite a bit of searching). I tested it in September 2015 and I don't remember these error messages.

Thanks in advance for your help.

Rylo
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

April 26, 2016 - 10:52

Good morning

Several solutions have helped me; to test them, do a:

Code: Select all

net stop waptservice
net start waptservice
Then try again from the wapt console. That will help to define the problem.

Otherwise, is port 8088 properly open for clients?

And most importantly:

In the file c:\wapt\wapt-get.ini, is the "wapt_server=" field correct?

(The IP address or DNS must be correct)

Otherwise
rylo
Messages: 8
Registration: Apr 26, 2016 - 10:14

April 26, 2016 - 3:04 PM

Yes, when I telnet to port 8088 it works, the `waptget ini` file is correctly configured.

I stopped and restarted the service, but it didn't change anything. I don't understand what's happening. We don't have a proxy, no firewall, we're on a local network. There's a Karpersky agent that might be the cause, but if telnet works, it doesn't seem to be that, but I could be wrong.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

April 26, 2016 - 3:11 PM

Can you tell me if you are using a Linux or Windows server?
rylo
Messages: 8
Registration: Apr 26, 2016 - 10:14

April 26, 2016 - 4:17 PM

It was a DNS problem on the domain controller.
Thanks for the help.
Locked