17/Mar/2022 15:57:54 [edge_utils.c:3603] Adding supernode = vip00.happyn.cc:30191
17/Mar/2022 15:57:54 [edge.c:960] WARNING: Switching to AES as key was provided.
17/Mar/2022 15:57:54 [edge.c:1000] Starting n2n edge 2.9.0.r945.2a8c13f.happyn Aug 8 2021 17:39:49
17/Mar/2022 15:57:54 [edge.c:1006] Using compression: lzo1x.
17/Mar/2022 15:57:54 [edge.c:1007] Using AES cipher.
17/Mar/2022 15:57:54 [edge_utils.c:330] Number of supernodes in the list: 1
17/Mar/2022 15:57:54 [edge_utils.c:332] supernode 0 => vip00.happyn.cc:30191
17/Mar/2022 15:57:54 [edge.c:1028] Successfully created resolver thread
17/Mar/2022 15:57:54 [edge.c:1035] Use manually set IP address.
Open device [name={26EAEC1C-B876-44CB-B144-ABEEAB9BB292}][ip=10.223.0.5][ifName=ÒÔÌ«Íø][MTU=1290][mac=00:FF:26:EA:EC:1C]
17/Mar/2022 15:57:55 [edge.c:1151] Created local tap device IP: 10.223.0.5, Mask: 255.255.255.0, MAC: 00:FF:26:EA:EC:1C
17/Mar/2022 15:57:55 [edge.c:1251] edge started
17/Mar/2022 15:57:55 [edge_utils.c:1048] Successfully joined multicast group 224.0.0.68:1968
17/Mar/2022 15:58:07 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:58:23 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:58:39 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:58:55 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:59:11 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:59:27 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:59:43 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 15:59:59 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191
17/Mar/2022 16:00:15 [edge_utils.c:1452] WARNING: Supernode not responding, now trying vip00.happyn.cc:30191

    foxcell

    检查一下 服务ID、服务密钥 填对了没有?

    一般这种情况是服务ID填错了;

    或者停止后重新连接一下试试?

    可以截图发送邮箱: support@happyn.cn ;我们帮您看一下;

    跟用户沟通,重启后就正常运行了;

    大概是windows 多网卡适配的时候没有做好,导致初次连接的时候没有正常联通;

    最近多个客户遇到Windows段连接的问题,但是原因不同,总结了一下:

    1. 机器设置了自动获取IP,但是局域网内另外一台机器手工设置了与此机器相同的IP,导致MAC地址冲突;

    表现: happynet客户端连接成功,局域网内其它机器ping不通此台机器

    解决方法: 改为手工设置不冲突的ip; 然后其它机器手工清除ARP表,以管理员权限打开命令行窗口,执行: arp -d


    2. 机器一直连接不上

    表现: happynet客户端一直报错"WARNING: Supernode not responding, now trying"

    解决方法: 发现有用户开启了高级设置中的启用本地数据转发功能;这个功能是将来准备为VIP套餐提供的,暂时不用开启;关闭这个选项重新启动就好了; 正常配置示例如下(除了本地数据压缩功能,其它暂时不要开):


    3. 机器有时候连接上,有时候又不行了

    表现: 部分免费用户报告,happynet客户端断断续续报错"WARNING: Supernode not responding, now trying"

    解决方法: 这是因为happynet客户端所处网络环境不稳定,happynet是通过UDP通信的,在某些地方宽带运营商对于UDP数据包做了QOS限制; 为了解决这个问题,我们为免费用户提供了备用服务器,请在 自定义参数 中加入:

    -l rvip.happyn.cc:3xxxx

    端口与分配给您的服务器端口保持一致;

    设置完毕后重新启动服务即可;

    5 天 后
    happynsupport 更改标题为「[问题]Windows启动时,一直报错"WARNING: Supernode not responding, now trying"