<?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[One way to enable SSL support for the Web UI]]></title><description><![CDATA[<p dir="auto">Here's how I SSL-enabled by NetXMS WebUI, the fast and easy way.  I come from a Linux background so I used stunnel, which is a utility that can SSL-enable any connection quickly and easily.  It is so reliable you forget it is there.  I'm new to the other utility listed here, nssm, but it made creating a new service a piece of cake (yes, I know about sc).</p>
<p dir="auto">System: NetXMS 3.2 listening on the default port of 8080 on Windows Server 2019</p>
<p dir="auto">Download two files:<br />
stunnel from <a href="https://www.stunnel.org/downloads.html" rel="nofollow ugc">https://www.stunnel.org/downloads.html</a><br />
nssm from <a href="http://nssm.cc/download" rel="nofollow ugc">http://nssm.cc/download</a></p>
<p dir="auto">Install stunnel using the installer.  It will have you create a new self-signed certificate.  If you want to use a signed one, there is plenty of info out there on how to do that.  If stunnel starts, stop it using the tray icon or kill it.</p>
<p dir="auto">Edit the stunnel config file (C:\Program Files (x86)\stunnel\config\stunnel.conf) and find the "TLS front-end to a web server" and make it look like this:</p>
<pre><code>; TLS front-end to a web server
[https]
accept  = 443
connect = 8080
cert = stunnel.pem
</code></pre>
<p dir="auto">Download and unzip nssm to c:\software\ or another non-user-specific location (e.g. c:\program files\ ).<br />
Open an Administrative command prompt and run nssm like:</p>
<pre><code>"C:\software\nssm-2.24\win64\nssm.exe" install stunnel
</code></pre>
<p dir="auto">Browse to and select the stunnel executable ("c:\Program Files (x86)\stunnel\bin\stunnel.exe"), enter a description of "SSL for NetXMS" and click "Install Service"<br />
Go to Services and start the service.</p>
<p dir="auto">Browse to your NetXMS server using <a href="https://netxms.my.org/nxmc" rel="nofollow ugc">https://netxms.my.org/nxmc</a>  (don't forget the nxmc).</p>
<p dir="auto">Yes, you have to add the /nxmc at the end.</p>
<p dir="auto">Worked great for me, hope it helps someone else who doesn't want to setup an IIS reverse proxy, etc.  YMMV.</p>
]]></description><link>https://forum.netxms.org/topic/6459/one-way-to-enable-ssl-support-for-the-web-ui</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 11:40:41 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6459.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 21 Mar 2020 20:57:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to One way to enable SSL support for the Web UI on Fri, 27 Mar 2020 14:18:11 GMT]]></title><description><![CDATA[<p dir="auto">You also could just enable SSL in tomcat like described here <a href="https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html" rel="nofollow ugc">https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html</a>.</p>
]]></description><link>https://forum.netxms.org/post/27645</link><guid isPermaLink="true">https://forum.netxms.org/post/27645</guid><dc:creator><![CDATA[maxsubzero]]></dc:creator><pubDate>Fri, 27 Mar 2020 14:18:11 GMT</pubDate></item><item><title><![CDATA[Reply to One way to enable SSL support for the Web UI on Thu, 26 Mar 2020 23:48:07 GMT]]></title><description><![CDATA[<p dir="auto">This worked great for me on Windows 2016.<br />
Thank you</p>
]]></description><link>https://forum.netxms.org/post/27643</link><guid isPermaLink="true">https://forum.netxms.org/post/27643</guid><dc:creator><![CDATA[northstar]]></dc:creator><pubDate>Thu, 26 Mar 2020 23:48:07 GMT</pubDate></item></channel></rss>