Problem updating from Debian 1.5 to 1.7 9

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
Chuge
Messages: 3
Registration: Sep 10, 2019 - 3:43 p.m.

September 10, 2019 - 3:48 PM

Good morning,
I am encountering a problem when I try to update the WAPT 1.5 community server installed on a Debian 9 system to version 1.7
I'm getting an error message regarding the GPG key

Code: Select all

 GPG error: https://wapt.tranquil.it/debian/wapt-1.7 stretch InRelease: The following signatures were invalid: EXPKEYSIG 58F751F8EE23241E Tranquil IT Systems <contact@tranquil.it>
W: The repository 'https://wapt.tranquil.it/debian/wapt-1.7 stretch InRelease' is not signed.
Do you have a solution?
Regards
Chuge
Messages: 3
Registration: Sep 10, 2019 - 3:43 p.m.

September 11, 2019 - 1:01 PM

Using this command, I no longer get the error message

Code: Select all

 curl -k https://wapt.tranquil.it/debian/wapt-1.7/dists/stretch/InRelease | gpg --keyring /etc/apt/trusted.gpg --verify
the result of this command without the -k
curl https://wapt.tranquil.it/debian/wapt-1. ... /InRelease | gpg --keyring /etc/apt/trusted.gpg --verify
%
Total
%
%
Received https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
gpg: verify signatures failed: Unknown system error
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.

Regards
Chuge
Messages: 3
Registration: Sep 10, 2019 - 3:43 p.m.

September 11, 2019 - 2:20 PM

Upgrade to 1.7 -> OK

But there's still an error message:

Code: Select all

wget -O - https://wapt.tranquil.it/debian/tiswapt-pub.gpg  | apt-key add -
--2019-09-11 13:18:41--  https://wapt.tranquil.it/debian/tiswapt-pub.gpg
Resolving wapt.tranquil.it (wapt.tranquil.it)... 185.16.48.72
Connecting to wapt.tranquil.it (wapt.tranquil.it)|185.16.48.72|:443... connected.
ERROR: The certificate of ‘wapt.tranquil.it’ is not trusted.
ERROR: The certificate of ‘wapt.tranquil.it’ hasn't got a known issuer.
The certificate's owner does not match hostname ‘wapt.tranquil.it’
gpg: no valid OpenPGP data found.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

September 15, 2019 - 7:48 PM

It was a temporary issue on our repo.
It should be working now!
Locked