Open Connection Sharing from the globe button in the Integrations page header, or from Connection Settings on the sign-in screen. First-run setup also offers both roles: an Outpost in the Connection step, and a Hub in the Sharing step.
Set Up a Hub
1
Pick the Hub computer
Choose a computer that has internet access, stays on, and is on the same subnet as the instrument
workstations. Atomscale must keep running on it for the Outposts to connect.
2
Switch to Hub mode
Select Hub and click Save. The Hub listens on port
8484 by default; you can choose any port from 1024 to 65535.
3
Approve the firewall prompt
The first time you turn on Hub mode, Windows asks an administrator to approve an inbound firewall
rule limited to the local subnet (see
Windows Firewall Rules). Approve it, or ask IT to
allow Atomscale through Windows Firewall.
4
Note the Hub address
The Hub lists the addresses other computers connect to, for example
10.1.10.50:8484, and the
Outposts connected to it.Set Up an Outpost
1
Enter the Hub address
On the instrument workstation, open Connection Sharing, select Outpost, and enter the Hub’s
address and port.
2
Test and save
Click Test connection. The test confirms the Hub is reachable
and that a secure connection to Atomscale works through it. Click
Save once it passes.
Changing It from the Web App
On the gateway’s page in the web app, Settings > Connection sharing > Configure switches the gateway between modes remotely. The gateway checks the new route first and refuses the change if, for example, the Hub is unreachable or the port is in use. After switching, it must reach Atomscale through the new route within 60 seconds, or it restores the previous settings and reports Rolled back. A remote switch to Hub mode never shows the Windows Firewall prompt, because nobody may be at the computer to approve it. If the rule was never approved, the Hub shows a firewall warning until someone at the computer turns Connection Sharing off and on again and approves the prompt.Security
The Hub limits what it relays:- It accepts connections only from the same IPv4 subnet, or from the Hub computer itself.
- It relays only encrypted HTTPS tunnels to port 443 on a fixed list of Atomscale hostnames (see Network Requirements). It can’t be used as a general web proxy.
- It refuses destinations that resolve to private or internal addresses.
- Traffic stays encrypted end to end between the Outpost and Atomscale. The Hub can’t read it.