<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Nginx prompts for PEM pass when starting UI (pfSense 2.3-RC)]]></title><description><![CDATA[<p dir="auto">When a password protected key is used to import a SSL certificate, nginx prompts for a PEM password, every time the UI starts.<br />
I'm wondering if this will lock out an admin, after a remote restart.</p>
<p dir="auto">Here's what I saw.</p>
<p dir="auto">When I use StartSSL's recommended CSR command</p>
<pre><code>openssl req -newkey rsa:2048 -keyout yourname.key -out yourname.csr
</code></pre>
<p dir="auto">it mandates assigning a PEM password.</p>
<p dir="auto">When that password protected key is used in an nginx SSL cert<br />
nginx prompts for the PEM pass whenever the webserver is started/restarted.</p>
<p dir="auto">When I restarted pfSense, it paused for the PEM pass, seemingly before loading NAT &amp; rules.<br />
I was at another computer on the LAN and pfSense didn't respond to ping/SSH/WebUI.</p>
<p dir="auto">I had to enter the password at the local console.</p>
<p dir="auto">My impression is that <strong>if I had restarted this pfSense box remotely, it would have been unreachable</strong> until the PEM pass was entered at the local console.<br />
<strong>I did not test</strong> to see if this is actually the case.  Sorry.</p>
<p dir="auto">I opted to strip the password from the key using</p>
<pre><code>openssl rsa -in yourname.key -out yournamenopass.key
</code></pre>
<p dir="auto">and reimport the nginx UI certfificate</p>
]]></description><link>https://forum.netgate.com/topic/97939/nginx-prompts-for-pem-pass-when-starting-ui-pfsense-2-3-rc</link><generator>RSS for Node</generator><lastBuildDate>Tue, 13 Oct 2026 03:46:24 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/97939.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 12 Apr 2016 15:40:42 GMT</pubDate><ttl>60</ttl></channel></rss>