Chris, thanks for the reply.
I have verified that both the hostname for the certificate and the hostname for
the site are correct.
The certificate is not expired right now, and it has almost one year left.
subjectAltName = @alt_names
[alt_names]
DNS.1 = tpsdashboardha..com
DNS.2 = tpsd
Thanks, Peter, for the help.
Could you please provide more insight on the steps to run testssl.sh? We are
using Windows Standard Server 2022.
This will help me.
Thank you.
-Original Message-
From: Peter Kreuser
Sent: Thursday, April 10, 2025 1:46 PM
To: Tomcat Users List
Subject: Re:
Usay,
Could you try tls test tool like testssl.sh on the problematic URLs?
It will tell you the reason...
Peter
> Am 10.04.2025 um 18:50 schrieb Christopher Schultz
> :
>
> Uday,
>
>> On 4/10/25 2:44 AM, Uday Upadhyay wrote:
>> I'm experiencing an issue when accessing the production web s
On 10/04/2025 17:53, Christopher Schultz wrote:
Charles,
On 4/9/25 6:57 PM, Charles Slivkoff wrote:
I noticed this in February and have attempted multiple times to
contact the list owners and have received no response.
There are no posts for Tomcat 10.1.x to tomcat-announce after 33 on
2024-1
Charles,
On 4/9/25 6:57 PM, Charles Slivkoff wrote:
I noticed this in February and have attempted multiple times to
contact the list owners and have received no response.
There are no posts for Tomcat 10.1.x to tomcat-announce after 33 on 2024-11-11.
https://lists.apache.org/thread/pbovsrrm11j
Uday,
On 4/10/25 2:44 AM, Uday Upadhyay wrote:
I'm experiencing an issue when accessing the production web servers without using the
.xxx.com domain. The browser displays a message stating, "Your connection is not
private."
This problem occurs in Edge, Chrome, and Firefox, while the developmen
On 10/04/2025 10:44, Greg Huber wrote:
Hello,
Going through the logs, the session creation was being triggered from
our 403 jsp page (they were not following the robots.txt and got
themselves banned).
10 minutes of log entries: (752 403's)
752 (32.71%) 0 (00.00%) 1.5 MiB (04.64%) 4
Hello,
Going through the logs, the session creation was being triggered from
our 403 jsp page (they were not following the robots.txt and got
themselves banned).
10 minutes of log entries: (752 403's)
752 (32.71%) 0 (00.00%) 1.5 MiB (04.64%) 403 - Forbidden:
Server is refusing to r
