Hello,
I just joined the forum following the JRES Marseille conference.
I'm having the problem of the message "SubjectAltNameWarning: Certificate for 'my server' has no `subjectAltName`" because I had version 1.7 which I upgraded to 2.2. Before buying my 200 licenses, I'd like to resolve this small issue. :D ...
The search returned 3 results
- June 9, 2022 - 12:11
- Forum: WAPT Server
- Subject: [SOLVED] SubjectAltNameWarning
- Answers: 13
- Views : 11543
- April 29, 2020 - 4:28 PM
- Forum: WAPT Packages
- Subject: version in registry does not match
- Answers: 2
- Views : 2879
Re: version in registry does not match
Okay, thank you for your reply. I'm not very proficient in Python yet, and I'm still working on consulting the WAPT documentation 
.
.- April 29, 2020 - 2:56 PM
- Forum: WAPT Packages
- Subject: version in registry does not match
- Answers: 2
- Views : 2879
version in registry does not match
Hello,
Below is my configuration:
WAPT Server version: 1.7.4 on Debian 9
WAPT Agent version: 1.7.4.6229
Database status: OK (1.7.4.0)
Windows 10 console on Oracle VM VirtualBox
Following the JRES, I am testing WAPT and starting on packaging. I don't know Python, but I have done some work before...
Below is my configuration:
WAPT Server version: 1.7.4 on Debian 9
WAPT Agent version: 1.7.4.6229
Database status: OK (1.7.4.0)
Windows 10 console on Oracle VM VirtualBox
Following the JRES, I am testing WAPT and starting on packaging. I don't know Python, but I have done some work before...
