title: SQL Server service breaks after adding SSL certificates in Linux
body: <p>I have set up a SQL Server database server on my Ubuntu 16 machine. To make it secure over a host network I am working on adding an SSL encryption certificate on it. </p>
  
  <p>I tried following the steps as mentioned on this link <a href="https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-encrypted-connections?view=sql-server-2017" rel="nofollow noreferrer">ssl-encryption-mssql</a></p>
  
  <p>But after restarting the service of SQL Server, it breaks giving the below exit code status</p>
  
  <blockquote>
    <p>code=exited, status=1/FAILURE</p>
  </blockquote>
  
  <p>I even tried to check the logs using <code>journalctl -u mssql-server.service -b</code> but it is not helpful at all. For the referrence, I am adding the screenshot of journalctl command below:</p>
  
  <p><a href="https://i.stack.imgur.com/DedHv.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DedHv.png" alt="output of journalctl"></a></p>
  
  <p>My <code>/var/opt/mssql/mssql.conf</code> looks something like this after following the steps from official doc.</p>
  
  <pre><code>[sqlagent]
  enabled = false
  
  [EULA]
  accepteula = Y
  
  [network]
  tlscert = /etc/ssl/certs/cert.pem
  tlskey = /etc/ssl/private/privkey.pem
  tlsprotocols = 1.2
  forceencryption = 1
  </code></pre>
  
  <p>EDIT-1: I further checked out the logs from /var/log/syslog, it stated the following log-
  <code>Error: 49940, Severity: 16, State: 1.Unable to open one or more of the user-specified certificate file(s). Verify that the certificate file(s) exist with read permissions for the user and group running SQL Server</code> and found this <a href="https://askubuntu.com/questions/1141360/letsencrypt-for-sql-server-on-linux">question</a> which seems similar, I tried the approach as told by Charles but it doesn't seem to work. Even I am using the Let's Encrypt Certificates. </p>
  
  <p>EDIT-2: It is not a licensed version, could this be the reason?</p>
  
  <p>How to resolve this error?</p>