starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #2498] Rust: error when using mods-update #1840

New issue

Closed

opened 2026-02-27 02:59:18 +03:00 by kerem · 12 comments

kerem commented

2026-02-27 02:59:18 +03:00

Owner

Originally created by @sasjafor on GitHub (Sep 5, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2498

User Story

When I use ./linuxgsm mods-update I get a failure and I believe the relevant part is this error:
curl: (3) URL using bad/illegal format or missing URL.

Basic info

Distro: Ubuntu 19.04
Game: Rust
Command: mods-update

Further Information

It only started happening today since the new rust update

To Reproduce

Steps to reproduce the behaviour:

Run rust server
Run ./linuxgsm mods-update after todays rust update
See error Failure! An issue occurred downloading Oxide for Rust

Expected behaviour

No error and working mod update.

Originally created by @sasjafor on GitHub (Sep 5, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2498 ## User Story When I use ./linuxgsm mods-update I get a failure and I believe the relevant part is this error: `curl: (3) URL using bad/illegal format or missing URL`. ## Basic info * Distro: Ubuntu 19.04 * Game: Rust * Command: mods-update ## Further Information It only started happening today since the new rust update ## To Reproduce Steps to reproduce the behaviour: 1. Run rust server 2. Run ./linuxgsm mods-update after todays rust update 3. See error `Failure! An issue occurred downloading Oxide for Rust` ## Expected behaviour No error and working mod update.

kerem

2026-02-27 02:59:18 +03:00

closed this issue
added the
type: bug

game: Rust
labels

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Sep 5, 2019):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.91. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Sep 5, 2019): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.91. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@carek5 commented on GitHub (Sep 5, 2019):

The same

@carek5 commented on GitHub (Sep 5, 2019): The same

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@psycomaffo commented on GitHub (Sep 6, 2019):

i had the same issue on 3 server, but with a different error on CentOS7...
with the command "mods-update", on 2 server i get
"curl: (3) Illegal characters found in URL
Failure! An issue occurred downloading Oxide for Rust"
and to the otherone i get this
"curl: (3) Illegal characters found in URL
FAIL
https://github.com/theumod/uMod.Rust/releases/download/2.0.4268/Oxide.Rust-LinuxFix.zip
https://github.com/theumod/uMod.Rust/releases/download/2.0.4268/Oxide.Rust.zip"
i already did the update-lgsm but the servers shoutdown immediatly after the start
sry for my bad english and if i'm in wrong to post here

@psycomaffo commented on GitHub (Sep 6, 2019): i had the same issue on 3 server, but with a different error on CentOS7... with the command "mods-update", on 2 server i get "curl: (3) Illegal characters found in URL Failure! An issue occurred downloading Oxide for Rust" and to the otherone i get this "curl: (3) Illegal characters found in URL FAIL https://github.com/theumod/uMod.Rust/releases/download/2.0.4268/Oxide.Rust-LinuxFix.zip https://github.com/theumod/uMod.Rust/releases/download/2.0.4268/Oxide.Rust.zip" i already did the update-lgsm but the servers shoutdown immediatly after the start sry for my bad english and if i'm in wrong to post here <blockquote></blockquote> <blockquote></blockquote>

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@carek5 commented on GitHub (Sep 6, 2019):

https://umod.org/community/rust/12061-server-not-starting-with-oxide?page=8

Helped for me

uMod - Server not starting with Oxide - Rust - Community
uMod is a universal modding platform, framework, and plugin API for Unity, .NET/C#, Unreal, and C++ games

@carek5 commented on GitHub (Sep 6, 2019): https://umod.org/community/rust/12061-server-not-starting-with-oxide?page=8 Helped for me <blockquote><img src="https://assets.umod.org/images/umod-favicon.png" width="48" align="right"><div><strong><a href="https://umod.org/community/rust/12061-server-not-starting-with-oxide?page=8">uMod - Server not starting with Oxide - Rust - Community</a></strong></div><div>uMod is a universal modding platform, framework, and plugin API for Unity, .NET/C#, Unreal, and C++ games</div></blockquote>

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@psycomaffo commented on GitHub (Sep 6, 2019):

Thanx a lot caker5... i already seen something like this some hours ago, but i didn't read about the LinuxFix Files.... now all work fine... tnx again

@psycomaffo commented on GitHub (Sep 6, 2019): Thanx a lot caker5... i already seen something like this some hours ago, but i didn't read about the LinuxFix Files.... now all work fine... tnx again

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@lukespragg commented on GitHub (Sep 6, 2019):

I believe this is caused by the assumption that the URL used will always have the filename in the URL, which they do not. In this case, our develop URL redirects to a URL that CONTAINS a filename, but doesn't END with a filename as it has arguments in the URL.

The solution should be for LGSM to always set a filename when using curl to grab the file, instead of using whatever the URL may or may not contain as the filename.

https://umod.org/games/rust/download/develop is the URL currently for our Linux builds, which redirects to https://ci.appveyor.com/api/projects/umod/umod-rust/artifacts/Oxide.Rust-linux.zip?pr=false&branch=linux. The redirect is already handled by LGSM, but the filename is not from what I can tell as I believe it tries to get it from the URL.

Edit: May not be the case after another look over LGSM. It was mentioned that replacing the curl and GitHub handling at https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/mods_list.sh#L40 with the develop URL should be enough.

@lukespragg commented on GitHub (Sep 6, 2019): I believe this is caused by the assumption that the URL used will always have the filename in the URL, which they do not. In this case, our develop URL redirects to a URL that CONTAINS a filename, but doesn't END with a filename as it has arguments in the URL. The solution should be for LGSM to always set a filename when using curl to grab the file, instead of using whatever the URL may or may not contain as the filename. https://umod.org/games/rust/download/develop is the URL currently for our Linux builds, which redirects to https://ci.appveyor.com/api/projects/umod/umod-rust/artifacts/Oxide.Rust-linux.zip?pr=false&branch=linux. The redirect is already handled by LGSM, but the filename is not from what I can tell as I believe it tries to get it from the URL. **Edit:** May not be the case after another look over LGSM. It was mentioned that replacing the curl and GitHub handling at https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/mods_list.sh#L40 with the develop URL should be enough.

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@sasjafor commented on GitHub (Sep 14, 2019):

I did some testing, and with the PR it does now correctly download and apply oxide. But it does it everytime the mods-update command is run. So it doesn't seem to detect that oxide is already up to date.

@sasjafor commented on GitHub (Sep 14, 2019): I did some testing, and with the PR it does now correctly download and apply oxide. But it does it everytime the mods-update command is run. So it doesn't seem to detect that oxide is already up to date.

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@Frisasky commented on GitHub (Sep 14, 2019):

lgsm did not detect which version installed, it just fetch latest version and overwritten old files

@Frisasky commented on GitHub (Sep 14, 2019): lgsm did not detect which version installed, it just fetch latest version and overwritten old files

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@sasjafor commented on GitHub (Sep 14, 2019):

Yes. But I thought it did detect it before? Because I run it with a cronjob. So I don't want it downloading oxide everytime that command runs.

@sasjafor commented on GitHub (Sep 14, 2019): Yes. But I thought it did detect it before? Because I run it with a cronjob. So I don't want it downloading oxide everytime that command runs.

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@Frisasky commented on GitHub (Sep 14, 2019):

all mod related function are included in this file, you did not find a function called check mod version, right?
https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/mods_core.sh

GitHub
GameServerManagers/LinuxGSM
Linux Game Server Managers_. Contribute to GameServerManagers/LinuxGSM development by creating an account on GitHub.

@Frisasky commented on GitHub (Sep 14, 2019): all mod related function are included in this file, you did not find a function called check mod version, right? https://github.com/GameServerManagers/LinuxGSM/blob/master/lgsm/functions/mods_core.sh <blockquote><img src="https://repository-images.githubusercontent.com/12000586/6e5e5300-8628-11e9-97fa-adcf12828a7c" width="48" align="right"><div><img src="https://github.githubassets.com/favicon.ico" height="14"> GitHub</div><div><strong><a href="https://github.com/GameServerManagers/LinuxGSM">GameServerManagers/LinuxGSM</a></strong></div><div>Linux Game Server Managers_. Contribute to GameServerManagers/LinuxGSM development by creating an account on GitHub.</div></blockquote>

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@sasjafor commented on GitHub (Sep 14, 2019):

Alright, I'll open a feature request then.

@sasjafor commented on GitHub (Sep 14, 2019): Alright, I'll open a feature request then.

kerem commented

2026-02-27 02:59:19 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 24, 2020):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Dec 24, 2020): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.