Plugin,a Decentralized Oracle built on XDC Network
  • Migrating from Plugin Node V2 to V2.4 Without Changing the Node Address
    • 1 - Backup on Plugin Node V2.0
    • 2 - Installation and Configuration of Plugin Node V2.4
    • 3 - Importing PluginV2 Node Address into PluginV2.4
    • 4. Backup After Plugin V2.4 Upgrade
  • Plugin 2.0 - Node Operators
    • Introduction
    • Unstake PLI Tokens from Plugin 1.0 Node
    • Plugin 2.0 Set Up Requirements
    • Node Installation
      • Node Fulfillment
      • Job Setup
        • Steps to Setup Direct Request Job
      • Process of Approval
    • How to Update Your Plugin Node for the Latest XDC Gas Fee
  • PLUGIN 2.0 - Validators
    • Introduction
    • Set-up Requirements
    • Job Setup
      • Steps to Setup Direct Request Job
      • Flux Monitor Job
        • Idle Timer
        • Drum Beat
        • Poll Timer
        • POLL TIMER + IDLE TIMER (Recommended)
      • Process Of Approval
      • Rewards Information
    • OCR Set-up
    • How to Update Your Plugin Node for the Latest XDC Gas Fee
  • WALLET
    • XDCPay - Apothem
    • XDCPay - Mainnet
  • PLUGIN VRF SUBSCRIPTION
    • Introduction
    • Guidance on Utilizing Random Values
    • Creation and Deployment of VRF-Consumer Contract
    • Requesting Random Values
  • Multichain
    • PLISwap - How to instructions
  • Plugin Data Feeds platform
    • Introduction
    • End data consumers - Mainnet
    • End data consumers - Apothem
    • Benefits
  • Restaking Model
    • Introduction
      • Scenarios in Re-staking Model
      • Benefits To Node Members
      • Steps for Restaking
  • Tips and tricks
    • Known-Issues
    • Open-Issues
  • Plugin 1.0 Installations - Deprecated
    • How to install Plugin 1.0 Node
      • Modular Method Deployment (Recommended Approach)
      • Script Method (Legacy)
        • Script - Phase 1
        • Script - Phase 2
      • Docker Method
        • Docker - Phase 1
        • Docker - Phase 2
    • Core Adapters
    • Fund your Node
  • External Initiators - Deprecated
    • Introduction
    • Installation
    • Setup & Build
  • Oracle Plugin 1.0 - Deprecated
    • Deployment
    • Fulfillment Request
    • Job-Setup
    • Testing
  • Job-Tasks Plugin 1.0 Deprecated
    • Sleep
    • Get > Bytes32
    • HttpGet
    • CRON
    • Web
  • External Adapters Plugin 1.0 - Deprecated
    • Introduction
    • Implement External -Adapters
    • Define Bridge
    • Add Bridge to Job Spec
  • Deprecated
    • How to use
  • Use Cases
    • Plugin WFN Use Case
      • Plugin WFN Data Review
      • Plugin WFN Use Case - FAQ
      • Plugin WFN - Ambient Weather Unit Onboarding Instructions
      • Plugin WFN - Acurite Weather Unit Onboarding Instructions - LEGACY
      • Unlock WFN Node
    • Crypto Compare - Pricing Index
  • Node Operators
    • How to Register / Sign-up
    • How to enable 2FA
    • How to update profile
    • How to add XDC Wallet Address
    • How to Navigate Dashboards
    • How to submit Node Details
    • How to stake PLI token for Plugin Node
    • How to add Job to your node
    • View the node details
    • De-Activate / Re-activate my nodes
    • Withdraw staked PLI
    • Withdraw PLI from Plugin Node
    • Withdraw PLI from Oracle contract
    • How to add more stake in Node?
    • How to Migrate my Plugin Node to New Server?
    • How to Un-Stake the node.
    • How a Reputation is calculated?
    • Node Maintenance Instructions for node operators
  • FEATURES
    • PLI Yield Farming
      • Steps for Staking in Plugin Yield Farming (PLIYF)
      • PLIYF - FAQ
  • Support
    • FAQ
  • RESOURCES
    • Node Setup Video Tutorials
    • Community Supports
    • How to Submit your node details - Video Tutorial
  • CHANGELOG
    • v1.0.1
    • V1.0.2
    • V1.0.3
    • V1.0.4
    • V1.05
  • Terms and Conditions
Powered by GitBook
On this page
  1. Plugin 1.0 Installations - Deprecated
  2. How to install Plugin 1.0 Node
  3. Script Method (Legacy)

Script - Phase 2

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

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.

    #####################################################################################
			    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'.			     
###########################################################################################  
###########################################################################################

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

Save and submit!,

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.

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

PreviousScript - Phase 1NextDocker Method

Last updated 2 years ago

Once you reached this point successfully, next go to

Core Adapters