# Troubleshooting issues

## 1. Node Installation Successful, But No Contract Calls:

If your node is installed but you do not see any contract calls on the <https://blockexplorer.bloxberg.org/> or <https://polygonscan.com/>:

* Check your configuration file to ensure the wallet address is correct:

$ cd \~/mvp-pox-node $ cat config

* Check and restart the etny service

$ sudo systemctl status etny-vagrant

## 2. Error: SGX Not Enabled or Properly Configured:

<figure><img src="/files/r3BORShZ51RIvotxWsxd" alt=""><figcaption></figcaption></figure>

If you encounter an SGX-related error:

* Make sure you have the latest BIOS update and your processor has the latest microcode update. More information can be found here: <https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/best-practices/microcode-update-guidance.html>
* In some cases, it is required to disable Hyper-threading, as a workaround to fix underlying hardware security issues. Intel periodically releases information on how to fix the microcode/firmware for their chipsets. Please check for the latest security updates and notes here: <https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/blob/main/releasenote.md>
* If you're operating a node within a virtual environment, ensure that you have an appropriate configuration for DCAP. Consult your Hardware Affiliate or intel to setup HAP properly.
* Mutual attestation for SGX requires low-latency network connectivity (less than 50ms) attestation which does not reset connections. A busy/congested network leads to irrecoverable errors during the attestation process.

## 3. Installer Error - UFW:

<figure><img src="/files/miLmSWHLlgWeOuMuz1go" alt=""><figcaption></figcaption></figure>

If you're receiving the error:

"Ftaller error: ufw allow out from any to SIP port 4001" command failed with exit code 1

It's possible there's a DNS issue:

1. Ensure your DNS server is able to resolve the domain names:

* "ipfs.ethernity.cloud"
* "core.bloxberg.org"
* "bloxberg.ethernity.cloud"

2. Test DNS resolution using ping:

$ ping ipfs.ethernity.cloud

Repeat the ping command for the other domains to verify they can be resolved.

## 4. Cleanup VM Not Working:

<figure><img src="/files/S7FR0lBYmjiCeh8ktCUy" alt=""><figcaption></figcaption></figure>

If you try to destroy the VM with the command:

**$ sudo vagrant destroy -f**

and it doesn't work, you might need to remove Vagrant completely and then reinstall it. To do this:

1. Remove Vagrant's data directory:

**$ sudo rm -rf \~/.vagrant.d**

2. Remove Vagrant from your system:

**$ sudo apt-get remove vagrant**

3. Run your installer script:

**$ sudo ./etny-node-installer.sh**

## 5. Collect the logs and share them as a text file on Discord.

$ cd \~/mvp-pox-node && sudo vagrant ssh -c "cat /var/log/etny-node.log && cat /home/vagrant/etny/node/config | grep -v KEY && cd /home/vagrant/etny/node/etny-repo && sudo git branch && sudo git log --pretty=format:%H -n 1 && sudo git log --pretty=format:%B -n 1"

{% embed url="<https://discord.com/channels/183867536931160064/790542509167738921>" %}


---

# 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.ethernity.cloud/ethernity-node/troubleshooting-issues.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.