[SOLVED] wapt agent and repo_rules

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
jdziadek
Messages: 47
Registration: January 23, 2023 - 4:10 PM

March 7, 2023 - 09:37

Hello, I have a similar problem. All the packages I updated after declaring the repository are not synchronizing.
When I look at the logs:

Code: Select all

Exception: Downloaded file https://xxxxxx/wapt/Packages sha256 xxxxxx does not match expected yyyyyy
Debian 11
WAPT Version: 2.4.0.14143
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

March 8, 2023 - 11:28

I solved my problem.
In fact, in the file /opt/wapt/wapt-get.ini I modified the path: local_repo_path=/home/wapt
and therefore in nginx I had to change the configuration so that nginx points to the local_repo_path.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

March 8, 2023 - 12:14

Indeed, if you modify the path, you must update it on the nginx system.
Thanks Guillaume for your feedback, :-)
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
x-davidl
Messages: 38
Registration: Apr 25, 2022 - 5:07 p.m.

March 8, 2023 - 2:46 PM

For jdziadek, it looks like the sync.json file doesn't seem to be the same between the source repository and the mirror machine.

Regards
jdziadek
Messages: 47
Registration: January 23, 2023 - 4:10 PM

March 10, 2023 - 08:33

x-davidl wrote: March 8, 2023 - 2:46 PM for jdziadek, it looks like the sync.json file doesn't seem to be the same between the source repository and the mirror machine.

Regards
Hello, my server-side json.sync is indeed old; it lists old packages and not new ones, so it makes sense that it's failing. How can I regenerate it properly?
Julian
Debian 11
WAPT Version: 2.4.0.14143
Locked