<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>The dhparam file cam be whichever you want it to be **provided
that** you configure it per server block.</p>
<p>Refer to the config documentation - <a
href="http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_dhparam">http://nginx.org/en/docs/http/ngx_http_ssl_module.html#ssl_dhparam</a>
- and the 'context' being 'http' or 'server' - you can define
different dhparam files for each server block. This said, if you
don't define this each server, it'll disable DHE ciphers (but not
ECDHE ciphers).</p>
<p><br>
</p>
<p>Thomas</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 3/19/20 10:42 AM, q1548 wrote:<br>
</div>
<blockquote type="cite"
cite="mid:39248f0c47c9c378274b05fa6bc1cbf2.NginxMailingListEnglish@forum.nginx.org">
<pre class="moz-quote-pre" wrap="">Hello Maxim,
Thanks for your helps. "http level...", Oh, not just a hardware server,
several different dedicated servers.
When wildcard SSL is used, the CRT file and the KEY file should be the same
in each hardware server, I just want to know, can each server use its
private dhparam file or must I use the same dhparam file? thank you very
much.
Posted at Nginx Forum: <a class="moz-txt-link-freetext" href="https://forum.nginx.org/read.php?2,287383,287385#msg-287385">https://forum.nginx.org/read.php?2,287383,287385#msg-287385</a>
_______________________________________________
nginx mailing list
<a class="moz-txt-link-abbreviated" href="mailto:nginx@nginx.org">nginx@nginx.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a>
</pre>
</blockquote>
</body>
</html>