[Help me] After upgrade to 1.3.0, the server cannot be connected.

[glamoroussky]

Details

All the settings are remain the same, the only thing I did is using the script to upgrade Hysteria to the 1.3.0 version. Right after I restart the hysteria after upgrade, the connection never worked. The server is up and running good anyway. For all my other server, I stayed in the previous version, and they are working perfectly. Is there any changes in the config formatting?

Hysteria server information

hysteria version v1.3.0 2022-11-08 04:55:38 385c2d6845b085ae788367be659ff7c752d44804

VPS information

Terminal on MacOS, Hetzner, Finland, 4GB RAM, 2 Cores.

Server config

{ "listen": ":10804", "protocol": "udp", "cert": "/etc/letsencrypt/live/xxx.co/fullchain.pem", "key": "/etc/letsencrypt/live/xxx.co/privkey.pem", "up_mbps": 500, "down_mbps": 500, "obfs": "XXXXXX", "auth": { "mode": "passwords", "config": ["XXXXXX", "XXXXX2", "XXXXXX3"] }, "alpn": "h2", "recv_window_conn": 52428800, "recv_window_client": 209715200, "resolver": "tls://1.1.1.1:853" }

Server logs

Systemctl status: hysteria-server.service - Hysteria, a feature-packed network utility optimized for networks of poor quality Loaded: loaded (/lib/systemd/system/hysteria-server.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-11-13 06:43:31 UTC; 3min 20s ago Docs: https://github.com/HyNetwork/hysteria/wiki Main PID: 754 (hysteria) Tasks: 5 (limit: 4556) Memory: 33.3M CGroup: /system.slice/hysteria-server.service └─754 /usr/local/bin/hysteria -c /etc/hysteria/config.json server

Nov 13 06:43:31 systemd[1]: Started Hysteria, a feature-packed network utility optimized for networks of poor quali> Nov 13 06:43:32 hysteria[754]: 2022-11-13T06:43:32Z [INFO] [config:{Listen::10804 Protocol:udp ACME:{Domains:[] Ema> Nov 13 06:43:32 hysteria[754]: 2022-11-13T06:43:32Z [INFO] Password authentication enabled Nov 13 06:43:32 hysteria[754]: 2022-11-13T06:43:32Z [INFO] [addr::10704] Server up and running

Journalctl:

Nov 13 06:42:48 systemd[1]: Stopped Hysteria, a feature-packed network utility optimized for networks of poor quali> -- Reboot -- Nov 13 06:43:31 systemd[1]: Started Hysteria, a feature-packed network utility optimized for networks of poor quali> Nov 13 06:43:32 hysteria[754]: 2022-11-13T06:43:32Z [INFO] [config:{Listen::10804 Protocol:udp ACME:{Domains:[] Ema> Nov 13 06:43:32 hysteria[754]: 2022-11-13T06:43:32Z [INFO] Password authentication enabled Nov 13 06:43:32 hysteria[754]: 2022-11-13T06:43:32Z [INFO] [addr::10704] Server up and running

Hysteria client information

Shadowrocket

Client config

N/A

Client environment (operating system)

MacOS M1/ iOS

Client logs

N/A

[tobyxdd]

This is strange. 1.3.0 doesn't have any changes that would make it not backward compatible, and I've personally tested it multiple times without problems. Are you saying your 1.3.0 server doesn't work with older clients (but works with 1.3.0 clients), or are you not able to connect either way?

[glamoroussky]

This is strange. 1.3.0 doesn't have any changes that would make it not backward compatible, and I've personally tested it multiple times without problems. Are you saying your 1.3.0 server doesn't work with older clients (but works with 1.3.0 clients), or are you not able to connect either way?

So I am using Shadowrocket on Mac and iOS, I have three servers been implemented Hysteria. I upgrade one server to the 1.3.0 and then, it cannot be connected anymore. However the other two, which are not been upgraded, are perfectly fine. And I just upgrade the first server from 1.3.0 to 1.3.1, but still, it cannot be connected with Shadowrocket.

[haruue]

Could you please try to downgrade the first server to v1.2.2 (or the version you used before upgraded to 1.3.0), and check whether it can be connected or not.

And what's the "previous version" you are using on the other two server?

[glamoroussky]

Could you please try to downgrade the first server to v1.2.2, and check whether it can be connected or not. I installed the server by using the one-click-script you officially provided. Could you please tell me how to do that? I am not good at this. XD

[haruue]

Which script are you using?

[glamoroussky]

Which script are you using?

https://raw.githubusercontent.com/apernet/hysteria/master/install_server.sh

I just release it has been modified 9 days ago, but I have been using the previous version for half year. Is it possible this the cause of the problem?

Also, the other tow server are still using 1.2.2 and they are fine.

[haruue]

I just realized it has been modified 9 days ago, but I have been using the previous version for half year. Is it possible this the cause of the problem?

I tested the script without the 9-day-ago patch and it works well. Though it is still recommend to keep your script up-to-dated.

Also, the other tow server are still using 1.2.2 and they are fine.

You can just copy /usr/local/bin/hysteria from other two working server to the first server, and restart hysteria-server.service.

[glamoroussky]

I just realized it has been modified 9 days ago, but I have been using the previous version for half year. Is it possible this the cause of the problem?

I tested the script without the 9-day-ago patch and it works well. Though it is still recommend to keep your script up-to-dated.

Also, the other tow server are still using 1.2.2 and they are fine.

You can just copy /usr/local/bin/hysteria from other two working server to the first server, and restart hysteria-server.service.

Thank you Haruue, I would like to keep them status quo, and wait for a version that actually work for my first server then upgrade them together.

[haruue]

What I mean is maybe it is only a connective problem between you and the first server, such as wrong-configured firewalls or the UDP port you are using being banned by GFW.

Rollback to a "working" version is a good way to rule out such kind of problems.

[iceyheart]

我也遇见了这个问题。从1.3.0开始到现在1.3.1，服务器status正常，也显示了客户端IP，但是就是连不上，不起作用。

[haruue]

我也遇见了这个问题。从1.3.0开始到现在1.3.1，服务器status正常，也显示了客户端IP，但是就是连不上，不起作用。

@iceyheart 能开一个新的 Issue 重新发一下你遇到的问题吗？ 需要服务端和客户端的配置、 日志、 服务端运行环境（操作系统、 VPS）， 我需要复现了这个问题才能给你们解决。