Peer Status Online but not Connected. #81

New Issue

Closed

opened 2025-11-20 05:05:57 -05:00 by saavagebueno · 36 comments

saavagebueno commented 2025-11-20 05:05:57 -05:00

Owner

Copy Link

Originally created by @MANKUD on GitHub (Nov 5, 2021).

Originally assigned to: @mlsmaycon on GitHub.

Hello,

I was trying to connect two windows machines and looks like they are shown online in the management dashboard but are not shown as connected is there something that I missed?

Since they are not shown as connected I am not able to get a ping response.

Originally created by @MANKUD on GitHub (Nov 5, 2021). Originally assigned to: @mlsmaycon on GitHub. Hello, I was trying to connect two windows machines and looks like they are shown online in the management dashboard but are not shown as connected is there something that I missed? Since they are not shown as connected I am not able to get a ping response.  

saavagebueno closed this issue 2025-11-20 05:05:57 -05:00

saavagebueno commented 2025-11-20 05:05:58 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 5, 2021):

Thank you for reporting the issue @MANKUD

We have changed the statuses displayed in the dashboard to avoid confusion.
We have 2 statuses now - [Offline, Online] that indicate whether peer is online and connected to the management service or not.
However, these statuses do not represent the connection status between peers (since the connections are peer-to-peer).

Would you mind sending us the recent output of the client log file? It is located under C:\ProgramData\Wiretrustee folder on Windows.

@braginini commented on GitHub (Nov 5, 2021): Thank you for reporting the issue @MANKUD We have changed the statuses displayed in the dashboard to avoid confusion. We have 2 statuses now - [Offline, Online] that indicate whether peer is online and connected to the management service or not. However, these statuses do not represent the connection status between peers (since the connections are peer-to-peer). Would you mind sending us the recent output of the client log file? It is located under C:\ProgramData\Wiretrustee folder on Windows.

saavagebueno commented 2025-11-20 05:05:58 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 5, 2021):

Here is the log file
client.log
.

@MANKUD commented on GitHub (Nov 5, 2021): Here is the log file [client.log](https://github.com/wiretrustee/wiretrustee/files/7488762/client.log) .

saavagebueno commented 2025-11-20 05:05:58 -05:00

Author

Owner

Copy Link

@stickman89 commented on GitHub (Nov 6, 2021):

This is relating to Windows Firewall... Add Inbound and Outbound rules for Wiretrustee's assigned IP Address range to 'Windows Defender Firewall with Advanced Security' to 'Allow the connection'; atleast untill this is fixed by the dev's here.

Tip: You need to do the above to all peers...

@stickman89 commented on GitHub (Nov 6, 2021): This is relating to Windows Firewall... Add Inbound and Outbound rules for Wiretrustee's assigned IP Address range to 'Windows Defender Firewall with Advanced Security' to 'Allow the connection'; atleast untill this is fixed by the dev's here. Tip: You need to do the above to all peers...  

saavagebueno commented 2025-11-20 05:05:58 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 6, 2021):

@stickman89 I tried disabling the firewall on both the peers and tried to ping and it did not help so I think its not issue with firewall.

@MANKUD commented on GitHub (Nov 6, 2021): @stickman89 I tried disabling the firewall on both the peers and tried to ping and it did not help so I think its not issue with firewall.

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@Soneji commented on GitHub (Nov 7, 2021):

I'm having the same issue, same client logs

root@ubuntu-2gb-nbg1-2:~# ssh 100.64.0.1
ssh: connect to host 100.64.0.1 port 22: No route to host

@Soneji commented on GitHub (Nov 7, 2021): I'm having the same issue, same client logs ``` root@ubuntu-2gb-nbg1-2:~# ssh 100.64.0.1 ssh: connect to host 100.64.0.1 port 22: No route to host ```

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@Chris3606 commented on GitHub (Nov 8, 2021):

Same issue, same client logs, trying to connect a Windows 10 to a Linux Mint box. My exact setup worked fine as of about a week and a half ago. I completely disabled firewalls on both boxes for the sake of testing, no effect.

@Chris3606 commented on GitHub (Nov 8, 2021): Same issue, same client logs, trying to connect a Windows 10 to a Linux Mint box. My exact setup worked fine as of about a week and a half ago. I completely disabled firewalls on both boxes for the sake of testing, no effect.

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 8, 2021):

Hello @MANKUD @Soneji sorry to hear that you facing these issues. In order to troubleshoot the issue, can you confirm the versions of the clients and could you run the following commands to enable a more verbose log:

wiretrustee service stop
wiretrustee service uninstall
wiretrustee service install --log-level debug
wiretrustee service start

In Windows you may need to run the powershell as admin and on Linux you need sudo

After that it will be great if you can share the log files from at least 2 peers that can't communicate.

@mlsmaycon commented on GitHub (Nov 8, 2021): Hello @MANKUD @Soneji sorry to hear that you facing these issues. In order to troubleshoot the issue, can you confirm the versions of the clients and could you run the following commands to enable a more verbose log: ```shell wiretrustee service stop wiretrustee service uninstall wiretrustee service install --log-level debug wiretrustee service start ``` > In Windows you may need to run the powershell as admin and on Linux you need sudo After that it will be great if you can share the log files from at least 2 peers that can't communicate.

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 9, 2021):

Hello @MANKUD @Soneji sorry to hear that you facing these issues. In order to troubleshoot the issue, can you confirm the versions of the clients and could you run the following commands to enable a more verbose log:

wiretrustee service stop
wiretrustee service uninstall
wiretrustee service install --log-level debug
wiretrustee service start

In Windows you may need to run the powershell as admin and on Linux you need sudo

After that it will be great if you can share the log files from at least 2 peers that can't communicate.

Here are the log file after enabling a more verbose log.

client 2.log

client 1.log

@MANKUD commented on GitHub (Nov 9, 2021): > Hello @MANKUD @Soneji sorry to hear that you facing these issues. In order to troubleshoot the issue, can you confirm the versions of the clients and could you run the following commands to enable a more verbose log: > > ```shell > wiretrustee service stop > wiretrustee service uninstall > wiretrustee service install --log-level debug > wiretrustee service start > ``` > > > In Windows you may need to run the powershell as admin and on Linux you need sudo > > After that it will be great if you can share the log files from at least 2 peers that can't communicate. Here are the log file after enabling a more verbose log. [client 2.log](https://github.com/wiretrustee/wiretrustee/files/7504414/client.2.log) [client 1.log](https://github.com/wiretrustee/wiretrustee/files/7504413/client.1.log)

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 10, 2021):

@MANKUD sorry for the delay in replying.

Checking client1.log it seems like debug wasn't enabled there. Can you run the commands above for this client too?

@mlsmaycon commented on GitHub (Nov 10, 2021): @MANKUD sorry for the delay in replying. Checking client1.log it seems like debug wasn't enabled there. Can you run the commands above for this client too?

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 11, 2021):

@MANKUD we found and fixed an issue with one of our TURN servers, can you test again?

@mlsmaycon commented on GitHub (Nov 11, 2021): @MANKUD we found and fixed an issue with one of our TURN servers, can you test again?

saavagebueno commented 2025-11-20 05:05:59 -05:00

Author

Owner

Copy Link

@Chris3606 commented on GitHub (Nov 11, 2021):

@mlsmaycon Although I'm not the OP, I did have the same issue w/ same type of behavior in the logs, and now it's fixed when I tried just now, for what that's worth; hoping the OP can verify as well.

@Chris3606 commented on GitHub (Nov 11, 2021): @mlsmaycon Although I'm not the OP, I did have the same issue w/ same type of behavior in the logs, and now it's fixed when I tried just now, for what that's worth; hoping the OP can verify as well.

saavagebueno commented 2025-11-20 05:06:00 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 12, 2021):

Thank you for the feedback @Chris3606, glad it is working again for you.

@mlsmaycon commented on GitHub (Nov 12, 2021): Thank you for the feedback @Chris3606, glad it is working again for you.

saavagebueno commented 2025-11-20 05:06:00 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@mlsmaycon I am getting his error on one of the systems that I am trying to add as peer.

@MANKUD commented on GitHub (Nov 12, 2021): @mlsmaycon I am getting his error on one of the systems that I am trying to add as peer. 

saavagebueno commented 2025-11-20 05:06:00 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@mlsmaycon

I am able to ping now seems like the issue is fixed also let me know how to solve the above-mentioned error.

@MANKUD commented on GitHub (Nov 12, 2021): @mlsmaycon I am able to ping now seems like the issue is fixed also let me know how to solve the above-mentioned error.

saavagebueno commented 2025-11-20 05:06:00 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@mlsmaycon
Also, there was an issue on windows on version wiretrustee_installer_0.2.2-beta.1_windows_amd64 the wiretrustee service just stops after a while and does not run and need to be manually started. I am not sure if that issue is fixed on the latest release.

@MANKUD commented on GitHub (Nov 12, 2021): @mlsmaycon Also, there was an issue on windows on version wiretrustee_installer_0.2.2-beta.1_windows_amd64 the wiretrustee service just stops after a while and does not run and need to be manually started. I am not sure if that issue is fixed on the latest release.

saavagebueno commented 2025-11-20 05:06:00 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 12, 2021):

@mlsmaycon Also, there was an issue on windows on version wiretrustee_installer_0.2.2-beta.1_windows_amd64 the wiretrustee service just stops after a while and does not run and need to be manually started. I am not sure if that issue is fixed on the latest release.

Thank you @MANKUD for mentioning this. Indeed there was an issue, specifically when there were reconnects to the Signal service. It was fixed and the latest version doesn't have this problem anymore:
https://github.com/wiretrustee/wiretrustee/releases/tag/v0.2.3

@braginini commented on GitHub (Nov 12, 2021): > @mlsmaycon Also, there was an issue on windows on version wiretrustee_installer_0.2.2-beta.1_windows_amd64 the wiretrustee service just stops after a while and does not run and need to be manually started. I am not sure if that issue is fixed on the latest release. Thank you @MANKUD for mentioning this. Indeed there was an issue, specifically when there were reconnects to the Signal service. It was fixed and the latest version doesn't have this problem anymore: https://github.com/wiretrustee/wiretrustee/releases/tag/v0.2.3

saavagebueno commented 2025-11-20 05:06:00 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 12, 2021):

@mlsmaycon I am getting his error on one of the systems that I am trying to add as peer.

Would you mind updating to the latest version?
We have also increased timeouts while the client tries to connect to the signal and management services.

We might also introduce some simple retry logic there (e.g. up to 3 times). What do you think @MANKUD ?

@braginini commented on GitHub (Nov 12, 2021): > @mlsmaycon I am getting his error on one of the systems that I am trying to add as peer. > >  Would you mind updating to the latest version? We have also increased timeouts while the client tries to connect to the signal and management services. We might also introduce some simple retry logic there (e.g. up to 3 times). What do you think @MANKUD ?

saavagebueno commented 2025-11-20 05:06:01 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@braginini

it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.

Simple retry logic sounds promising.

@MANKUD commented on GitHub (Nov 12, 2021): @braginini it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.  Simple retry logic sounds promising.

saavagebueno commented 2025-11-20 05:06:01 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@braginini
Are you planning to add an option to create multiple networks where we can have multiple IP ranges for different networks or even the same IP range on the multiple networks and not just the default 100.64.0.x?

@MANKUD commented on GitHub (Nov 12, 2021): @braginini Are you planning to add an option to create multiple networks where we can have multiple IP ranges for different networks or even the same IP range on the multiple networks and not just the default 100.64.0.x?

saavagebueno commented 2025-11-20 05:06:01 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 12, 2021):

@braginini Are you planning to add an option to create multiple networks where we can have multiple IP ranges for different networks or even the same IP range on the multiple networks and not just the default 100.64.0.x?

@MANKUD
We wanted to address the network split by introducing ACLs.
Simply put, you'd be able to create groups of peers and they would be able to connect to each other only, not interfering with other groups.

@braginini commented on GitHub (Nov 12, 2021): > @braginini Are you planning to add an option to create multiple networks where we can have multiple IP ranges for different networks or even the same IP range on the multiple networks and not just the default 100.64.0.x? @MANKUD We wanted to address the network split by introducing ACLs. Simply put, you'd be able to create groups of peers and they would be able to connect to each other only, not interfering with other groups.

saavagebueno commented 2025-11-20 05:06:01 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 12, 2021):

@braginini

it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.

Simple retry logic sounds promising.

That is strange
may I ask you to show a client.log?

@braginini commented on GitHub (Nov 12, 2021): > @braginini > > it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error. > >  > > Simple retry logic sounds promising. That is strange may I ask you to show a client.log?

saavagebueno commented 2025-11-20 05:06:01 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@braginini Are you planning to add an option to create multiple networks where we can have multiple IP ranges for different networks or even the same IP range on the multiple networks and not just the default 100.64.0.x?

@MANKUD We wanted to address the network split by introducing ACLs. Simply put, you'd be able to create groups of peers and they would be able to connect to each other only, not interfering with other groups.

@braginini
Would I be able to use the same IP range in the different group of peers for example use the same default 100.64.0.x for multiple groups and also would there be an option to choose the desired IP range something like 10.0.0.1 or 10.1.1.1 etc instead of 100.64.0.x?

@MANKUD commented on GitHub (Nov 12, 2021): > > @braginini Are you planning to add an option to create multiple networks where we can have multiple IP ranges for different networks or even the same IP range on the multiple networks and not just the default 100.64.0.x? > > @MANKUD We wanted to address the network split by introducing ACLs. Simply put, you'd be able to create groups of peers and they would be able to connect to each other only, not interfering with other groups. @braginini Would I be able to use the same IP range in the different group of peers for example use the same default 100.64.0.x for multiple groups and also would there be an option to choose the desired IP range something like 10.0.0.1 or 10.1.1.1 etc instead of 100.64.0.x?

saavagebueno commented 2025-11-20 05:06:02 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@braginini
it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.

Simple retry logic sounds promising.

That is strange may I ask you to show a client.log?

@braginini

here is the log file attached.
client.log

@MANKUD commented on GitHub (Nov 12, 2021): > > @braginini > > it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error. > >  > > Simple retry logic sounds promising. > > That is strange may I ask you to show a client.log? @braginini here is the log file attached. [client.log](https://github.com/wiretrustee/wiretrustee/files/7527843/client.log)

saavagebueno commented 2025-11-20 05:06:02 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 12, 2021):

@braginini
it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.

Simple retry logic sounds promising.

That is strange may I ask you to show a client.log?

@braginini

here is the log file attached. client.log

@MANKUD could u plz ping api.wiretrustee.com ?
also what is the output of telnet api.wiretrustee.com 33073 ?

@braginini commented on GitHub (Nov 12, 2021): > > > @braginini > > > it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error. > > >  > > > Simple retry logic sounds promising. > > > > > > That is strange may I ask you to show a client.log? > > @braginini > > here is the log file attached. [client.log](https://github.com/wiretrustee/wiretrustee/files/7527843/client.log) @MANKUD could u plz ping api.wiretrustee.com ? also what is the output of `telnet api.wiretrustee.com 33073` ?

saavagebueno commented 2025-11-20 05:06:02 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@braginini
it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.

Simple retry logic sounds promising.

That is strange may I ask you to show a client.log?

@braginini
here is the log file attached. client.log

@MANKUD could u plz ping api.wiretrustee.com ? also what is the output of telnet api.wiretrustee.com 33073 ?

@braginini

@MANKUD commented on GitHub (Nov 12, 2021): > > > > @braginini > > > > it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error. > > > >  > > > > Simple retry logic sounds promising. > > > > > > > > > That is strange may I ask you to show a client.log? > > > > > > @braginini > > here is the log file attached. [client.log](https://github.com/wiretrustee/wiretrustee/files/7527843/client.log) > > @MANKUD could u plz ping api.wiretrustee.com ? also what is the output of `telnet api.wiretrustee.com 33073` ? @braginini  

saavagebueno commented 2025-11-20 05:06:02 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 12, 2021):

@braginini
it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error.

Simple retry logic sounds promising.

That is strange may I ask you to show a client.log?

@braginini
here is the log file attached. client.log

@MANKUD could u plz ping api.wiretrustee.com ? also what is the output of telnet api.wiretrustee.com 33073 ?

@braginini

This is suprasingly strange.

Could you please try running telnet signal2.wiretrustee.com 10000 to check whether the problem persists also for the Signal service?

P.S. I'm able to successfully establish connection with telnet

@braginini commented on GitHub (Nov 12, 2021): > > > > > @braginini > > > > > it's already updated to the latest release. I tried multiple times to add the peer but I am getting the same error not sure why getting such an error. > > > > >  > > > > > Simple retry logic sounds promising. > > > > > > > > > > > > That is strange may I ask you to show a client.log? > > > > > > > > > @braginini > > > here is the log file attached. [client.log](https://github.com/wiretrustee/wiretrustee/files/7527843/client.log) > > > > > > @MANKUD could u plz ping api.wiretrustee.com ? also what is the output of `telnet api.wiretrustee.com 33073` ? > > @braginini > >  > >  This is suprasingly strange. Could you please try running `telnet signal2.wiretrustee.com 10000` to check whether the problem persists also for the Signal service? P.S. I'm able to successfully establish connection with telnet

saavagebueno commented 2025-11-20 05:06:02 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 12, 2021):

@braginini

Unfortunately, the connection failed to that too.

@MANKUD commented on GitHub (Nov 12, 2021): @braginini Unfortunately, the connection failed to that too. 

saavagebueno commented 2025-11-20 05:06:03 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 13, 2021):

@MANKUD It seems like you have either a local network restriction to the services ports. Looking by the logs, it seems that either you moved the client to a new network as it was able to connect to our management system before or something changed in the client itself.

Can you give us more details regarding its network? if possible, test from another computer in the network as well.

@mlsmaycon commented on GitHub (Nov 13, 2021): @MANKUD It seems like you have either a local network restriction to the services ports. Looking by the logs, it seems that either you moved the client to a new network as it was able to connect to our management system before or something changed in the client itself. Can you give us more details regarding its network? if possible, test from another computer in the network as well.

saavagebueno commented 2025-11-20 05:06:03 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 13, 2021):

@mlsmaycon

Hello the client was not moved to a different network it's in the same network and yes I was able to join the management system before but I had removed the app and now when I am trying again I am not able to join at all and it's giving the error I mentioned above. The network does not have any restrictions as such it's connected to a router with dynamic IP and there is no special firewall as such installed.

@MANKUD commented on GitHub (Nov 13, 2021): @mlsmaycon Hello the client was not moved to a different network it's in the same network and yes I was able to join the management system before but I had removed the app and now when I am trying again I am not able to join at all and it's giving the error I mentioned above. The network does not have any restrictions as such it's connected to a router with dynamic IP and there is no special firewall as such installed.

saavagebueno commented 2025-11-20 05:06:03 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 13, 2021):

@MANKUD did you check from another client in the same network?

You mentioned that there is no special firewall installed, but did you check with it temporarily disabled and perhaps antivirus too?

@mlsmaycon commented on GitHub (Nov 13, 2021): @MANKUD did you check from another client in the same network? You mentioned that there is no special firewall installed, but did you check with it temporarily disabled and perhaps antivirus too?

saavagebueno commented 2025-11-20 05:06:03 -05:00

Author

Owner

Copy Link

@braginini commented on GitHub (Nov 13, 2021):

additionally to what @mlsmaycon asked, @MANKUD could you please run these commands?

telnet apitest.wiretrustee.com 33073
telnet apitest.wiretrustee.com 33071

telnet apitest.wiretrustee.com 80
telnet apitest.wiretrustee.com 443

What is the output?

@braginini commented on GitHub (Nov 13, 2021): additionally to what @mlsmaycon asked, @MANKUD could you please run these commands? `telnet apitest.wiretrustee.com 33073` `telnet apitest.wiretrustee.com 33071` `telnet apitest.wiretrustee.com 80` `telnet apitest.wiretrustee.com 443` What is the output?

saavagebueno commented 2025-11-20 05:06:03 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 13, 2021):

@mlsmaycon

Hi unfortunately I do not have access to any other system in the same network. I also tried disabling the firewall and system antivirus but it did not help.

@braginini

let me try these and get back to you with an update.

@MANKUD commented on GitHub (Nov 13, 2021): @mlsmaycon Hi unfortunately I do not have access to any other system in the same network. I also tried disabling the firewall and system antivirus but it did not help. @braginini let me try these and get back to you with an update.

saavagebueno commented 2025-11-20 05:06:03 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 13, 2021):

additionally to what @mlsmaycon asked, @MANKUD could you please run these commands?

telnet apitest.wiretrustee.com 33073 telnet apitest.wiretrustee.com 33071

telnet apitest.wiretrustee.com 80 telnet apitest.wiretrustee.com 443

What is the output?

telnet apitest.wiretrustee.com 33073

telnet apitest.wiretrustee.com 33071

telnet apitest.wiretrustee.com 80

telnet apitest.wiretrustee.com 443

@MANKUD commented on GitHub (Nov 13, 2021): > additionally to what @mlsmaycon asked, @MANKUD could you please run these commands? > > `telnet apitest.wiretrustee.com 33073` `telnet apitest.wiretrustee.com 33071` > > `telnet apitest.wiretrustee.com 80` `telnet apitest.wiretrustee.com 443` > > What is the output? telnet apitest.wiretrustee.com 33073  telnet apitest.wiretrustee.com 33071  telnet apitest.wiretrustee.com 80  telnet apitest.wiretrustee.com 443 

saavagebueno commented 2025-11-20 05:06:04 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 13, 2021):

@braginini @mlsmaycon

I see that wiretrustee works without wireguard installed on the windows machine how does it work without wireguard running on the machine it's built over wireguard right?

I also could not find any wireguard tunnel created on windows not sure how it's working.

@MANKUD commented on GitHub (Nov 13, 2021): @braginini @mlsmaycon I see that wiretrustee works without wireguard installed on the windows machine how does it work without wireguard running on the machine it's built over wireguard right? I also could not find any wireguard tunnel created on windows not sure how it's working.

saavagebueno commented 2025-11-20 05:06:04 -05:00

Author

Owner

Copy Link

@mlsmaycon commented on GitHub (Nov 14, 2021):

@braginini @mlsmaycon

I see that wiretrustee works without wireguard installed on the windows machine how does it work without wireguard running on the machine it's built over wireguard right?

I also could not find any wireguard tunnel created on windows not sure how it's working.

Yes, we are using wireguard-go package which is an official package from Wireguard. The interface is created after we connect to Management and Signal services, that is why you are unable to see such an interface.

@mlsmaycon commented on GitHub (Nov 14, 2021): > @braginini @mlsmaycon > > I see that wiretrustee works without wireguard installed on the windows machine how does it work without wireguard running on the machine it's built over wireguard right? > > I also could not find any wireguard tunnel created on windows not sure how it's working. Yes, we are using wireguard-go package which is an official package from Wireguard. The interface is created after we connect to Management and Signal services, that is why you are unable to see such an interface.

saavagebueno commented 2025-11-20 05:06:04 -05:00

Author

Owner

Copy Link

@MANKUD commented on GitHub (Nov 15, 2021):

@mlsmaycon thank you for the info I think this can me marked as resolved now.

@MANKUD commented on GitHub (Nov 15, 2021): @mlsmaycon thank you for the info I think this can me marked as resolved now.

saavagebueno referenced this issue 2025-11-20 07:11:25 -05:00

[PR #81] [MERGED] peer management HTTP API #2526

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

fix/byop-selfhost

feat/status-short-flags

fix/rosenpass

ui-refactor-ui

ui-refactor

proxy-ipv6-bracket-and-debug-bundle

e2e-windows-dns-combined

mgmt-proxy-peer-ipv6

refactor-combined

wasm-websocket-dial

drop-dns-probes

feature/affected-peers

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

debug-logs

reduce-embed-wg-pool

windows-dns-firewall

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

dependabot/npm_and_yarn/proxy/web/postcss-8.5.12

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

wasm-js-func-release

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

vnc-server

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

dependabot/go_modules/golang.org/x/image-0.38.0

feature/metrics-push-management-control

release/0.68.3

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream-1.7.8

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.97.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

dependabot/go_modules/github.com/go-jose/go-jose/v4-4.1.4

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

dependabot/go_modules/github.com/pion/dtls/v3-3.0.11

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

dependabot/go_modules/github.com/quic-go/quic-go-0.57.0

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

feature/changeset

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

dependabot/go_modules/github.com/docker/docker-28.0.0incompatible

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

v0.70.5

v0.70.4

v0.70.3

v0.70.2

v0.70.1

v0.70.0

v0.69.0

v0.68.3

v0.68.2

v0.68.1

v0.68.0

v0.67.4

v0.67.3

v0.67.2

v0.67.1

v0.67.0

v0.66.4

v0.66.3

v0.66.2

v0.66.1

v0.66.0

v0.65.3

v0.65.2

v0.65.1

v0.65.0

v0.64.6

v0.64.5

v0.64.4

v0.64.3

v0.64.2

v0.64.1

v0.64.0

v0.63.0

v0.62.3

v0.62.2

v0.62.1

v0.62.0

v0.61.2

v0.61.1

v0.61.0

v0.60.9

v0.60.8

v0.60.7

v0.60.6

v0.60.5

v0.60.4

v0.60.3

v0.60.2

v0.60.1

v0.60.0

v0.59.13

v0.59.12

v0.59.11

v0.59.10

v0.59.9

v0.59.8

v0.59.7

v0.59.6

v0.59.5

v0.59.4

v0.59.3

v0.59.2

v0.59.1

v0.59.0

v0.58.2

v0.58.1

v0.58.0

v0.57.1

v0.57.0

v0.56.1

v0.56.0

v0.55.1

v0.55.0

v0.54.2

v0.54.1

v0.54.0

v0.53.0

v0.52.2

v0.52.1

v0.52.0

v0.51.2

v0.51.1

v0.51.0

v0.50.3

v0.50.2

v0.50.1

v0.50.0

v0.49.0

v0.48.0-dev2

v0.48.0

v0.47.2

v0.47.1

v0.47.0

v0.46.0

v0.45.3

v0.45.2

v0.45.1

v0.45.0

v0.44.0

v0.43.3

v0.43.2

v0.43.1

v0.43.0

v0.42.0

v0.41.3

v0.41.2

v0.41.1

v0.41.0

v0.40.1

v0.40.0

v0.39.2

v0.39.1

v0.39.0

v0.38.2

v0.38.1

v0.38.0

v0.37.2

v0.37.1

v0.37.0

v0.36.7

v0.36.6

v0.36.5

v0.36.4

v0.36.3

v0.36.2

v0.36.1

v0.36.0

v0.35.2

v0.35.1

v0.35.0

v0.34.1

v0.34.0

v0.33.0

v0.32.0

v0.31.1

v0.31.0

v0.30.3

v0.30.2

v0.30.1

v0.30.0

v0.29.4

v0.29.3

0.29.3

v0.29.2

v0.29.1

v0.29.0

v0.28.9

v0.28.8

v0.28.7

v0.28.6

v0.28.5

v0.28.4

v0.28.3

v0.28.2

v0.28.1

v0.28.0

v0.27.10

v0.27.9

v0.27.8

v0.27.7

v0.27.6

v0.27.5

v0.27.4

v0.27.3

v0.27.2

v0.27.1

v0.27.0

v0.26.7

v0.26.6

v0.26.5

v0.26.4

v0.26.3

v0.26.2

v0.26.1

v0.26.0

v0.25.9

v0.25.8

v0.25.7

v0.25.6

v0.25.5

v0.25.4

v0.25.3

v0.25.2

v0.25.1

v0.25.0

v0.24.4

v0.24.3

v0.24.2

v0.24.1

v0.24.0

v0.23.9

v0.23.8

v0.23.7

v0.23.6

v0.23.5

v0.23.4

v0.23.3

v0.23.2

v0.23.1

v0.23.0

v0.22.7

v0.22.6

v0.22.5

v0.22.4

v0.22.3

v0.22.2

v0.22.1

v0.22.0

v0.21.11

v0.21.10

v0.21.9

v0.21.8

v0.21.7

v0.21.6

v0.21.5

v0.21.4

v0.21.3

v0.21.2

v0.21.1

v0.21.0

v0.20.8

v0.20.7

v0.20.6

v0.20.5

v0.20.4

v0.20.3

v0.20.2

v0.20.1

v0.20.0

v0.19.0

v0.18.1

v0.18.0

v0.17.0

v0.16.0

v0.15.3

v0.15.2

v0.15.1

v0.15.0

v0.14.6

v0.14.5

v0.14.4

v0.14.3

v0.14.2

v0.14.1

v0.14.0

v0.13.0

v0.12.0

v0.11.6

v0.11.5

v0.11.4

v0.11.3

v0.11.2

v0.11.1

v0.11.0

v0.10.10

v0.10.9

v0.10.8

v0.10.7

v0.10.6

v0.10.5

v0.10.4

v0.10.3

v0.10.2

v0.10.1

v0.10.0

v0.9.8

v0.9.7

v0.9.6

v0.9.5

v0.9.4

v0.9.3

v0.9.2

v0.9.1

v0.9.0

v0.8.12

v0.8.11

v0.8.10

v0.8.9

v0.8.8

v0.8.7

v0.8.6

v0.8.5

v0.8.4

v0.8.3

v0.8.2

v0.8.1

v0.8.0

v0.7.1

v0.7.0

v0.6.4

v0.6.3

v0.6.2

v0.6.1

v0.6.0

v0.5.11

v0.5.10

v0.5.1

v0.5.0

v0.4.0

v0.3.5

v0.3.4

v0.3.3

v0.3.2

v0.3.1

v0.3.0

v0.2.3

v0.2.2-beta.1

v0.2.1-beta.5

v0.2.0-beta.5

v0.2.0-beta.4

v0.2.0-beta.3

v0.2.0-beta.2

v0.2.0-beta.1

v0.1.0-beta.3

v0.1.0-beta.2

v0.1.0-beta.1

v0.1.0-rc.2

v0.1.0-rc-1

v0.0.8-hotfix-1

v0.0.8

v0.0.7

v0.0.6

v0.0.5

v0.0.4

v0.0.3

v0.0.2

v0.0.1

v0.0.0

Labels

Clear labels

2021 Q4

2022 Q1

2022 Q1

accessibility

acl

agent

agent

Android

Android

api

authentik

automation

azure

battery-usage

bug

cache

client

client-ui

cloud

cloud-only

cloudflare

community

compatibility

config-idp

config-issue

connection

contribution

coturn

cross-vpn

dashboard

data-usage

distribution

dns

docker

documentation

duplicate

enhancement

enhancement

event-stream

feature-request

freebsd

getting-started

go

good first issue

gui

help wanted

home-assistant

idp

inconsistency

integration

integrations

ios

ipv6

jwt

k8s

keycloak

linux

login

macos

management-service

missing-docs

mobile

moved-internal

needs-review

netbird-ui

networking

new-platform

nginx

notification

okta

openwrt

packaging

peer-management

peer-management

peer-management

performance

postgres

posture-checks

psk

pull-request

Mirrored from GitHub Pull Request

question

refactor

relay

release

rfc

routes

security

security-related

self-hosting

server

signal

sleep-issue

ssh

ssl

status

store

synology

system-compatibility-issue

test-suite

third-party-integration

triage

triage-needed

troubleshooting

UX

waiting-feedback

windows

wontfix

zitadel

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

saavagebueno

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SVI/netbird#81