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 
> <ch...@christopherschultz.net>:
> 
> 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 development 
>> environment URLs work well with or without domain names.
>> I have verified that the SSL certificate is properly configured with the 
>> correct subject alternative names.
>> Any guidance or suggestions on how to resolve this would be greatly 
>> appreciated.
> 
> Usually the browser will tell you why it's showing that particular error. Can 
> you get more information? For example "the certificate is self-signed" or 
> "the certificate has expired" or "the hostname for the certificate does not 
> match the hostname for the site"?
> 
> -chris
> 
>>  Tomcat Apache Version 10.1.39 is running on Microsoft Windows Server 2022 
>> Standard.
>> The application server is running on the Windows cluster: tps_app2 and 
>> tps_app3.
>> The database server is running on the SQL Server cluster.
>> Below is the list of URLs and Browsers on which they are running fine 
>> without any message.
>> URLs Development:
>> Chrome
>> Firefox
>> Edge
>> https://tpsdashboard-dev.xxxx.com/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tps_app-dev2.xxxx.com/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tpsdashboard-dev/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tps_app-dev2/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> URLs Production:
>> https://tpsdashboard.xxxx.com/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tpsdashboardha.xxxx.com/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tps_app2.xxxx.com/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tps_app3.xxxx.com/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tpsdashboard/tpsDashboard/
>> Not Working
>> Not Working
>> Not Working
>> https://tpsdashboardha/tpsDashboard/
>> Not Working
>> Not Working
>> Not Working
>> https://tps_app2/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> https://tps_app3/tpsDashboard/
>> Working Fine
>> Working Fine
>> Working Fine
>> Thank you!
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to