Using certbot with 2 different domains causes DNS_PROBE_FINISHED_NXDOMAIN

Help
1

I have a domain that is chat.adm.br with several subdomains with certs enabled in my ubuntu server with nginx. Now I'm trying to enable HTTPS for another domain equiparcarrocerias.com.br AND www.equiparcarrocerias.com.br . It used to work in the past, not sure why it's not working now.

This is probably relevant: this exact same setup worked and loaded the site, then the company that hosts the DNS servers for the EQUIPAR domain had errors, and the provider just changed the domain DNS server IPs. Before it broke, this site worked normally. Now with the new DNS servers and the DNS pointing to the correct server ip, it gives this dns error. I just regenerated all certificates.

The certificate generation went smoothly:

668×514 22.8 KB

My Steps:

  1. Had chat.adm.br and subomains configured
  2. Added equiparcarrocerias.com.br and www.equiparcarrocerias.com.br (they point to the correct server ip checked with DNSChecker)
  3. certs generated normally, opted with "Expand" certificate
  4. equiparcarrocerias shows DNS_PROBE_FINISHED_NXDOMAIN error

The NGINX file just points directly to the /var/www/equipar/index.htm file, it worked normally before. I'm not sure if this is the problem but in the equiparcarrocerias.com.br NGINX file the certificate seems to be from the other site, chat.adm.br, but I guess this file includes the equiparcarrocerias certificate keys. Is this correct, or should the EQUIPARCARROCERIAS nginx file include a separate certificate just for this site? Image of what I'm talking about:
Tabby_hhDlGO1Agx


My domain is:  chat.adm.br AND equiparcarrocerias.com.br 

I ran this command: sudo certbot --nginx

It produced this output: OK generated all certs normally. Used "Expand" option

My web server is (include version): nginx version: nginx/1.18.0 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-105-generic x86_64)

My hosting provider, if applicable, is: Hetzner

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): 2.10.0
2

You mean when you enter the hostname in your browser? Because such a "DNS_PROBE_FINISHED_NXDOMAIN" in your browser is not related to the certificate, but to local DNS resolving.

2 Likes
3

Yes when i load in the browser. Is the site working for you? haha

4

Works just fine. I see some images of trucks in the background :slight_smile:

2 Likes
5

Oh great haha, I just disabled my cloudflare WARP and it works now. Thanks :joy:

2 Likes
6

image
Are you running both?
Are they doing what you expect?

2 Likes
7

Actually I installed Apache to test some random app, but I don't use it atm for anything. I don't remember if I succeeded or not

I'm not even sure if it's possible to use both at the same time, I know I can set the 80 port to 81 but I think it's impossible because all web servers need to use port 443 specifically or something for some reason I don't know.

I don't really know much about writing nginx/apache config, my use for it is using nginx template file to point domain to the right app's port and that's it

8

If you don't need Apcahe, then you should uninstall it.
[it costs nothing to reinstall in the future - if you should ever need it again]

2 Likes
9

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