You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Uday Upadhyay <uu...@esri.com.INVALID> on 2025/04/10 06:44:43 UTC
Your connection is not private Issue
Hi,
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.
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!
RE: Your connection is not private Issue
Posted by Uday Upadhyay <uu...@esri.com.INVALID>.
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.xxxx.com
DNS.2 = tpsdashboardha
DNS.3 = tpsdashboard.xxxx.com
DNS.4 = tpsdashboard
DNS.5 = tpsdashboard-dev.xxxx.com
DNS.6 = tpsdashboard-dev
DNS.7 = tps_app.xxxx.com
DNS.8 = tps_app
DNS.9 = tps_app2.xxxx.com
DNS.10 = tps_app2
DNS.11 = tps_app3.xxxx.com
DNS.12 = tps_app3
DNS.13 = tps_app-dev.xxxx.com
DNS.14 = tps_app-dev
DNS.15 = tps_app-dev2.xxxx.com
DNS.16 = tps_app-dev2
EOF
[cid:image002.png@01DBAA6E.B5FAAB30]
Thanks
-----Original Message-----
From: Peter Kreuser <lo...@kreuser.name>
Sent: Thursday, April 10, 2025 1:46 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: Re: Your connection is not private Issue
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://urldefense.com/v3/__https://tpsdashboard-dev.xxxx.com/tpsDash<https://urldefense.com/v3/__https:/tpsdashboard-dev.xxxx.com/tpsDash>
>> board/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uu
>> Uf0zQeRGkVfS1Jp7B090BEidDsddA0$ [tpsdashboard-dev[.]xxxx[.]com]
>> Working Fine Working Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app-dev2.xxxx.com/tpsDashboar<https://urldefense.com/v3/__https:/tps_app-dev2.xxxx.com/tpsDashboar>
>> d/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0z
>> QeRGkVfS1Jp7B090BEiO7zzUNc$ [tps_app-dev2[.]xxxx[.]com] Working Fine
>> Working Fine Working Fine
>> https://urldefense.com/v3/__https://tpsdashboard-dev/tpsDashboard/__<https://urldefense.com/v3/__https:/tpsdashboard-dev/tpsDashboard/__>;
>> !!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGk
>> VfS1Jp7B090BEifI8g7Cc$ [tpsdashboard-dev] Working Fine Working Fine
>> Working Fine
>> https://urldefense.com/v3/__https://tps_app-dev2/tpsDashboard/__;!!CK<https://urldefense.com/v3/__https:/tps_app-dev2/tpsDashboard/__;!!CK>
>> ZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1
>> Jp7B090BEiD28JzWg$ [tps_app-dev2] Working Fine Working Fine Working
>> Fine URLs Production:
>> https://urldefense.com/v3/__https://tpsdashboard.xxxx.com/tpsDashboar<https://urldefense.com/v3/__https:/tpsdashboard.xxxx.com/tpsDashboar>
>> d/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0z
>> QeRGkVfS1Jp7B090BEisttx9wI$ [tpsdashboard[.]xxxx[.]com] Working Fine
>> Working Fine Working Fine
>> https://urldefense.com/v3/__https://tpsdashboardha.xxxx.com/tpsDashbo<https://urldefense.com/v3/__https:/tpsdashboardha.xxxx.com/tpsDashbo>
>> ard/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf
>> 0zQeRGkVfS1Jp7B090BEiZkiO5ec$ [tpsdashboardha[.]xxxx[.]com] Working
>> Fine Working Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app2.xxxx.com/tpsDashboard/__<https://urldefense.com/v3/__https:/tps_app2.xxxx.com/tpsDashboard/__>
>> ;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRG
>> kVfS1Jp7B090BEiu-4-8yE$ [tps_app2[.]xxxx[.]com] Working Fine Working
>> Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app3.xxxx.com/tpsDashboard/__<https://urldefense.com/v3/__https:/tps_app3.xxxx.com/tpsDashboard/__>
>> ;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRG
>> kVfS1Jp7B090BEiCiNnC_0$ [tps_app3[.]xxxx[.]com] Working Fine Working
>> Fine Working Fine
>> https://urldefense.com/v3/__https://tpsdashboard/tpsDashboard/__;!!CK<https://urldefense.com/v3/__https:/tpsdashboard/tpsDashboard/__;!!CK>
>> ZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1
>> Jp7B090BEiC7KVaXk$ [tpsdashboard] Not Working Not Working Not Working
>> https://urldefense.com/v3/__https://tpsdashboardha/tpsDashboard/__<https://urldefense.com/v3/__https:/tpsdashboardha/tpsDashboard/__>;!!
>> CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVf
>> S1Jp7B090BEifxZllNY$ [tpsdashboardha] Not Working Not Working Not
>> Working
>> https://urldefense.com/v3/__https://tps_app2/tpsDashboard/__;!!CKZwjT<https://urldefense.com/v3/__https:/tps_app2/tpsDashboard/__;!!CKZwjT>
>> OV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1Jp7B
>> 090BEiZkaLxRE$ [tps_app2] Working Fine Working Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app3/tpsDashboard/__;!!CKZwjT<https://urldefense.com/v3/__https:/tps_app3/tpsDashboard/__;!!CKZwjT>
>> OV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1Jp7B
>> 090BEilCDzF44$ [tps_app3] Working Fine Working Fine Working Fine
>> Thank you!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org<ma...@tomcat.apache.org>
> For additional commands, e-mail: users-help@tomcat.apache.org<ma...@tomcat.apache.org>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org<ma...@tomcat.apache.org>
For additional commands, e-mail: users-help@tomcat.apache.org<ma...@tomcat.apache.org>
Re: Your connection is not private Issue
Posted by Robert Turner <rt...@e-djuster.ca.INVALID>.
Details on testssl.sh are available on their web site: https://testssl.sh/
You can run it from any computer against the target computer. Best to run
it on a *nix style computer, or from WSL if running on Windows is your only
option.
On Fri, Apr 11, 2025 at 12:48 AM Uday Upadhyay <uu...@esri.com.invalid>
wrote:
> 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 <lo...@kreuser.name>
> Sent: Thursday, April 10, 2025 1:46 PM
> To: Tomcat Users List <us...@tomcat.apache.org>
> Subject: Re: Your connection is not private Issue
>
>
> 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 <
> chris@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://urldefense.com/v3/__https://tpsdashboard-dev.xxxx.com/tpsDash
> >> board/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uu
> >> Uf0zQeRGkVfS1Jp7B090BEidDsddA0$ [tpsdashboard-dev[.]xxxx[.]com]
> >> Working Fine Working Fine Working Fine
> >> https://urldefense.com/v3/__https://tps_app-dev2.xxxx.com/tpsDashboar
> >> d/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0z
> >> QeRGkVfS1Jp7B090BEiO7zzUNc$ [tps_app-dev2[.]xxxx[.]com] Working Fine
> >> Working Fine Working Fine
> >> https://urldefense.com/v3/__https://tpsdashboard-dev/tpsDashboard/__;
> >> !!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGk
> >> VfS1Jp7B090BEifI8g7Cc$ [tpsdashboard-dev] Working Fine Working Fine
> >> Working Fine
> >> https://urldefense.com/v3/__https://tps_app-dev2/tpsDashboard/__;!!CK
> >> ZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1
> >> Jp7B090BEiD28JzWg$ [tps_app-dev2] Working Fine Working Fine Working
> >> Fine URLs Production:
> >> https://urldefense.com/v3/__https://tpsdashboard.xxxx.com/tpsDashboar
> >> d/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0z
> >> QeRGkVfS1Jp7B090BEisttx9wI$ [tpsdashboard[.]xxxx[.]com] Working Fine
> >> Working Fine Working Fine
> >> https://urldefense.com/v3/__https://tpsdashboardha.xxxx.com/tpsDashbo
> >> ard/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf
> >> 0zQeRGkVfS1Jp7B090BEiZkiO5ec$ [tpsdashboardha[.]xxxx[.]com] Working
> >> Fine Working Fine Working Fine
> >> https://urldefense.com/v3/__https://tps_app2.xxxx.com/tpsDashboard/__
> >> ;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRG
> >> kVfS1Jp7B090BEiu-4-8yE$ [tps_app2[.]xxxx[.]com] Working Fine Working
> >> Fine Working Fine
> >> https://urldefense.com/v3/__https://tps_app3.xxxx.com/tpsDashboard/__
> >> ;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRG
> >> kVfS1Jp7B090BEiCiNnC_0$ [tps_app3[.]xxxx[.]com] Working Fine Working
> >> Fine Working Fine
> >> https://urldefense.com/v3/__https://tpsdashboard/tpsDashboard/__;!!CK
> >> ZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1
> >> Jp7B090BEiC7KVaXk$ [tpsdashboard] Not Working Not Working Not Working
> >> https://urldefense.com/v3/__https://tpsdashboardha/tpsDashboard/__;!!
> >> CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVf
> >> S1Jp7B090BEifxZllNY$ [tpsdashboardha] Not Working Not Working Not
> >> Working
> >> https://urldefense.com/v3/__https://tps_app2/tpsDashboard/__;!!CKZwjT
> >> OV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1Jp7B
> >> 090BEiZkaLxRE$ [tps_app2] Working Fine Working Fine Working Fine
> >> https://urldefense.com/v3/__https://tps_app3/tpsDashboard/__;!!CKZwjT
> >> OV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1Jp7B
> >> 090BEilCDzF44$ [tps_app3] Working Fine Working Fine Working Fine
> >> Thank you!
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
RE: Your connection is not private Issue
Posted by Uday Upadhyay <uu...@esri.com.INVALID>.
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 <lo...@kreuser.name>
Sent: Thursday, April 10, 2025 1:46 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: Re: Your connection is not private Issue
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://urldefense.com/v3/__https://tpsdashboard-dev.xxxx.com/tpsDash
>> board/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uu
>> Uf0zQeRGkVfS1Jp7B090BEidDsddA0$ [tpsdashboard-dev[.]xxxx[.]com]
>> Working Fine Working Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app-dev2.xxxx.com/tpsDashboar
>> d/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0z
>> QeRGkVfS1Jp7B090BEiO7zzUNc$ [tps_app-dev2[.]xxxx[.]com] Working Fine
>> Working Fine Working Fine
>> https://urldefense.com/v3/__https://tpsdashboard-dev/tpsDashboard/__;
>> !!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGk
>> VfS1Jp7B090BEifI8g7Cc$ [tpsdashboard-dev] Working Fine Working Fine
>> Working Fine
>> https://urldefense.com/v3/__https://tps_app-dev2/tpsDashboard/__;!!CK
>> ZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1
>> Jp7B090BEiD28JzWg$ [tps_app-dev2] Working Fine Working Fine Working
>> Fine URLs Production:
>> https://urldefense.com/v3/__https://tpsdashboard.xxxx.com/tpsDashboar
>> d/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0z
>> QeRGkVfS1Jp7B090BEisttx9wI$ [tpsdashboard[.]xxxx[.]com] Working Fine
>> Working Fine Working Fine
>> https://urldefense.com/v3/__https://tpsdashboardha.xxxx.com/tpsDashbo
>> ard/__;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf
>> 0zQeRGkVfS1Jp7B090BEiZkiO5ec$ [tpsdashboardha[.]xxxx[.]com] Working
>> Fine Working Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app2.xxxx.com/tpsDashboard/__
>> ;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRG
>> kVfS1Jp7B090BEiu-4-8yE$ [tps_app2[.]xxxx[.]com] Working Fine Working
>> Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app3.xxxx.com/tpsDashboard/__
>> ;!!CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRG
>> kVfS1Jp7B090BEiCiNnC_0$ [tps_app3[.]xxxx[.]com] Working Fine Working
>> Fine Working Fine
>> https://urldefense.com/v3/__https://tpsdashboard/tpsDashboard/__;!!CK
>> ZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1
>> Jp7B090BEiC7KVaXk$ [tpsdashboard] Not Working Not Working Not Working
>> https://urldefense.com/v3/__https://tpsdashboardha/tpsDashboard/__;!!
>> CKZwjTOV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVf
>> S1Jp7B090BEifxZllNY$ [tpsdashboardha] Not Working Not Working Not
>> Working
>> https://urldefense.com/v3/__https://tps_app2/tpsDashboard/__;!!CKZwjT
>> OV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1Jp7B
>> 090BEiZkaLxRE$ [tps_app2] Working Fine Working Fine Working Fine
>> https://urldefense.com/v3/__https://tps_app3/tpsDashboard/__;!!CKZwjT
>> OV!x7gR2k17-ciRQVTf3QF1b9fGZPbEHmDqbyhhcazlMT2wFR4uuUf0zQeRGkVfS1Jp7B
>> 090BEilCDzF44$ [tps_app3] Working Fine Working Fine Working Fine
>> Thank you!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Your connection is not private Issue
Posted by Peter Kreuser <lo...@kreuser.name>.
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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Your connection is not private Issue
Posted by 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org