[RESOLVED] Secondary Repository

[Mickael]

Hello,

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 are using a Raspberry Pi 4B as the remote secondary repository.
Our OS is Debian Bookworm 64, up to date
Agent version: 2.6.1.17472.

When we try 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 get the following message: `THttpClientSocket.OpenBind("info-server":443): Is a server available on this address:port? [remoteip=] [#3 Not Found]`.
If we replace the server name with its IP address, we get the following message: `Access violation`.

Have you ever encountered this problem?

WAPT server version 2.6.1.17472 with an enterprise license

[dcardon]

Hello Mikaël,

From what I remember, 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 please add the line `gzip off;` to your `/etc/nginx/site-enabled/wapt.conf` file? wapt server as 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

Sincerely,

Denis

[Mickael]

Hello,

thank you very much, this solved the problem.
The command `wapt-get reset-config-from-url` worked, and I was able to register the repository using the command `wapt-get register`
. The repository is now present in the WAPT console.

`gzip off;` was missing from the file `/etc/nginx/site-enabled/wapt.conf`.

[dcardon]

Hi Mikaël,

thanks for the feedback. The line in question will be removed during the next update and the launch of postconf.sh. But we'll look into it again to see the source of the problem. It shouldn't be bugging out like that on the Raspberry Pi...

Best regards,

Denis