Error on :ERR_CERT_COMMON_NAME_INVALID

Help
1

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:

meet.fun3dchat.com

I ran this command:
NA

It produced this output:
NA

My web server is (include version):

nginx version: nginx/1.14.0 (Ubuntu)

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

Ubuntu 18.04 lts

My hosting provider, if applicable, is:

kimsufi (ovh)

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):
NA

certbot 0.31.0

IP

198.100.144.111

Hi,

We have a nginx webserver with websocket listening port: 4297

We have configured a proxy that listens port: 7777 ssl and forwards it to port: 4297

When we try connecting without using ssl with ws everything works fine, but when we add ssl when our app tries to connect with port: 7777 we get this error in return:

> NET::ERR_CERT_COMMON_NAME_INVALID.

We already did several tests but we always have the same results. What are we doing wrong?

Thank you.

1 Like
2

Hi @IvanZD

there is a working port 443.

Port 7777 doesn't answer. So where runs that port 7777?

Use the port 443 as template.

Additional problem with a wss: Sometimes the ip is used to connect the webservice. That's always wrong, check, if the domain name is used.

1 Like
3

thank you for your help, we've made it work!

2 Likes
4

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