Your connection to this site is not secure

Help
1

we have react app running with DNS name VMESAS.CO
VMESAS.COM

when i click on VMESAS.co VMESAS.COM connection is secure but when i login from the landing of the website site it is showing "your connection to this site is not secure"

we have configured to call backend api's using https://ip:port/login from react app.

Also, all of sudden we are getting ERR_CERT_COMMON_NAME_INVALID" error when we try to login from the landing page . Some times it works and sometimes it fails.

Please advise what to check and how to fix these 2 issues.

Thanks

1 Like
2

Hello @Mahesh4con, welcome to the Let's Encrypt community. :slightly_smiling_face:

When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Thank you for assisting us in helping YOU!

1 Like
3

Global DNS can't resolve that name.

edit: VMESAS.COM

4 Likes
4

Let’s Encrypt offers Domain Validation (DV) certificates. You are trying to use an IP Address thus the certificate does not cover the IP Address.

4 Likes
6

Hi Bruce,

Thanks for the response, i appreciate . i am new to the community.

My Domain name is VMESAS.COM

How can i use the domain name to call my backend API's.

Let me provide more details.

My domain is: vmesas.com

I ran this command: certbot --nginx -d vmesas.com

It produced this output: it created the .pem files

My web server is (include version): nginx

The operating system my web server runs on is (include version): Ubuntu

My hosting provider, if applicable, is: Oracle Cloud & AWS

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): cerbot 1.21.0

My scenario is i have react app hosted and running in oracle cloud with DNS name. Once i open the landing page i have login and signup pages.

All my backend api's running in aws server.

I generated the certificates in my UI server and copied those certificates to the api server and consuming them in the backend program.

Those URL with IP can't be called but it should called from my react with DNS name only.

Not sure how to fix the issue or what is the best approach to configure my setup.

Thanks

1 Like
7

For HTTPS to your backend setup a subdomain for its IP in your DNS. That must be a unique name from your UI name so maybe like backend.vmesas.com

Then get a cert with that subdomain name and configure your react app to use that. You should run something on your AWS backend server as Let's Encrypt will validate an HTTP Challenge using the IP address in your DNS for that domain. Since that is pointing at your AWS backend server that is where you should handle that. Another option is to use a DNS Challenge which you could do from your UI server (or even somewhere else). But, those are harder to setup and you have the problem of needing to copy the certs securely to your backend server..

In summary, think of those two systems, your UI and your backend, as completely different services needing their own cert for HTTPS.

Some of your recent certs only have the name vmesas.com in it and earlier ones had both that and its www subdomain. A cert must have all the names you might use in a URL for HTTPS to that server. See your cert history below

https://tools.letsdebug.net/cert-search?m=domain&q=vmesas.com&d=168

2 Likes
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.