Self-Updater Target URL 404 for Latest Release

[komori]

It seems like the latest releases' built package didn't make it on the latest release (v3.3.2b) post.

On startup, my v3.2.1b release notified me of the new version (v3.3.2b) and offered update as usual, but immediately after the download confirmation prompt it fails, prints some errors, and promptly closes the program.

Taking a closer look it the update download URL, https://github.com/Lacyway/V-Rising-Server-Manager/releases/latest/download/VSM.zip, redirects and resolves to https://github.com/Lacyway/V-Rising-Server-Manager/releases/download/v3.3.2-beta/VSM.zip, which returns a 404 from Github causing the abrupt program exit.

I'm not waiting on any fix or changes--the current feature set is much more than I could've hoped for when I stumbled across VSM last weekend--3.2.1b has smooth sailing for me. I mostly wanted to give a quick heads-up if v3.3.2b was released in rushed circumstances for whatever reason and the missing package zip was just overlooked.

That, and I definitely wanted to say "thank you!" and voice my appreciation for sharing your project here. I work in IT, on the net-eng portion of the field, so I was getting very exasperated with the current state of deprecated and incomplete official documentation. Mostly due to my inability to get a darned simple gameserver up, running & listed from a win VM running on a Proxmox host at home. Granted, I was trying to hustle through it, but using a disjointed array of various forum posts, gaming blogs, document fragments on github, etc was an easy target for the lack of prompt success.

Anyhoow, I've since sorted out which options were deprecated and causing my problems, but VSM and your, albeit brief, setup wiki got me up and running on the first pass. It was so painless and easy that I was skeptical the server was functional when I first saw the listing appear in-game. It's been great for me since. The only snag I've found is the automatic gameserver update process appeared to leave a process running that held onto udp/9876-9877 causing conflict when it tries to launch the updated server. I'm not even certain root cause was VSM, so I'll turn auto-updates back on in the near future or pull an older version via steamcmd and let VSM update it while logging all the things and let you know what role VSM plays--if any--in the failure to re-launch. I've rambled enough, so one last hurrah for this little beacon of light in a sea of partially deprecated and incomplete documentation. I've got two worlds humming along nice stable, oh, and the tooltips for each game setting are such an stellar time-saver and amazing QoL feature as someone new to the game, thanks again!

[Lacyway]

Thank you for the nice words!

I seem to have missed uploading it, thanks for letting me know. I've uploaded it now.

I'll have a look at the Wiki soon, I kind of updated it very sloppy after >3.0 because there were so many changes and time is a luxury these days.

The process holding on those ports must be the HttpClient sending a GET request to steamcmd.net to get the latest update time, they're not supposed to be disposed of according to the documentation but I was worried something like this would eventually happen. Before I used SteamCMD and read all the output, but I noticed it was so damn inconsistent and slow so I resorted to this solution recently. If it does happen again, please let me know and I'll have to look at an alternative solution for the HttpClient. 👍

[Lacyway]

At a closer look it should only be using port 80 and 443, but if it happens again let me know and I'll set a timeout to ~2 minutes according to the documentation and see if that helps.

[komori]

I'll have a look at the Wiki soon, I kind of updated it very sloppy after >3.0 because there were so many changes and time is a luxury these days.

Ah, I was ranting about Stunlock's documentation, or lack thereof. I know they're considered an "indie" studio, but I'd think ensuring a smooth process for their customers who are trying to use their own resources running game servers would be a fairly significant priority. Your documentation, on the other hand, has been on-point and plenty thorough--I followed the steps and it produced [two] stable servers that have ran great since the first time they were fired up through VSM.

The self-update worked great, running v3.3.2b now. I haven't spent the time to create a new out-of-date server to test the update process to investigate the port conflict yet. But I do have whatever debug & logging options I could find turned up so I should get something when Stunlock pushes the next patch. Thanks again!

[aishuocuohuadedashu]

I would like to ask you, my own server can not be displayed in the public list, the steam game list can be seen." ListOnSteam": true, "ListOnEOS": true, these two files are set and are not displayed

[Lacyway]

I would like to ask you, my own server can not be displayed in the public list, the steam game list can be seen." ListOnSteam": true, "ListOnEOS": true, these two files are set and are not displayed

This is an issue with the game that has been a problem since release for me too. Sometimes it works, sometimes it doesn't. Make sure ports are open and sometimes it takes ~5 minutes until it appears. Otherwise I'd advise you to check if someone can help you on the Official VRising Discord, I see people posting this problem every now and then and maybe they've found a solution.

[aishuocuohuadedashu]

I would like to ask you, my own server can not be displayed in the public list, the steam game list can be seen." ListOnSteam": true, "ListOnEOS": true, these two files are set and are not displayed

This is an issue with the game that has been a problem since release for me too. Sometimes it works, sometimes it doesn't. Make sure ports are open and sometimes it takes ~5 minutes until it appears. Otherwise I'd advise you to check if someone can help you on the Official VRising Discord, I see people posting this problem every now and then and maybe they've found a solution.

I have not found an effective way, the server has not appeared in the public list, I came here for help! I am a Chinese gamer, because some networks are not accessible, so I come here for help

[Lacyway]

I would like to ask you, my own server can not be displayed in the public list, the steam game list can be seen." ListOnSteam": true, "ListOnEOS": true, these two files are set and are not displayed

This is an issue with the game that has been a problem since release for me too. Sometimes it works, sometimes it doesn't. Make sure ports are open and sometimes it takes ~5 minutes until it appears. Otherwise I'd advise you to check if someone can help you on the Official VRising Discord, I see people posting this problem every now and then and maybe they've found a solution.

I have not found an effective way, the server has not appeared in the public list, I came here for help! I am a Chinese gamer, because some networks are not accessible, so I come here for help

You could try changing the game and query port to something else, like 27015 and 27016. That seems to have worked for some people.

There is not much else I can do to assist, sorry. It's an issue with the game.

[aishuocuohuadedashu]

请问各位，我自己的服务器不能显示在公共列表中，steam游戏列表可以看到。“ListOnSteam”:true，“ListOnEOS”:true，设置这两个文件，不显示

这是游戏的一个问题，自发布以来对我来说也是一个问题。有时行得通，有时行不通。确保端口打开，有时大约需要5分钟才会出现。否则，我会建议你检查一下是否有人能在官方的不和谐上帮助你，我看到人们不时地张贴这个问题，也许他们已经找到了解决办法。

我还没有找到有效的方法，服务器还没有出现在公共列表中，我来这里寻求帮助！我是一名中国游戏玩家，因为一些网络无法访问，所以我来这里寻求帮助

您可以尝试将游戏和查询端口更改为其他端口，如27015和27016。这似乎对一些人有效。

抱歉，我帮不上什么忙。这是游戏的问题。

Ok, thanks for your answer