• Welcome to Web Hosting Community Forum for Webmasters - Web hosting Forum.
 

Recommended Providers

Fully Managed WordPress Hosting
lc_banner_leadgen_3
Fully Managed WordPress Hosting

WordPress Theme

Divi WordPress Theme
WPZOOM

Forum Membership

Forum Membership

nginx is defaulting to the first page that it finds when no SSL in place

Started by bearcatsandor, September 27, 2022, 05:38:52 AM

bearcatsandor

This is a bit of a catch-22.  I'm migrating about 9 sites from someone who is giving up hosting, and is transferring their clients to me.  Right now, I'm working on one of the migrations. I have the wordpress files and database in place and nginx is all set up. I can't create an ssl certificate with certbot yet, because I'm not the authority until the owner points the site's A record at me. No problem. That's how it's supposed to work.

When I attempt to view the site with http and tell my browser (any of them) to ignore the mismatched cert (because it doern't exist), instead of being able to ignore the certificate mismatch warning and view the site anyway, nginx serves the first site with a certificate alphabetically. So when you visit myawesome.com you get a warning, ignore it, and awesome-site.com shows up instead. A little research tells me that this is by nginx design, and it feels wierd. I don't remember this being an issue under Apache.

Because I have nginx configured to always serve https, I can't seem to make an exception for a single site. So I can't view a site before I tell a client to flip the switch! I could self-sign, then revoke-delete that cert when I was done, but that feels cludgy.

Has anyone else run into this? What does one do?