# Remote Instance using Putty

In this guide we will run virtual remote control of the Cloudeka portal service machine using PuTTY from your computer.

{% hint style="warning" %}
To run remote control of virtual machines using putty, make sure you have done the following configuration:\
a. [Create ](https://docs.cloudeka.id/deka_flexi/deka-flexi-network/6.1_vpc_network/create-vpc-network)[VPC](https://docs.cloudeka.id/deka_flexi/deka-flexi-network/6.1_vpc_network/create-vpc-network).\
b. [OpenVPN ](https://docs.cloudeka.id/deka_flexi/deka-vpn/openvpn-configuration)[Configuring](https://docs.cloudeka.id/deka_flexi/deka-vpn/openvpn-configuration)\
c. [IPsec Configuring](https://docs.cloudeka.id/deka_flexi/deka-vpn/ipsec-configuration)
{% endhint %}

The case examples used in this guide are two projects, each of which has a virtual machine on an Instance in the Cloudeka portal service. The following IP addresses are used in each project.

<table data-header-hidden><thead><tr><th width="275.3333333333333"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Column</strong></td><td><strong>Project A</strong></td><td><strong>Project B</strong></td></tr><tr><td>(a) VPN - Floating IP</td><td>103.191.14.149</td><td>103.168.135.220</td></tr><tr><td>(b) VPN - Network</td><td>10.10.10.0</td><td>10.20.20.0</td></tr><tr><td>(c)VPN - Network OpenVPN</td><td>20.20.20.0/24</td><td>-</td></tr><tr><td>(d) Instance - Gateway IP</td><td>10.10.10.1</td><td>10.20.20.1</td></tr><tr><td>(e) Instance - Internal IP</td><td>10.10.10.55</td><td>10.20.20.6</td></tr></tbody></table>

Here are the steps to run remote control of virtual machines in the Cloudeka portal service using PuTTY:

* Make an OpenVPN connection using Viscosity Inline from Project A.

* Enter the Username and Password used according to the OpenVPN User list in Project A.

* Run putty on your computer. Enter the IP address used by the virtual machine in Project A.

* Press the Accept button to enter the Project A virtual machine.

* Enter the username and password used by the virtual machine.

* You have successfully logged into the Project A virtual machine.

To be able to test the connection to Project B, you must conImage Security on Project A on the Cloudeka portal service, namely adding the IP address of the subnet used by Project B.

* On the Project A page in the Cloudeka Portal service, select the Security menu and press the Edit button to make configuration changes.

* On the Edit Security page, you will add two new rules to Inbound by pressing the New Rule button.

* The first type of rule is SSH, while the second type of rule is All ICMP Rule. In each Source column for both Types, enter the IP address of the subnet used by Project B, namely 10.20.20.0/24.

* Press the Save button to save changes.

* Do the same steps to conImage Security on Project B by adding the subnet IP address on Project A, namely 10.10.10.0/24.

* Enable IPsec on Project A, make sure the IP address used is the Project B subnet.

* Test the connection via Putty from the Project A virtual machine to the Project B virtual machine by inputting the following syntax: ping 10.20.20.6.

* The results of testing the network connection to the Project B virtual machine were completed in 3005 milliseconds (± 3 seconds).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.ai/guidance-for-individual/deka-flexi/deka-vpn/remote-instance-using-putty.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.
