Troubleshooting

Welcome to the troubleshooting chapter of our documentation. In this section, we aim to assist you in resolving various issues you might encounter. We understand that troubleshooting can be complex, as there are multiple scenarios that need to be considered.

To make this process easier, we have broken down each scenario into specific sections. Each section will guide you through the steps to identify and resolve the issue effectively. Whether you're facing connectivity problems, software errors, or hardware malfunctions, you'll find detailed instructions tailored to each situation.

Let's dive in and tackle these challenges together!

Identify the scenario that best matches your situation. If none of the scenarios apply, please reach out to our support team for further assistance.

General Troubleshooting

Open and Check for open Ports

You need to open Firewall Ports to let MasterNodes communicate with the Storage Node. Check the Firewall from your ISP and your local machine.

Opening Ports usually means:

• creating a Firewall Rule to allow ingress traffic and

• create port forwarding to map the WAN port to the LAN port.

Verify Ports are Open with https://www.yougetsignal.com/tools/open-ports/

Examples of to configure your device:

• Fritzbox (Germany)

• Swisscom (Switzerland)

• Sunrise (Switzerland)

please let us know on [e-mail] which provider/device you operate, and we will add this to the documentation.

Troubleshoot before your node was active

If you face an issue during the installation in the case that your node was not active, there are several ways to solve the issue. Not active in this context means that your node was not registered, and you never get any Data from the Master Node.

1. Docker wasn't installed previously, and you didn't assign a License

2. Docker wasn't installed previously, after installation you assigned a license

3. You run Docker already with other containers, and you didn't assign a License

4. You run Docker already with other containers, after installation you assigned a license

Troubleshoot after your node was active

If you encounter issues during the node's operational time after receiving data from the master node, exercise caution while troubleshooting. Modifying or deleting system configurations can result in your stake being slashed.

This section will follow soon. Create a ticket to get help on this stage.

---

Troubleshoot Steps for each scenario

1. Docker wasn't installed previously, and you didn't assign a License

In this scenario, neither data nor licenses are impacted. Therefore, it's perfectly acceptable to remove everything and start anew.

Make sure that:

• You meet the Minimum Requirements > especially the architecture

• Docker is installed properly with the installation steps provided for your OS

• You are using the latest Node Build. You can find the version information at the bottom left of your node's frontend interface.

For the following configuration, you can run our script to remove and reinstall Docker and the latest Node:

• Linux VPS Debian and Ubuntu

• You run the node with default setting (Data and Config path, as well as Ports are default)

• You don't have any other Container in your Docker (as mentioned in this chapter already)

Take care with this script. It removes Docker and all its container from your node an reinstall the latest Docker with and Node Version. Run this skript at your own risk.

• Remove Node and Docker

wget https://wesendit.io/setup/remove.sh
sudo chmod +x remove.sh
sudo ./remove.sh

• Reinstall Docker and Node with the latest version

// For Ubuntu x86 based systems
wget https://wesendit.io/setup/install_ubuntu.sh
sudo chmod +x install_ubuntu.sh
sudo ./install_ubuntu.sh

// For Debian x86 based systems
wget https://wesendit.io/setup/install_debian.sh
sudo chmod +x install_debian.sh
sudo ./install_debian.sh

2 Docker wasn't installed previously, after installation you assigned a license

In this case, you need to take care, that you do not touch any node configuration on your server. Your license can be lost!

• Disconnect your License from the Node on https://app.wesendit.io/en/nodes/

• Check the steps at 1. Docker wasn't installed previously, and you didn't assign a License

3 You run Docker already with other containers, and you didn't assign a License

In this case, you can most likely redeploy the docker Container. For this, use the following code:

// Navigate to the node where the compose file is located.
cd /var/lib/wesendit-node/
// Copose down, pull new Version and compose up
sudo docker compose down
sudo docker pull wesendit/node
sudo docker compose up -d

Check your frontend IP:PORT in your browser and log in with the previous credentials.

4 You run Docker already with other containers, after installation you assigned a license

In this case, you need to take care, that you do not touch any node configuration on your server. Your license can be lost! Moreover, take care of the other containers to not damage any other system.

• Disconnect your License from the Node on https://app.wesendit.io/en/nodes/

• Follow 3 You run Docker already with other containers, and you didn't assign a License