> ## Documentation Index
> Fetch the complete documentation index at: https://cobo.com/developers/llms.txt
> Use this file to discover all available pages before exploring further.

# Network environments for deploying a server co-signer

> Learn about the network environments required for deploying a server co-signer.

<Tip>
  Try [Cobo WaaS Skill](/v2/guides/overview/cobo-waas-skill) in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster 🚀
</Tip>

A server co-signer requires the following network environments to run optimally:

* No inbound connections are required.
* During installation (or upgrade) phase:
  * Able to access the apt sources of the system to install all necessary dependencies (only applicable to Ubuntu servers)
  * Able to access the Docker Engine installation files to install the Docker Engine
  * Able to access docker.io registry (the public Docker registry)
  * Able to access the Intel website to download the driver (applicable to a SGX-ready server)
* Runtime network requirements: Your server must have outbound access to the following endpoints:

  | Environment | Port | Domain              |
  | ----------- | ---- | ------------------- |
  | Development | 443  | ws.tss.dev.cobo.com |
  | Production  | 443  | ws.tss.cobo.com     |

  If you have configured a TSS Node callback server, the server co-signer should also be able to access the callback server.