Change the default HTTPS port

When you create a self-signed certificate for using FactoryTalk Updater in a browser, the default HTTPS port number is 60129.
  1. To configure a Windows firewall rule for the self-defined port:
  2. On the FactoryTalk Updater server computer, in the Start menu, open
    Windows Firewall With Advanced Security
    .
  3. Right-click
    Inbound Rules
     and select
    New Rule
    .
  4. In the
    New Inbound Rule Wizard
     dialog bpx, select
    Port
    , and then select
    Next
    .
  5. In the
    Steps
     menu, select
    TCP Protocol and Ports
    .
  6. Select
    Specific local ports
     and enter a self-defined port number, such as
    50000
    . Select
    Next
    .
  7. In the
    Steps
     menu, select
    Name
    .
  8. In the
    Name
     box, enter a name for the new inbound rule, such as
    FTUpdater Web Client Site New Port
    , and select
    Finish
    .
  9. To change the port for the default website to the self-defined port in the IIS Manager application:
  10. On the FactoryTalk Updater server computer, open the Internet Information Services (IIS) Manager application.
  11. Select
    Server Certificates
    .
  12. In the
    Connections list
    , under
    Sites
    , right click the UpdaterWebServer certificate and select Edit Bindings.
  13. In the
    Site Bindings
     dialog box, select the https binding item and select
    Edit
    .
  14. In the
    Edit Site Binding
     dialog box, in the
    Port
     box, enter the self-defined port number and select
    OK
    . 
  15. In the
    Connections list
    , under
    Sites
    , right-click
    UpdaterWebServer certificate
    , and select
    Manage Website
    Restart
    .
    You can use the self-defined port number to open the FactoryTalk Updater application in a browser. For example:
    https://server-computer-name:50000
    For server-computer-name, you can insert the IP address or the computer name for your FactoryTalk Updater server.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.