Network Configuration
Network configuration is an important component to ensure that TAKAKRYPT services can operate optimally, both in communication between internal modules and with external systems.
Prerequisites
Before deploying TAKAKRYPT, the following network configurations need to be prepared:
-
Static IP Address
It is recommended to use a static IP address to maintain connectivity consistency and avoid unexpected routing changes. -
Port Access
Ensure that all required ports have been allowed on the firewall. The list of required ports can be found in the next section. -
Domain or Hostname
Use a properly configured domain or hostname to facilitate system access and support the implementation of SSL/TLS certificates. -
Secure Connection (HTTPS)
Enable the HTTPS protocol with an SSL/TLS certificate to ensure that all data communication takes place in an encrypted manner. -
Internal Communication
Ensure that all system components, including backend services and agents, can be connected to each other via an internal network or VPN. -
Firewall & Security Group
Apply access restrictions by opening only the required ports and limiting access sources based on the principle of least privilege. -
DNS Resolution
Ensure that the DNS service is able to resolve hostnames between services, especially in container-based environments such as Docker or Kubernetes.
Required Ports
The following is a list of default ports that need to be opened on the firewall so that TAKAKRYPT services can run properly:
| Port | Protocol | Service | Description |
|---|---|---|---|
| 80 | TCP | HTTP | Redirect to HTTPS (443) |
| 443 | TCP | HTTPS | Secure access to the web dashboard |
| 25 / 465 / 587 | TCP | SMTP | Email notification port, adjusted to the mail server configuration |
| 4222 | TCP | NATS | Communication between services (client connections) |
| 6222 | TCP | NATS | Route connections between NATS cluster nodes |
| 8222 | TCP | NATS | HTTP monitoring endpoint for the NATS server |