Cert of site1 being served for site2

Help
1

I have a running instance of Jitsi Meet server on NGINX/Ubuntu 18.04 (meet.melodrom.ru)
I’m trying to add a Wordpress site on the same NGINX

certbot --nginx runs OK for both sites;
certbot renew --dry-run runs fine;

however, when I try to access self.cash it is served with cert of meet.melodrom.ru

My domain is: self.cash

I ran this command: wget https://self.cash

It produced this output:

–2020-04-23 01:19:15-- https://self.cash/
Resolving self.cash (self.cash)… 134.209.186.248
Connecting to self.cash (self.cash)|134.209.186.248|:443… connected.
ERROR: no certificate subject alternative name matches
requested host name ‘self.cash’.
To connect to self.cash insecurely, use `–no-check-certificate’.

My web server is (include version): NGINX

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

My hosting provider, if applicable, is: DO

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): certbot 0.31.0

1 Like
2

The problem is within the web server configuration.

DNS resolves both names to the same IP:

Name:    self.cash
Address:  134.209.186.248

Name:    meet.melodrom.ru
Address:  134.209.186.248
1 Like
3

yes they are on the same IP.
Please let me know if I miss something regarding SNI in my configs, etc

4

Most likely, yes, the web server has failed to match the self.cash requests to a specific virtual host and is instead serving the default site.

1 Like
5

But what could that be?

6

Try this command:
nginx -T | grep server_name

[maybe it will shed some light on the problem]

1 Like
7

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