<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Ok I guess I should have been more clear.
This is a debian package issue in that the debian package is linking the default site
default -> /etc/nginx/sites-available/default
Which contains 2 listen lines as I listed before</p>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"> listen 80 default_server;
listen [::]:80 default_server;
After digging further into this I discovered it was IPv6 line that was causing the issue.
listen [::]:80 default_server;
We disable IPv6 on our servers.
I did not run into this on Ubuntu 18.04.
It appears there was a lot of changes to how debian packaged nginx between the 2 OS releases.
With these changes there appears to be a lot of changes to the default.
I suggest not trying to link the default and not attempting to do a restart.
Just a suggestion though. </p>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Now I am trying to find a way to get passed this issue as we build an entire server via debian packages.
I can not have a package error out in my build process.</p>
<p class="message flowed" style="font-family: monospace; padding-top: 8px; margin-top: 0px; border-top: 0px; white-space: pre-wrap; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">
</p>
<div class="moz-cite-prefix">On 10/7/2022 11:45 AM, Debian Bug
Tracking System wrote:<br>
</div>
<blockquote type="cite"
cite="mid:handler.1021393.D1021393.16651573441996461.notifdone@bugs.debian.org">
<pre class="moz-quote-pre" wrap="">This is an automatic notification regarding your Bug report
which was filed against the nginx-common package:
#1021393: error in package nginx-common_1.18.0-6ubuntu14.2_all.deb for ubuntu 22.04 with default enabled site.
It has been closed by Thomas Ward <a class="moz-txt-link-rfc2396E" href="mailto:teward@thomas-ward.net"><teward@thomas-ward.net></a>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Thomas Ward <a class="moz-txt-link-rfc2396E" href="mailto:teward@thomas-ward.net"><teward@thomas-ward.net></a> by
replying to this email.
</pre>
</blockquote>
</body>
</html>