Q1:When executing the ‘devicego’ script, there is a failure to establish a new connection to the server.edgego host, resulting in the HTTPConnectionPool reaching the maximum retry count. How can this issue be resolved?

＊Error : Failed to establish a new connection

＊Error : Failed to execute script 'devicego' due to unhandled exception!

A1:

Please ping server-edgego.local and log the IP address of the EdgeGO server

1. Edit Hosts File

Windows:

Open Notepad as an administrator and open the hosts file:

　・In Notepad, go to File > Open.

　・Navigate to **C:\\Windows\\System32\\drivers\\etc**.

　・Change the file type filter to "All Files."

　・Open the file named "hosts."

Linux:

Open a terminal with administrative privileges and open the hosts file:

　・Execute the following command to ping the EdgeGO server:

　　　- ping server-edgego.local  

　　　　(Note down the IP address)

　・Use a command-line text editor

　　　- [nano] sudo nano /etc/hosts

　　　- [vim] sudo vim /etc/hosts

　・Add the host entry at the end of the file. 

　・Type the IP address followed by the hostname you want to map.

　　　- [IP of the EdgeGO server] server.edgego

　・Save the changes and exit the text editor.

　　　- [nano] press Ctrl + X > Y to confirm changes, and press Enter to exit

　　　- [vim] type : wq and press Enter to save and exit.

2. Add the host entry:

　・At the end of the file, add a new entry.

　・[IP of the EdgeGO server]server.edgego

　・Type the IP address followed by the hostname you want to map.

3. Save the hosts file:

　・Save the file and close Notepad.

You may need to save the file to your desktop first and then copy it back to the original location, overwriting the existing file.

Q1:May I confirm that there are distinctions in the setup process for the EdgeGO server between a WiFi connection and an Ethernet (cabled) connection?

【 Setup EdgeGO server 】

A1:

The type of network connection, whether through WiFi or Ethernet, should not be a critical factor. 

The key is to ensure that both the EdgeGO server and EdgeGO device are connected to a straightforward and uncomplicated network without extensive IT interventions. 

This might help rule out any network access restrictions. Additionally, it's worth noting that network access restrictions can vary based on IT configurations.

Q2:As far as I know, the server and the agent still need to be on the same network for the server to detect the agent. However, in our case, the server will be hosted remotely (anywhere), and the agent will be on-premise, so they will not be in the same network. Would EdgeGO still be able to work?

【 Onboarded 】

A2:

There are several hosting options available for the EdgeGO server, including the following:

Option 1: Public Cloud Hosting

You can opt to host the EdgeGO server on a public cloud platform such as AWS, Azure, GCP, or a self-hosted public server. To implement this, ensure that the /etc/hosts file on the EdgeGO device is configured to point to the EdgeGO server's public IP address. This allows bypassing auto-discovery and directly onboarding the device to the server in the public cloud. Keep in mind that this option necessitates the team to set up firewalls and ensure the server's security. Public Cloud Hosting appears to be a swift solution suitable for proof-of-concept.

Option 2: Tailscale (or Headscale, the open-source alternative) for Virtual Edge

As mentioned earlier, another viable option is to leverage services like Tailscale to create a virtual edge. This approach allows all devices to join a virtual network, even if physically distributed worldwide. While setting up Tailscale might be a bit more involved, it offers enhanced security measures.

Option 3: VPN (Virtual Private Network)

Implement a VPN for hosting the EdgeGO server. This involves creating a secure, encrypted connection between the EdgeGO device and the server. A VPN ensures data confidentiality and integrity, providing additional security for your EdgeGO deployment.

Q3:When deciding between Headscale and setting up our own VPN, the optimal choice depends on specific requirements and circumstances. Which option is more appropriate for our use?

A3:

It's worth noting that Tailscale and Headscale represent a newer generation of VPN technology known as mesh VPNs. This technology offers a more dynamic and flexible approach compared to conventional VPNs. 

Headscale, being an open-source alternative to Tailscale, offers similar functionality in creating a virtual network for distributed devices. It provides a secure and scalable solution, and since it's open source, you have more control over the implementation and can tailor it to your specific needs. However, it might require a bit more effort to set up and maintain compared to a commercial VPN solution.

On the other hand, using a 4traditional VPN provides a well-established and widely-used method for creating a secure, encrypted connection between the EdgeGO device and the server. It's a reliable option with a long track record of securing connections over the internet.

Ultimately, the decision between Headscale and a VPN depends on factors like the level of control you want, the specific security requirements of your EdgeGO deployment, and your team's familiarity with the technologies involved.

Q4:How to host the EdgeGO Server on Cloud Platforms ?

A4: For information on how to host a EdgeGO Server on Cloud Platform, please refer to the Cloud page.