Public bug reported: We have a cronjob that regularly regenerates vhost configs from a template, renews certificates and reloads nginx.
Lately, we are frequently seeing an error where during a short window, nginx serves the wrong site & certificate are served by nginx. For instance, I see this error log entry: 2021/08/04 06:53:19 [error] 2296834#2296834: *618991 connect() failed (111: Connection refused) while connecting to upstream, client: 2604:a880:400:d0::1d78:1001, server: onlyoffice.*****.org, request: "GET /wp-login.php HTTP/1.1", upstream: "http://[::1]:8910/wp-login.php";, host: "****.net" The domain which is served in place of the one which was requested is NOT the default server, instead, it is one whose config hasn't been regenerated because it has a custom config that is exempt from being automatically regenerated. Again, this erroneous behaviour seems to last only for a very short while, but this is enough to e.g. cause a Nextcloud client to complain about the wrong certificate and stop synchronizing. ** Affects: nginx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938857 Title: nginx serves wrong site while config is being reloaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1938857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
