setting_up_msupply:client_server_faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
setting_up_msupply:client_server_faq [2023/07/31 23:30] – [Separate Dashboard Server Instance] Nick Pendergrastsetting_up_msupply:client_server_faq [2024/06/14 02:16] (current) – [Central Sync Server] Nick Pendergrast
Line 34: Line 34:
 | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) | | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) |
 | TSPlus Remote Web Kiosk | TCP 443 | HTTPS | Public | if running TSPlus for remote kiosk access to mSupply Client on the server | | TSPlus Remote Web Kiosk | TCP 443 | HTTPS | Public | if running TSPlus for remote kiosk access to mSupply Client on the server |
 +| SSL renewal | TCP 80 | HTTPS | Public | Required for automatic SSL renewal via ACME http challenge (no other web traffic will use this port) |
 +| mSupply ColdChain API | TCP 8090 | HTTPS | Public | For mSupply ColdChain API (if used) |
 | mSupply Application Server | TCP 19812, 19813, 19814 | | Local | mSupply Client connections to mSupply application server over LAN | | mSupply Application Server | TCP 19812, 19813, 19814 | | Local | mSupply Client connections to mSupply application server over LAN |
-| mSupply Client broadcast | UDP 49157 to 65535 | | Local | mSupply clients will automatically broadcast on the local network over this UDP port range to find the mSupply server |+| mSupply broadcast | UDP 49157 to 65535 | | Local | mSupply will automatically broadcast on the local network over this UDP port range to find the mSupply server |
  
-=== Central Server with no syncing remote sites ===+=== mSupply Server (Central or Remote) with no syncing remote sites ===
  
 All mSupply Client applications connect to the server over the LAN. There are no remote sites that need to sync to the central server. All mSupply Client applications connect to the server over the LAN. There are no remote sites that need to sync to the central server.
Line 56: Line 58:
  
 ^ Service ^ Allow Port ^ Protocol ^ Network ^ Requirement ^ ^ Service ^ Allow Port ^ Protocol ^ Network ^ Requirement ^
-| PostgreSQL | TCP 5432 | HTTP | Local | export of data from the mSupply db to the Postgres dashboard db  |+| PostgreSQL | TCP 5432 |  | Local | export of data from the mSupply db to the Postgres dashboard db  |
 | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) | | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) |
  
Line 75: Line 77:
 === 1) Client configuration file === === 1) Client configuration file ===
  
-After mSupply Client has been installed edit the EnginedServer.4Dlink found at this path **C:\mSupply client\Database** using notepad. Replace **<SERVER IP ADDRESS>** in the code below with the Server IP. This same file edited file can then be deployed to this folder of all the mSupply Client installations on this LAN.+After mSupply Client has been installed edit the EnginedServer.4Dlink found at this path **C:\mSupply client\Database** using notepad. Replace **<SERVER IP ADDRESS>** in the code below with the Server IP. This same edited file can then be deployed to the client database folder of all the mSupply Client installations on this LAN.
  
 <code> <code>
  • Last modified: 2023/07/31 23:30
  • by Nick Pendergrast