# Script - Phase 2

After the successful execution of Phase 1, follow this Phase 2 to complete the script way installations

{% hint style="info" %}
Before proceeding to the next step, please **change the default contents of ‘.env.apicred’ & ‘.env.password’ to your own credentials** **and safely keep a note of this contents.** It is important to keep a note of this password somewhere. 
{% endhint %}

```
    #####################################################################################
			    IMPORTANT MESSAGE                                    
########################################################################################
# Make sure you have the below-mentioned 2 files available and populated as given below. 
# Then start 'pm2 start 2_nodeStartPM2.sh' script to run your  
# node in the background. To view your node log use 'pm2 logs 0'.
#                                                                          
# File 1: .env.password => contains your Keystore password
#  *** KEYSTORE PASSWORD SHOULD FOLLOW THIS CONDITIONS ***
#   “must be longer than 12 characters”,			    
#   “must contain at least 3 lowercase characters”,	     
#   “must contain at least 3 uppercase characters”,	     
#   “must contain at least 3 numbers”,			     
#   “must contain at least 3 symbols”,			     
#   “must not contain more than 3 identical consecutive characters”.						     
#     
# File 2: .env.apicred => first line of the file contains #email id for UI
#  second line of the file contains a password for UI
#  (This password should be strong, but need not follow the Keystore password condition).	     
#						
#
# NOTE: These files have default contents, please change the mail & passwords before 
starting 'pm2 2_nodeStartPM2.sh #start'.			     
###########################################################################################  
###########################################################################################

```

{% hint style="info" %}
**Edit the file 2\_nodeStartPM2.sh** file and change the **last line** 

**from** 

plugin node start -d -p password.txt -a apicredentials.txt

**to**

plugin node start -d -p .env.password -a .env.apicred
{% endhint %}

Save and submit!, 

{% hint style="info" %}
**Password must be kept safe & secure else, there is no way to retrieve it** and the funds managed by the private key will also get lost. 

Each time you start/restart your node, you will have to enter this password to unlock the Keystore. The node requires to sign the transaction through the private key of the Keystore and submit it to the blockchain.
{% endhint %}

After you change the credentials submit the following command

> **pm2 start 2\_nodeStartPM2.sh**

You should be able to view the logs on the console and also the list of existing jobs using the below command

> **plugin jobs list**

If you do not have any issues, you should be able to see the Plugin node using the below URL

> <http://localhost:6688/>

Replace the localhost with your public/remote IP if you are running this in VPS

*Once you reached this point successfully, next go to* [**Core Adapters**](https://docs.goplugin.co/plugin-installations/core-adapters)


---

# 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.goplugin.co/plugin-1.0-installations-deprecated/how-to-install-plugin-1.0-node/script-method-legacy/script-phase-2.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.