# Coti Full Node Guide
A quick guide on setting up a node on the coti testnet / mainnet.
{% hint style="warning" %}
Mainnet nodes are added by invite only or by running a node on the testnet and waiting for your invite providing you meet the criteria.
{% endhint %}
## Introduction
Welcome to a fast guide on getting up and running quickly on COTI. This guide is not aimed at beginners so you may need to google some things, especially if you are new to Ubuntu and various web technologies. \
\
That being said, we have had IT beginners successfully launch nodes with this guide so don't let it put you off!
### Requirements to take part
#### :no\_entry: You can't participate if you are from a country in the restricted list below
Setting up a COTI Pay VIPER wallet and therefore running a node is not allowed in the following countries: Afghanistan, Barbados, Bosnia & Herzegovina, Botswana, Burkina Faso, Burundi, Cambodia, Canada, Cayman Islands, Central African Republic, Côte d'Ivoire, Cuba, Democratic People's Republic of Korea (DPRK), Democratic Republic of the Congo, Eritrea, Ethiopia, Ghana, Gibraltar, Guinea, Guinea-Bissau, Haiti, Iran, Iraq, Israel, Jamaica, Jordan, Lebanon, Liberia, Libya, Mali, Morocco, Myanmar, Nicaragua, Pakistan, Panama, Senegal, Somalia, South Sudan, Sri Lanka, Syria, The Bahamas, Trinidad & Tobago, Tunisia, Uganda, United States of America (USA) and U.S territories, Venezuela, Yemen, and Zimbabwe
US territories - The U.S. has five permanently inhabited territories: Puerto Rico and the U.S. Virgin Islands in the Caribbean Sea, Guam and the Northern Mariana Islands in the North Pacific Ocean, and American Samoa in the South Pacific Ocean.
#### :white\_check\_mark: You must stake a minimum of 150,000 COTI in the COTI treasury
It will be needed once you are invited on to the mainnet. You will earn in two ways. You will get 30% APR on 150k coins = 3750 per month. On top of that lets say your 150k is in the treasury at 1X (no leverage no risk) at 11% APY currently, then you will also earn 1375 COTI on top for a total earn that month of 5125 COTI. Note: to take part in the testnet you do **not** need to stake ANY coti.
### Follow the guide in order
The guide will be written so you can flow through from Top to Bottom.
I will provide helpful hints along the way to assist where possible.
# Sign Up
{% hint style="info" %}
If you are an **exchange** you can skip this wallet and kyc section
{% endhint %}
To run a node on COTI Mainnet or Testnet, you’ll need a COTI Pay Wallet aka Viper, and then you can generate a seed and extract the private key.
To create a COTI wallet, you’ll need to register for a wallet if you don’t have one already. You can do this at via . You'll be able to see us registering one below in the screenshots.
{% hint style="danger" %}
**Do NOT** use the same phrase as your secret key that you use for your password
{% endhint %}
{% hint style="danger" %}
**NEVER** give **ANYONE** your seed or secret key, not even to coti staff else you risk **losing** your funds.
{% endhint %}
# KYC
### Now we wait for KYC response (3-5 business days)
Check your email. You should expect a confirmation within 3 - 5 business days. If you haven't been contacted after that feel free to drop an email to **** with the subject of KYC.
If you have setup two factor authentication you will get the screenshot below. I have provided a quick link to setting up two factor below which you can open in another browser window if you wish.
{% content-ref url="/pages/-MYuYz7F5hRpAkkw\_HLk" %}
[Two Factor Authentication](/extra-recommended-info/two-factor-authentication)
{% endcontent-ref %}
Continue to the next page to learn how to generate your seed now that you have logged in.
# Secret Key & SEED
This is a really important section.
After logging in to , click on the trustchain enter button.
{% hint style="warning" %}
Be sure to choose **testnet** from the drop down box on the following screens if you are setting up the node for the testnet. Remember: Mainnet is invite only.
{% endhint %}
### What is a good secret key?
Choosing a secret key is very important and although a minimum of 8 characters is allowed, i would advise to go with the maximum of 15 characters for better security. Below is a random example of a secret key I could have chosen which is suitable.
You may be thinking how will I remember that? The answer is either write it down and keep it safe, or you could use a password manager like [Bitwarden ](https://bitwarden.com/)or [Lastpass](https://lastpass.com/) which are much more effective and safer than storing anything in your browser.
{% hint style="danger" %}
Before copying any seeds or keys, be sure your computer is clean from viruses or malware. Some users may be more confident to turn off their internet once they have the seed on screen etc. The seed and secret key is your responsibility to keep safe!
**Do NOT** use the same phrase as your secret key that you use for your CPS password
**NEVER** give **ANYONE** your seed or secret key, not even to coti staff else you risk **losing** your funds to impersonators.
{% endhint %}
### Wallet and Private Key
Now go to and sign in to retrieve the private key we need for the node install. Also never give this to anyone also.
Copy the private key above.
# Registering a VPS
Hosting your node
You will need an Ubuntu VPS to host your node to allow you to be part of the testnet.
I personally recommend keeping it nice and cheap for the testnet but that does not mean going under specification!
Check out for the screen below so you can choose a VPS. The Best Choice below will meet the requirements of the testnet no problem whilst also not burning a hole in your pocket.
NOTE: VPS from Vultr for the same specification can be as much as $80 per month so it pays to shop around.
{% hint style="info" %}
For **MAINNET** see the tab below
{% endhint %}
{% tabs %}
{% tab title="Testnet Specification" %}
The requirements are: Ubuntu 18.04 or 20.04 LTS x64 VPS, 320 GB SSD, 6 CPU, 16 GB RAM, 5 TB bandwidth
{% endtab %}
{% tab title="Mainnet Specification" %}
### Top Specification
The top specification (expensive though) is: Ubuntu 18.04 or 20.04 LTS x64 VPS of the spec matching [c5.4xlarge](https://aws.amazon.com/ec2/instance-types/c5/) which is 16 vcpu, 32 GB RAM.
### Minimum Specification
Ubuntu 18.04 LTS x64, 12vcpu, 16GB Ram, 320GB SSD, 5 TB bandwidth, preferably not on shared infrastructure.
You could look at running a bare metal server with someone like [Leaseweb](https://www.leaseweb.com/dedicated-servers/high-performance-server) if you want some dedicated hardware at a reasonable price. Other providers are available like AWS, Vultr, Digital Ocean etc.
{% content-ref url="/pages/-MYvk7ahu446KMtXMqHW" %}
[Broken mention](broken://pages/-MYvk7ahu446KMtXMqHW)
{% endcontent-ref %}
{% endtab %}
{% endtabs %}
### Registering a VPS for Testnet
I'll take you through everything from buying the VPS to setting it up, lets go.
Now you can take a break while your VPS is provisioned. This can take a few hours but may be sooner. You will be emailed once the VPS is ready.
# VPS Setup
Great! i have received an email with all of the details on to say the VPS has been provisioned. I have blurred out my details but yours will have all of the necessary information!
Refer to the numbers on the screenshot below
1. This is your login information for
2. Note the IP address of your node, we will need that to configure your "A" record at namecheap or whoever you use for your domain name.
{% hint style="info" %}
2\. (extra info) The VNC details are useful for emergencies if you accidentally lock yourself out of the node. Just be aware they are there but you should never need them for this tutorial.
{% endhint %}
### Quick test of the login details and view how to reinstall the VPS
Lets try out the login details and make sure we can connect
{% hint style="info" %}
If you ever make a mistake, remember the Reinstall button right there on the menu above. It will factory reset the VPS to be wiped to the same state as when you purchased the VPS. This is great if something goes wrong with the setting up
{% endhint %}
### Lets go and register a domain name and configure an "A" record to point to our new VPS IP address.
# Registering a domain name
For this I will be using [namecheap.com](https://namecheap.com) which is a popular low cost domain name register and it's pretty easy to use.
{% hint style="info" %}
**TIP:** To view the screenshots at full size, simply click on the screenshot.
{% endhint %}
Search for a domain name that you wish to use and see if it is available. I went with an extension of ".online" as it seemed pretty cheap.
This page simply shows a purchase of the domain name.
Complete the payment then you have bought yourself a domain name!
Check your email as you will probably have to confirm your email address to finalise the registration.
# Add an "A" record
Now you have bought your domain name, the next step is to point it your VPS.
{% hint style="info" %}
An "A" record is simply how you point a domain name to an IP address. When you register a VPS it will be given an IP address that looks like four sets of numbers, separated by full stops.
{% endhint %}
After verifying my email address, I have logged in to my [namecheap.com](https://namecheap.com) account and gone to Domain List and clicked Advanced DNS where you will find the correct screen to add an "A" record.
I decided i wanted my node address to be "tutorialnode.cotinodes.online" so i wrote tutorial node in the host, and then i took the IP address from the VPS registration email (1) and added it in the Value field like shown on the screenshot below. You use YOUR VPS ip address of course. Select 5 min or even 1 min on the TTL which means how fast the DNS will update, then click the green tick.
Now wait however long you gave the TTL value above i.e. 5 minutes, make a drink, come back and continue!
# Register your node hash
For testnet node operator
{% hint style="info" %}
This is a **testnet** only section. Exchanges and mainnet nodes can ignore this section
{% endhint %}
Testnet users must register their public key aka node hash with coti to then make the transition on to the testnet. This can be done now (easier route) or later, providing you do a reboot once COTI confirm your node is registered.
#### Step 1: Login to the testnet
Login to the **testnet** at [pay.coti.io/testnet](https://pay.coti.io/testnet) and once in your wallet, click the cog at the top right corner and find your **public key.** Get ready to copy the public key see the screenshot below.
**Step 2: Send email to COTI**
Send an email to with email subject of Register Testnet Node.
You may copy and paste this text and insert the information
Dear Coti,
Please register my node on to the COTI Testnet.
My node is at URL: \
My node hash/public key is: \
Please email me to let me know when I can proceed.
Kind Regards,
\
Send the email then you can either wait for the response from COTI, or continue and finish the node install with a "Wrong node hash for network testnet" error.
{% hint style="info" %}
If you decide to continue with the guide without getting a reply from the email above, you will get a "Wrong node has for network Testnet" error once the node starts to run after you complete the Installing a node section. Thats ok though, as once COTI say you are registered you can issue the "reboot" command to the node and the node will reboot and should come online within a few minutes.
{% endhint %}
# Connect to the node
## What is putty?
Putty is a FREE and open source terminal program, it basically allows you to connect to your Ubuntu node! If you are familiar with Terminal or other programs feel free to use those.
### Installing Putty
To install putty go to [putty.org](https://putty.org)
As I'm installing on my windows machine ill select the 64bit x86 version like so....
Install the downloaded putty program, follow all the defaults for install then find Putty in your programs list and launch it.
1. Click Session
2. Add your hostname that you created earlier in [Add an "A" record](/purchases/add-an-a-record) for example tutorialnode.cotinodes.online or mynode.mydomain.com etc
3. Add the port, usually 22.
4. Give your session a name.
5. Click Save
Awesome, now you have a connection in putty that you can load anytime you wish to connect to your node. You are now ready to connect, and then install your node.
1. Click your saved session
2. Press Load
3. Press Open
1. Press Yes to allow connection. You should only see that the first time you connect from your device.
Type root or whichever username you were given on your VPS instructions and press enter
{% hint style="warning" %}
You will not be able to see the password that you either type OR paste.\
Go to your VPS email and copy the root password, then to paste your password, you should RIGHT CLICK on the black window and press enter. The right click pastes the password invisibly and enter will attempt to login.
{% endhint %}
If you are logged in you should see the welcome screen to your VPS!
# Installing a node
If you are **NOT** a crypto exchange click the link below to install a full node.
{% content-ref url="/pages/-MYlkOCMgU2eXQTAhCTi" %}
[Install a full node](/installing-the-node/installing-a-node/step-6-ready-to-run-code)
{% endcontent-ref %}
If you **ARE** a crypto exchange with an API key, click the link below
{% content-ref url="/pages/-MaKdACQTpBXRyG2x1hq" %}
[Installing an exchange full node](/installing-the-node/installing-a-node/installing-an-exchange-node)
{% endcontent-ref %}
# Install a full node
Node installation tips specifically for users (not exchanges)
## Login to your VPS.
Connect to your VPS as the root user with putty or any other popular terminal connection program.
Once connected with root, copy the code below and paste it into your putty / terminal window and press enter.
{% hint style="info" %}
You can find the github repo [here](https://github.com/Geordie-R/coti-full-node) if you want to dig in to the code further.
{% endhint %}
```
rm -rf installfullnode.sh
wget -O installfullnode.sh https://raw.githubusercontent.com/Geordie-R/coti-full-node/main/installfullnode.sh
chmod +x installfullnode.sh
./installfullnode.sh
```
\#You will be asked if you are installing for mainnet or testnet. Choose the number corresponding to the option
You will be asked a series of questions :
* Your SSH Port No (22 if you have not changed it)
* Your Ubuntu Username (use coti if not sure it will be created fresh)
* Your Email address
* Your server hostname from namecheap or other provider of your choice e.g. coti.mynode.com
* Your wallet private key (**not** your secret key)
* Your wallet seed key
* \***Testnet only - Node added 16/07/2022: -** (which version to launch type **3.1.0** for now)
* \***Mainnet only** (which version to launch e.g. 1.4.1 etc)
{% hint style="info" %}
If you are not sure of any of the answers that get asked above whilst running the code above, leave the answer empty and it will terminate after the questions so that you can run the installfullnode.sh script again on its own, as shown below.
```
./installfullnode.sh
```
{% endhint %}
Answer all of the questions, pressing enter after each answer, then the node will configure itself.
If you are not an exchange, please skip the next section and move on to the Finally checking you're up section.
# Installing an exchange full node
Node installation tips specifically for exchanges
I will detail what the difference is between installing a full node and installing an exchange full node.
The major difference installing for an exchange is you will be given an API key and also your mnemonic, seed and private key will be generated by YOU on your node, rather than given to you from the cps coti website.
You may follow the rest of the guide you see on the left menu from top to bottom, just ignore the WALLET AND KYC section as it does not apply to you.
### Connect to your node
Connect to your VPS as the **root** user with putty or any other popular terminal connection program of your choice.
Once connected with root, copy the code below and paste it into your putty / terminal window and press enter.
{% hint style="info" %}
You can find the github repo here: if you want to dig in to the code further.
{% endhint %}
```
rm -rf installfullnode.sh
wget -O installfullnode.sh https://raw.githubusercontent.com/Geordie-R/coti-full-node/main/installfullnode.sh
chmod +x installfullnode.sh
./installfullnode.sh
```
You will be asked if you are installing for mainnet or testnet. Choose the number corresponding to the option.
You will be asked a series of questions :
* Your SSH Port No (22 if you have not changed it)
* Your Ubuntu username (use coti if not sure it will be created fresh, do not use root)
* Your email address
* Your server hostname e.g. coti.mynode.com
* Your API Key
* Version to use: which version to launch e.g. 1.4.1 or type latest for the latest version if that is what you have been told to use.
{% hint style="info" %}
If you are not sure of any of the answers that get asked whilst running the code above, leave the answer empty and it will terminate after the questions so that you can run the installfullnode.sh script again on its own, as shown below.
```
./installfullnode.sh
```
{% endhint %}
Answer all of the questions, pressing enter after each answer, then the node will configure itself. Now lets head back to the main menu again and check that your node is up with the link below. Remember to head back here once you have finished that page
{% content-ref url="/pages/-MYm07-jNc3bjKmnm7Fl" %}
[Finally: Checking you're up!](/installing-the-node/finally-checking-youre-up)
{% endcontent-ref %}
### Recording your keys, then deleting the keys file.
During install, the script uses the newly generated keys storing them on disk in keys.json for a short time. This next section allows you to view your keys then delete them.
{% hint style="danger" %}
Make a safe backup of your keys, seeds and mnemonics stored inside the keys.json file. Run the code below to view your keys and then delete them from disk.
{% endhint %}
```
rm -rf getkeysthendelete.sh
wget -O getkeysthendelete.sh https://raw.githubusercontent.com/Geordie-R/coti-full-node/main/getkeysthendelete.sh
chmod +x getkeysthendelete.sh
./getkeysthendelete.sh
```
### Clearing your bash / terminal history
I recommend you clear your bash/terminal history once you have finished. Do this with the following command.
```
history -c
```
# Finally: Checking you're up!
If you successfully installed the node you will be on the lookout for this message
#### **COTI FULL NODE IS UP**
If you see the message above, use the tabs below to check for your node on mainnet or testnet.
{% tabs %}
{% tab title="Checking on Testnet" %}
Check you're up by logging into[ https://pay.coti.io/testnet ](< https://pay.coti.io/testnet >)and find your node in the drop down node list once you're past the username and password section.
{% endtab %}
{% tab title="Checking on Mainnet" %}
Check you're up by logging into and find your node in the drop down node list once you're past the username and password section.
{% endtab %}
{% endtabs %}
{% hint style="info" %}
If you are an **exchange only:** be sure to head back to the exchange page and run the keys section now to record your mnemonics, seed and private key then delete the keys file.
{% endhint %}
### What happens if I reboot
The node is currently running under a systemd service so if you reboot the service will automatically start. We would recommend you stop the service before rebooting of course. \
\
You can see the configuration for this service if you wish:
```
nano /etc/systemd/system/cnode.service
```
### Start/Stop
To stop or start the service use a variation of this command replacing start with stop
```
systemctl start cnode.service
```
### Viewing the log
If you want to view the log you can use the following command. If you have used a user other than coti, please replace the first mention of coti in the command below with your username. If you just want to see the end of the log replace nano with tail -f
```
nano /home/coti/coti-node/logs/FullNode1.log
```
## Uninstalling
If you make a mistake and want to uninstall and try the installation again, here is the code to uninstall.
```
rm -rf uninstallfullnode.sh
wget -O uninstallfullnode.sh https://raw.githubusercontent.com/Geordie-R/coti-full-node/main/uninstallfullnode.sh
chmod +x uninstallfullnode.sh
./uninstallfullnode.sh
```
# Uninstalling the node
If you make a mistake or want to uninstall and try the installation again, here is the code to uninstall.
```
rm -rf uninstallfullnode.sh
wget -O uninstallfullnode.sh https://raw.githubusercontent.com/Geordie-R/coti-full-node/main/uninstallfullnode.sh
chmod +x uninstallfullnode.sh
./uninstallfullnode.sh
```
# Upgrading your node
We have a new upgrade script you will be pleased to know!\
\
To upgrade your node, login as root and once logged in run the following code.
```
cd ~
rm -rf upgrade.sh
wget -O upgrade.sh https://raw.githubusercontent.com/Geordie-R/coti-node-upgrade/main/upgrade.sh && chmod +x upgrade.sh
./upgrade.sh
```
You will be asked a series of questions once you run the code above.
* You will be asked if you are upgrading a node on the testnet or mainnet. Type number 1 for the mainnet or 2 for the testnet then press enter.
* You will be asked for your ubuntu username the node is installed under. Leave it empty and press enter if you used "coti" originally.
* You will be asked what version of the node software you would like to install. Type the number if you know it in this format: 3.1.0 then press enter. If you leave it empty it will use the latest version. Please note if a brand new release has just been released i may not have had time to update the latest version in the script so just type it in manually if you are upgrading to a brand new release.
If all goes well you should see UPGRADE COMPLETE! in giant letters!
#### Credits
Thanks to Cryptofirebird for the collaboration with code and testing! Checkout his excellent website with lots of useful features here:
{% hint style="danger" %}
Once you have completed the above two steps, you can [go here to check ](/installing-the-node/finally-checking-youre-up)if you are up.
{% endhint %}
# Firewall / Ports
You may ignore this page, this is just for information purposes only for people wanting to configure their firewalls manually etc.
The ports that are needed are automatically configured for you in the UFW setup inside the installfullnode.sh script. However, if you need to know the ports that we open, see the incoming list below.
### Incoming
Your SSH port (22 if you left it to the default)
80
443
7070 (you may want to lock down to receive only traffic from nodemanager IP address for this port)
{% hint style="info" %}
The testnet node manager IP is 52.59.142.53 and the mainnet node manager IP is 35.157.47.86. You may lock down 7070 to these IP addresses depending on which network you are on.
{% endhint %}
# Two Factor Authentication
Login to cps.coti.io and click on the settings cog labelled 1 in the screenshot below, and then click Enable.
### Download Google Authenticator
Follow the numbers below
1. Download the app for your phone
2. Make a backup of the text 2FA key in case you lose your phone. You must never give this to anyone. Then feel free to scan the QR code.
3. Enter your login password for CPS once again for security reasons.
4. Open google authenticator on your phone and enter the 6 digit, 2 factor code.
# Node Hardening
Checkout the node hardening guide here:
# Troubleshooting your node
Sometimes unexpected things can go wrong. The log is the best place to go to find out.
### Check your logs
If you are wondering what is going on with your node then you should check your logs. To view your logs you can use a few different commands.
#### View log in real time
`tail -f /home/coti/coti-node/logs/FullNode1.log`
#### Get last 100 lines of your log
```
tail -n 100 /home/coti/coti-node/logs/FullNode1.log
```
#### Looking for specific phrases like ERROR as you use the tail command above
To further narrow down your tail command above you may want to hunt for a word like ERROR or COTI FULL NODE IS UP or some other phrase.
To do that just add a pipe and a grep and the word to search for like so:
```
tail -n 100 /home/coti/coti-node/logs/FullNode1.log | grep "ERROR"
```
{% hint style="info" %}
When you use grep, and are looking for a phrase, there may be errors which dont contain the word ERROR so it is not fool proof in that way. Its a good skill to have though knowing how to grep your tail. That sounds a bit wrong eh haha.
{% endhint %}
#### Analyse log with a text editor
`nano /home/coti/coti-node/logs/FullNode1.log`
#### Example of what a working node looks like
If you somehow do not have a log from the above commands then your node may not even have produced a log yet. Something likely went wrong. The most common issues when users install the node is that they mix up their private key (64 characters long) with their secret key (8-15 characters long). Or, sometimes people use their mainnet keys instead of their testnet keys. Do not do this.
If all else fails run the [uninstall](/uninstalling-the-node/uninstalling-the-node) and then [install](/installing-the-node/installing-a-node) again and closely monitor the install script until you see the node behaving like the screenshot above or before that you may see a phrase COTI FULL NODE IS UP.
### Need help?
Checkout the [discord for node operators here](https://discord.gg/QwVgfAa) if you need any assistance.
# Reseting Transactions
If you get a corrupt database, or the node status is UnSync on the coti node alert bot then run the following code in order.
### Step1 - Script download and Script run.
Copy and right click to paste the following code in your VPS .
```
cd ~
rm -rf reset_transactions.sh
wget -O reset_transactions.sh https://raw.githubusercontent.com/Geordie-R/coti-node-upgrade/main/reset_transactions.sh && chmod +x reset_transactions.sh
./reset_transactions.sh "true"
```
### Step 2 - Reboot the cnode.service
```
sudo systemctl restart cnode.service
```
### Step 3 - Set reset.transactions back to false
```
./reset_transactions.sh "false"
```
Now just wait 10 minutes and then check both the [Finally: Checking you're up!](/installing-the-node/finally-checking-youre-up) and also try sending some token through your node.
# Node Hash Retrieval
At the moment while COTI are fixing up some loose ends by putting the [Register your node hash](/purchases/full-node-operator) inside viper wallet instead, COTI support may ask you for your node hash.\
\
Now right this second I'm not 100% exactly what they want but checkout these two links:
Use your hostname in the URL for your node like this to receive a node hash in bytes format.\
You can also check here. Search for your node and send COTI your nodeHash
If you need any assistance locating your node hash ask in the [node operators group](https://discord.gg/QwVgfAa) in disccord.
# Export Logs
If you need to send your logs to COTI or to a community member who is helping you, this is the section for you.
{% hint style="info" %}
Please note that this section needs you to study the code which you copy and paste to edit it to your own values. For example you need to use YOUR node address and YOUR SSH port no etc
{% endhint %}
With a little bit of work you can be retrieving files from your Ubuntu node. I will cover how to do this with both Putty and Termius. I will cover Termius later in the week but if you cant wait just switch to the SFTP option in termius to allow the passing of files to and from your node.
## Exporting logs with Putty
Although this title says through putty, it is actually done through a program called pscp which is written by the makers of Putty. On putty.org website click through to download putty which will then take you through to the screen which contains pscp. See the screenshots below.
### Download PSCP
Download pscp to the **root** of your C:\ on your machine (not your node)
{% hint style="info" %}
The reason we say download pscp to the root of your drive is so that the windows path system can find the pscp file when calling it from command prompt in windows.
{% endhint %}
### For node hardened users
If you have hardened your node and you have previously generated a private key (ssh key) to connect to your node with then follow this section.
If you connect to your node with a node username and password that your VPS provider gave you then skip this section.
Please study and then run the following command on your windows command prompt. The command will pull back the logs to your machine if successful into the c:\ProgramData\CotiLogs folder. Be sure to edit the path after the -i part to be the path your private key. Also edit the port after the -P part to be your SSH port number. If you are not sure, this port is listed on the putty settings of your node. Also edit the bit which is "" to show your ubuntu user AND your node URL.
```
pscp -i C:\your_path_to_your_private_key.ppk -P 22 -sftp root@coti.mynode.com:/home/coti/coti-node/logs/* %HOMEDRIVE%\ProgramData\CotiLogs
```
The node will then ask you for your password to your SSH key. Once entered press enter and the copying of the files will begin. You will now find your files at c:\ProgramData\CotiLogs . You may have to go there manually in windows as ProgramData can be hidden by default. Go to Start > Run > and paste c:\ProgramData\CotiLogs into the open box.
### For non-hardened node users
For users that have not done any security enhancements for SSH keys follow this section.
Run the following command on your windows command prompt. The command will pull back the logs to your machine if successful into the c:\ProgramData\CotiLogs folder.
Remember to edit the port (after -P in the code below) to be your SSH port number. If you are not sure, this port is listed on the putty settings of your node. Also edit the bit which is "" to show your ubuntu user AND your node URL.
```
pscp -P 22 -sftp root@coti.mynode.com:/home/coti/coti-node/logs/* %HOMEDRIVE%\ProgramData\CotiLogs
```
Once ran you should see something like this in command prompt
Now just check to see if you see your logs at c:\ProgramData\CotiLogs
You can then send them to coti or your friend by adding the c:\ProgramData\CotiLogs folder to a zip file so you can email it.
{% hint style="info" %}
The easiest way in windows to make a zip file is to right click the CotiLogs folder and press Send to > Compressed zip file. You can then just email coti the one zip file.
{% endhint %}
If you somehow do not have a log from the above commands then your node may not even have produced a log yet. Something likely went wrong. The most common issues when users install the node is that they mix up their private key (64 characters long) with their secret key (8-15 characters long). Or, sometimes people use their mainnet keys instead of their testnet keys. Do not do this.
If all else fails run the [uninstall](/uninstalling-the-node/uninstalling-the-node) and then [install](/installing-the-node/installing-a-node) again and closely monitor the install script until you see the node behaving like the screenshot above or before that you may see a phrase COTI FULL NODE IS UP.
### Need help?
Checkout the [discord for node operators here](https://discord.gg/QwVgfAa) if you need any assistance.
# Reseting Transactions
If you get a corrupt database, or the node status is UnSync on the coti node alert bot then run the following code in order.
### Step1 - Script download and Script run.
Copy and right click to paste the following code in your VPS .
```
cd ~
rm -rf reset_transactions.sh
wget -O reset_transactions.sh https://raw.githubusercontent.com/Geordie-R/coti-node-upgrade/main/reset_transactions.sh && chmod +x reset_transactions.sh
./reset_transactions.sh "true"
```
### Step 2 - Reboot the cnode.service
```
sudo systemctl restart cnode.service
```
### Step 3 - Set reset.transactions back to false
```
./reset_transactions.sh "false"
```
Now just wait 10 minutes and then check both the [Finally: Checking you're up!](/installing-the-node/finally-checking-youre-up) and also try sending some token through your node.
# Node Hash Retrieval
At the moment while COTI are fixing up some loose ends by putting the [Register your node hash](/purchases/full-node-operator) inside viper wallet instead, COTI support may ask you for your node hash.\
\
Now right this second I'm not 100% exactly what they want but checkout these two links:
Use your hostname in the URL for your node like this to receive a node hash in bytes format.\
You can also check here. Search for your node and send COTI your nodeHash
### Download PSCP
Download pscp to the **root** of your C:\ on your machine (not your node)
{% hint style="info" %}
The reason we say download pscp to the root of your drive is so that the windows path system can find the pscp file when calling it from command prompt in windows.
{% endhint %}
### For node hardened users
If you have hardened your node and you have previously generated a private key (ssh key) to connect to your node with then follow this section.
If you connect to your node with a node username and password that your VPS provider gave you then skip this section.
Please study and then run the following command on your windows command prompt. The command will pull back the logs to your machine if successful into the c:\ProgramData\CotiLogs folder. Be sure to edit the path after the -i part to be the path your private key. Also edit the port after the -P part to be your SSH port number. If you are not sure, this port is listed on the putty settings of your node. Also edit the bit which is "