Hello,
I'm working on WAPT as an intern and I'm stuck on a repository problem.
Since I'm testing the software so my supervisor can then reuse my work, I don't have anyone on-site to help me solve the problem.
When I go to the private repository tab in the console, it remains empty despite the fact that I've imported several packages (both from a repository and a file), packages which are definitely on my server since I can see their presence by clicking on the private repository tab in the web console.
Have I missed a step in the installation? Is this an error?
Thank you for your attention. Sincerely,
Libersa.
WAPT console and private repository (error)
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
On the server, in the same directory as the packages, there must be a "Packages" file.
This is the package index. This is the file that is read to display the list of packages in the console or that is read by client PCs to find out the latest versions of the packages.
This file is updated each time a new package is uploaded to the server.
Check that this file exists (it is actually a zip file) in the private repository tab and that its date is more recent than all the packages... and that it is accessible via http.
Using the command prompt (cmd) as administrator, test the following commands:
This is the package index. This is the file that is read to display the list of packages in the console or that is read by client PCs to find out the latest versions of the packages.
This file is updated each time a new package is uploaded to the server.
Check that this file exists (it is actually a zip file) in the private repository tab and that its date is more recent than all the packages... and that it is accessible via http.
Using the command prompt (cmd) as administrator, test the following commands:
wapt-get -ldebug --direct update
wapt-get search
Tranquil IT
Hello,
I see I forgot to mention that my server was running Debian when I wrote my message, so regarding the commands, I would appreciate their Linux equivalents (sorry for the oversight).
As for the "Packages" file, I can see that it is indeed present via the web console and that it updated along with the last imported package. However, nothing is displayed in the private repository tab of the console.
Regarding HTTP accessibility, I can download the file via the private repository in the web console, if I understand the question correctly, but it doesn't give me a zip file.
Thank you for your reply.
I see I forgot to mention that my server was running Debian when I wrote my message, so regarding the commands, I would appreciate their Linux equivalents (sorry for the oversight).
As for the "Packages" file, I can see that it is indeed present via the web console and that it updated along with the last imported package. However, nothing is displayed in the private repository tab of the console.
Regarding HTTP accessibility, I can download the file via the private repository in the web console, if I understand the question correctly, but it doesn't give me a zip file.
Thank you for your reply.
In the console, check the repository URL in the Tools / Local WAPT Configuration menu
main repository URL
The
http://mywaptserver.mylocaldomain/wapt
(note the /wapt at the end).
Then, click the "Refresh Available Packages" button in the "Private Repository" tab.
Are you using a proxy?
main repository URL
The
http://mywaptserver.mylocaldomain/wapt
(note the /wapt at the end).
Then, click the "Refresh Available Packages" button in the "Private Repository" tab.
Are you using a proxy?
Tranquil IT
Thanks, problem solved!
The repository URL was written as an IP address: https://192.168.xxx.xxx.
I modified it to add /wapt to the end, and the repository now displays correctly.
Thank you for your help, and best of luck with your project.
The repository URL was written as an IP address: https://192.168.xxx.xxx.
I modified it to add /wapt to the end, and the repository now displays correctly.
Thank you for your help, and best of luck with your project.
