<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic After Upgrade to 6, Security Server Not Changing listening Port in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954364#M23962</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ran into a weird situation where after upgrading a security server to 6.1.0-2509221, it doesn't change the SSL listening port when before the upgrade it wasn't on the standard SSL port.&lt;/P&gt;&lt;P&gt;It was originally configured to listen on 444 before the upgrade, following the upgrade I tried to change it back to 443 and a netstat -ban still shows it listening on port 444.&lt;/P&gt;&lt;P&gt;I double checked the the config.properties file, and there was no entry for serverPort, and the configuration shows 443 in the View admin manager. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Re-applying the configuration via the web page gives no change, still listens on 444.&lt;/P&gt;&lt;P&gt;- Restarting the security server service no change, still listens on 444.&lt;/P&gt;&lt;P&gt;- Rebooting the server no change, still listens on 444.&lt;/P&gt;&lt;P&gt;- Statically placed serverPort=443 in the config.properties, still listens on 444.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the ports are verified open, both 444 and 443, so I'm thinking I may have hit a bug. Anybody else have security servers that listen on non-standard SSL ports?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A complete reinstall of the security server is next, changing the listen port back to 443, shouldn't have to do that though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Apr 2015 14:39:50 GMT</pubDate>
    <dc:creator>elgwhoppo</dc:creator>
    <dc:date>2015-04-09T14:39:50Z</dc:date>
    <item>
      <title>After Upgrade to 6, Security Server Not Changing listening Port</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954364#M23962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ran into a weird situation where after upgrading a security server to 6.1.0-2509221, it doesn't change the SSL listening port when before the upgrade it wasn't on the standard SSL port.&lt;/P&gt;&lt;P&gt;It was originally configured to listen on 444 before the upgrade, following the upgrade I tried to change it back to 443 and a netstat -ban still shows it listening on port 444.&lt;/P&gt;&lt;P&gt;I double checked the the config.properties file, and there was no entry for serverPort, and the configuration shows 443 in the View admin manager. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Re-applying the configuration via the web page gives no change, still listens on 444.&lt;/P&gt;&lt;P&gt;- Restarting the security server service no change, still listens on 444.&lt;/P&gt;&lt;P&gt;- Rebooting the server no change, still listens on 444.&lt;/P&gt;&lt;P&gt;- Statically placed serverPort=443 in the config.properties, still listens on 444.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All the ports are verified open, both 444 and 443, so I'm thinking I may have hit a bug. Anybody else have security servers that listen on non-standard SSL ports?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A complete reinstall of the security server is next, changing the listen port back to 443, shouldn't have to do that though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 14:39:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954364#M23962</guid>
      <dc:creator>elgwhoppo</dc:creator>
      <dc:date>2015-04-09T14:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: After Upgrade to 6, Security Server Not Changing listening Port</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954365#M23963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You checked config.properties, but did you check in locked.properties for the port setting to see if it's been moved in there before/during the upgrade? Locked.properties will override any settings in config.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 17:13:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954365#M23963</guid>
      <dc:creator>mpryor</dc:creator>
      <dc:date>2015-04-09T17:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: After Upgrade to 6, Security Server Not Changing listening Port</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954366#M23964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hah, I was replying with that in a message when you responded. I forgot that I had hardened the server by requiring TLS 1.2 in the locked.properties file, and wouldn't you know that I also included serverPort=444 was in there. Big 'ole derple derp. Thanks!for posting.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 17:28:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/After-Upgrade-to-6-Security-Server-Not-Changing-listening-Port/m-p/954366#M23964</guid>
      <dc:creator>elgwhoppo</dc:creator>
      <dc:date>2015-04-09T17:28:02Z</dc:date>
    </item>
  </channel>
</rss>

