Page 1 of 1

Secondary repository configuration

Published: July 23, 2026 - 2:42 PM
by Mickael
Good morning,

We want to install a secondary repository on a remote site.
We received a procedure from a Tranquil IT technician, which we are following to the letter, but we are encountering some problems.

We use a Raspberry Pi 4B as a remote secondary repository.
Debian Bookworm 64 OS up to date

Server web page information
WAPT Server version: 2.6.1.17834
WAPT Agent version: 2.6.1.17834
WAPT Setup version: 2.6.1.17834
WAPT Deploy version: 2.6.1.17834
company license

When we want to configure the agent with the command sudo wapt-get reset-config-from-url https://"info retrieved from our wapt server's web page"

We have the following message: Access violation

We had already encountered this problem some time ago.

Here is the solution that was provided.
Links: viewtopic.php?t=4495
From what I recall, we previously encountered a gzip support bug on Raspberry Pis as a secondary repository. I thought it had been fixed, but it seems that's not the case... Could you add the line `gzip off;` to your `/etc/nginx/site-enabled/wapt.conf` file on your WAPT server, as shown below?
Code: Select all
...
gzip off;
gzip_min_length 1000;
gzip_buffers 4 8k;
gzip_http_version 1.0;
gzip_disable "msie6";
gzip_types text/plain text/css application/json;
gzip_vary on;
...
Then restart nginx and try syncing your secondary repository again.

Code: Select all

systemctl restart nginx
At the time we performed the procedure and it worked
Today the code is working correctly with gzip vary set to off, on the server side
But we get the error: Access violation


Thank you in advance

Re: Secondary repository configuration

Published: July 24, 2026 - 09:46
by dcardon
Hi Mickaël,

I don't think it's a gzip issue; it should have been fixed some time ago.

If I remember correctly, the custom Raspberry Pi ARM64 kernel introduces (if I recall correctly) non-standard page sizes of 16k which can cause problems [1]. But normally that's for the Pi 5...

However, there were some Access Violation fixes in the latest nightly build [2]. Could you just update the agent on the Raspberry Pi 4?

Regards,

Denis

[1] https://www.raspberrypi.com/documentati ... tml#kernel
[2] https://wapt.tranquil.it/wapt/nightly/w ... -d924c912/