# Configuration Inbound Rule

The Security Group at Deka Harbor has determined the port you can use. If you enter a port that is not specified, the message “The specified port is not allowed. Please check the port in the frontend configuration of the Load Balancer.” For a more detailed explanation of the ports that can be used, see Table below.

<table><thead><tr><th width="157">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>443</strong></td><td>This port can be used for secure communication via the HTTPS (Hypertext Transfer Protocol Secure) protocol.</td></tr><tr><td><strong>6443</strong></td><td>The port used by kubernetes to provide a secure server API management and authentication interface.</td></tr><tr><td><strong>80</strong></td><td>The port is used for unencrypted communication via the HTTP protocol but information sent via this port is not encrypted so it is not safe for use in environments that require data security.</td></tr><tr><td><strong>3100</strong></td><td>This port can be used for various services depending on the configuration.</td></tr></tbody></table>

The following is a guide to setting up the configuration for inbound rules on Deka Harbor:

* On the Cloudeka portal service page, select the Deka Harbor menu on the Platform.

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/20dekaharbor/20.40dash(a).png" alt=""><figcaption><p>Configuration Inbound Rule</p></figcaption></figure>

* Select the cluster to be added to configure the Load Balancer by clicking More in the Action column then clicking Details.

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/20dekaharbor/20.41dash(b).png" alt=""><figcaption><p>Configuration Inbound Rule</p></figcaption></figure>

* Select the Security Group tab then press the Edit button.

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/20dekaharbor/20.42%20config%20SG.png" alt=""><figcaption><p>Configuration Inbound Rule</p></figcaption></figure>

* Fill in the data to be changed.

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/20dekaharbor/20.43%20config%20SG.png" alt=""><figcaption><p>Configuration Inbound Rule</p></figcaption></figure>

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/20dekaharbor/20.44%20config%20SG.png" alt=""><figcaption><p>Configuration Inbound Rule</p></figcaption></figure>

<table><thead><tr><th width="178">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Protocol Type</strong></td><td>Supported protocols are:<br>- SSH,<br>- HTTP,<br>- HTTPS,<br>- Custom TCP Rules, you can customize TCP rules and specify specific ports according to your needs.<br>- Custom UDP Rules, you can customize udp rules and specify specific ports according to your needs.<br>- All ICMP Rules.</td></tr><tr><td><strong>Ether Type</strong></td><td>Type of IP used, select IPv4 and IPv6.</td></tr><tr><td><strong>Sources</strong></td><td>For inbound rules, which allow you to limit the source of inbound connections by entering individual IP addresses or entering a CIDR. for example, enter CIDR 182.23.45.0/24 into the rule to allow inbound traffic from IP addresses between 182.23.45.0 and 182.23.45.255. Or leave the field blank if you want to allow from any source.</td></tr></tbody></table>

* Press the Save button to save changes.

<figure><img src="https://putri.box.cloudeka.id/cloudeka-assets/static/images/20dekaharbor/20.45%20config%20SG.png" alt=""><figcaption><p>Configuration Inbound Rule</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudeka.id/platform/deka-harbor/configuration-inbound-rule.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.