Troubleshooting Connectivity Issues — start here

Work through these in order. The first two account for most reports, and cost nothing to check.

1. Is your service active and does it still have data?

2. Are you using the right node for where you are?

3. Is the correct service selected in the app?

4. Is your device clock accurate?

5. Connects, but no internet?

6. Still stuck? Find your client

If none of this resolves it, open a ticket and tell us: your platform, the client app, the node you selected, and what the client log says. That gets a real answer on the first reply instead of the third.

  • 0 gebruikers vonden dit artikel nuttig
Was dit antwoord nuttig?

Gerelateerde artikelen

On Windows, it prompts that the .NET Framework 4.6 module is missing, but during installation, it indicates that it's already present.

On Windows, it prompts that the .NET Framework 4.6 module is missing, but during installation, it...

Installation program did not run successfully

This error usually occurs because there are old versions of the client remaining in the system...

Unable to download the client

Download VilaNet (recommended) You do not need to open a ticket to get the client. VilaNet is our...

Can't Connect to Server Node? Connected but No Internet? Here's How to Fix It

We have implemented automatic failover for most server nodes. If a node still will not connect,...

Unable to Install APK on Android: "There Was a Problem Parsing the Package" Error

Issue: The error message "There was a problem parsing the package" typically occurs when your...