Two NoRM issues

Marcel Cox wrote:
> If the port 8009 is missing, then there was probably a certificate error
> at the moment httpstk was loaded. If you fix any potential certificate
> errors, the the next reboot should fix the problem. Provided the
> certificate problem is fixed, you can also manually bind httpstk to port
> 8009 in the current session by using the httpbind command. To see the
> exact syntax, issue the following command at the server console:
> help httpbind
>
>
I'm now on-site working with that server, and there definitely is some
sort of certificate issue; trying to get it resolved.

Thanks. On the first one, after fixing the HOSTS file, I could get into
it with Firefox which would prompt me for a certificate exception, so I
think the cert has to be re-done now that HOSTS is fixed. Once I accept
the exception, it "remembers" & lets me back in via https://...8009.

-- DE