<?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[DNSCrypt with pfSense 2.3.1]]></title><description><![CDATA[<p dir="auto">I've had DNSCrypt setup and working since 2.2. I installed pkg and the dnscrypt-proxy pkg and setup the start up script</p>
<p dir="auto">When I upgraded to 2.3 everything worked ok. I've now upgraded to 2.3.1 and DNSCrypt does not start. When I try to manually start it via the script I get:</p>
<pre><code>Starting dnscrypt_proxy.
Shared object "libsodium.so.13" not found, required by "dnscrypt-proxy"
/usr/local/etc/rc.d/dnscrypt-proxy.sh: WARNING: failed to start dnscrypt_proxy
</code></pre>
<p dir="auto">I googled it and found this reference to FreeBSD: https://github.com/jedisct1/dnscrypt-proxy/issues/242</p>
<p dir="auto">But the proposed fix doesn't seem to work (and the listed script doesn't match exactly what I have already)</p>
<p dir="auto">Anyone else have DNSCrypt working on 2.3.1 or know how to fix?</p>
]]></description><link>https://forum.netgate.com/topic/100123/dnscrypt-with-pfsense-2-3-1</link><generator>RSS for Node</generator><lastBuildDate>Wed, 17 Jun 2026 04:40:43 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/100123.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 19 May 2016 00:14:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DNSCrypt with pfSense 2.3.1 on Fri, 20 May 2016 20:52:52 GMT]]></title><description><![CDATA[<p dir="auto">you have to update dnscrypt to latest version (use 18 version)</p>
<p dir="auto">https://forum.pfsense.org/index.php?topic=111895.0</p>
]]></description><link>https://forum.netgate.com/post/626224</link><guid isPermaLink="true">https://forum.netgate.com/post/626224</guid><dc:creator><![CDATA[yop038]]></dc:creator><pubDate>Fri, 20 May 2016 20:52:52 GMT</pubDate></item><item><title><![CDATA[Reply to DNSCrypt with pfSense 2.3.1 on Thu, 19 May 2016 01:27:57 GMT]]></title><description><![CDATA[<p dir="auto">Yes, I ran in to this myself.</p>
<p dir="auto">I "fixed" it by making a symbolic link in /usr/local/lib from libsodium.so.18 to libsodium.so.13:</p>
<p dir="auto">ln -s libsodium.so.18 libsodium.so.13</p>
<p dir="auto">After that it worked again.</p>
<p dir="auto">I have no idea what side effects this may have.</p>
]]></description><link>https://forum.netgate.com/post/625728</link><guid isPermaLink="true">https://forum.netgate.com/post/625728</guid><dc:creator><![CDATA[ESPNSTI]]></dc:creator><pubDate>Thu, 19 May 2016 01:27:57 GMT</pubDate></item></channel></rss>