From 25edd9c083edc31d5a77562413d0a68150034f9e Mon Sep 17 00:00:00 2001 From: Jordan Brown Date: Sun, 24 Sep 2017 11:44:56 -0400 Subject: [PATCH] Fixes readme indicating that 38607 is hardcoded --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cbe383f14c..ffdfa39f19 100644 --- a/README.md +++ b/README.md @@ -72,10 +72,11 @@ This process is identical to the above steps in command line mode. You can alway ## Setting up Remote access 1. Obtain an SSL certificate to secure the connection (this is beyond the scope of this guide) +1. Either stick with the default port `38607` or change it with `admin set-port ` 1. [Bind the SSL certificate to port 38607](https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-configure-a-port-with-an-ssl-certificate) - - e.g. `netsh http add sslcert ipport=0.0.0.0:38607 certhash= appid={F32EDA25-0855-411C-AF5E-F0D042917E2D}` + - e.g. `netsh http add sslcert ipport=0.0.0.0: certhash= appid={F32EDA25-0855-411C-AF5E-F0D042917E2D}` - The `appid` GUID actually doesn't matter, but for sanity, you should use the GUID of TGServerService.exe as printed above -1. Ensure port 38607 can be acccessed from the internet +1. Ensure the port can be acccessed from the internet 1. Log in from any computer using a username and password from the service computer in either the CLI or GUI ## Updating