Librespeed Rust doesn't read the config file #1482

New Issue

OVERLORD · 2026-02-05T01:16:23+03:00

OVERLORD commented

2026-02-05 01:16:23 +03:00

Originally created by @Denny-89 on GitHub (Aug 19, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Librespeed Rust

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/librespeed-rust.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

It seems the thing doesn't read the config file. First i thought i can't set port 80 because of some Rust security feature (i'm not familiar with it), but then i noticed ports like 9999 and similar also won't work; i even tried to change the LXC to privileged. Only port 8080 worked because it's seemingly somewhere hardcoded or there is a second config file with the defaults...no clue, didn't have time to check it. Dark mode and redact IP addresses also doesn't work.

Looks like a part of the config file is accepted because i was able to disable the sqlite database and it didn't give me the jpeg speedtest results.

🔄 Steps to reproduce the issue.

Step 1: Create the LXC with the script
Step 2: Change any option inside /var/lib/librespeed-rs/configs.toml and restart the LXC
Step 3: Open the IP and notice the port is still 8080, dark mode isn't set, etc. Surprisingly changing the database from sqlite to none works

❌ Paste the full error output (if available).

Running /usr/bin/librespeed-rs -c /var/lib/librespeed-rs/configs.toml directly outputs

    | (_) |__  _ __ ___  ___ _ __   ___  ___  __| |      _ __ ___
    | | | '_ \| '__/ _ \/ __| '_ \ / _ \/ _ \/ _` |_____| '__/ __|
    | | | |_) | | |  __/\__ \ |_) |  __/  __/ (_| |_____| |  \__ \
    |_|_|_.__/|_|  \___||___/ .__/ \___|\___|\__,_|     |_|  |___/
                            |_|

[2025-08-18 23:48:13.795 INFO librespeed_rs] Config assets directory failed !
[2025-08-18 23:48:13.797 INFO librespeed_rs] Configs initialized file : /var/lib/librespeed-rs/configs.toml
[2025-08-18 23:48:13.798 INFO librespeed_rs] Database Sqlite initialized successfully
[2025-08-18 23:48:13.798 INFO librespeed_rs] Server started on 0.0.0.0:80
[2025-08-18 23:48:13.798 INFO librespeed_rs] Server base url : /backend/

🖼️ Additional context (optional).

If i change the assets_path from "./assets" to "/var/lib/librespeed-rs/assets", it surprisingly works but this shouldn't be a fix at all. Dark mode still doesn't work tho; according to librespeed.org it's supposed to look like this.

I've found a comment from the dev for a similar issue https://github.com/librespeed/speedtest-rust/issues/18#issuecomment-2562712300 and his answer was "Everything works fine with the method in the wiki."

Originally created by @Denny-89 on GitHub (Aug 19, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Librespeed Rust ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/librespeed-rust.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. It seems the thing doesn't read the config file. First i thought i can't set port 80 because of some Rust security feature (i'm not familiar with it), but then i noticed ports like 9999 and similar also won't work; i even tried to change the LXC to privileged. Only port 8080 worked because it's seemingly somewhere hardcoded or there is a second config file with the defaults...no clue, didn't have time to check it. Dark mode and redact IP addresses also doesn't work. Looks like a part of the config file is accepted because i was able to disable the sqlite database and it didn't give me the jpeg speedtest results. ### 🔄 Steps to reproduce the issue. Step 1: Create the LXC with the script Step 2: Change any option inside `/var/lib/librespeed-rs/configs.toml` and restart the LXC Step 3: Open the IP and notice the port is still 8080, dark mode isn't set, etc. Surprisingly changing the database from sqlite to none works ### ❌ Paste the full error output (if available). Running `/usr/bin/librespeed-rs -c /var/lib/librespeed-rs/configs.toml` directly outputs ``` _ _ _ _ | (_) |__ _ __ ___ ___ _ __ ___ ___ __| | _ __ ___ | | | '_ \| '__/ _ \/ __| '_ \ / _ \/ _ \/ _` |_____| '__/ __| | | | |_) | | | __/\__ \ |_) | __/ __/ (_| |_____| | \__ \ |_|_|_.__/|_| \___||___/ .__/ \___|\___|\__,_| |_| |___/ |_| [2025-08-18 23:48:13.795 INFO librespeed_rs] Config assets directory failed ! [2025-08-18 23:48:13.797 INFO librespeed_rs] Configs initialized file : /var/lib/librespeed-rs/configs.toml [2025-08-18 23:48:13.798 INFO librespeed_rs] Database Sqlite initialized successfully [2025-08-18 23:48:13.798 INFO librespeed_rs] Server started on 0.0.0.0:80 [2025-08-18 23:48:13.798 INFO librespeed_rs] Server base url : /backend/ ``` ### 🖼️ Additional context (optional). If i change the `assets_path` from `"./assets"` to `"/var/lib/librespeed-rs/assets"`, it surprisingly works but this shouldn't be a fix at all. Dark mode still doesn't work tho; according to `librespeed.org` it's supposed to look like [this](https://github.com/user-attachments/assets/417b6bb1-199f-44f5-bc94-f0dbcd5d3a6f). I've found a comment from the dev for a similar issue https://github.com/librespeed/speedtest-rust/issues/18#issuecomment-2562712300 and his answer was "Everything works fine with the method in the wiki."

OVERLORD added the external label 2026-02-05 01:16:23 +03:00

OVERLORD closed this issue

2026-02-05 01:16:25 +03:00

OVERLORD commented

2026-02-05 01:16:29 +03:00

@tremor021 commented on GitHub (Aug 19, 2025):

This has nothing to do with our script. We literaly install their .deb package...

@tremor021 commented on GitHub (Aug 19, 2025): This has nothing to do with our script. We literaly install their .deb package...

OVERLORD commented

2026-02-05 01:16:31 +03:00

@Denny-89 commented on GitHub (Aug 19, 2025):

I thought something weird happened at the docker to LXC "conversion" because the guy insisted everything works perfectly if it's done like in his wiki and will probably complain if i open an issue there. The script got the same or almost the same commands, but still...i've seen literal carbon copies of projects where some had issues where there shouldn't be any. Can someone else try it too?

@Denny-89 commented on GitHub (Aug 19, 2025): I thought something weird happened at the docker to LXC "conversion" because the guy insisted everything works perfectly if it's done like in his wiki and will probably complain if i open an issue there. The script got the same or almost the same commands, but still...i've seen literal carbon copies of projects where some had issues where there shouldn't be any. Can someone else try it too?

OVERLORD commented

2026-02-05 01:16:35 +03:00

@tremor021 commented on GitHub (Aug 19, 2025):

I really don't know. We just get the release .deb from their github and install it like every other package. We don't touch anything else. If something doesn't work properly, then its the app or .deb that has issues.

@tremor021 commented on GitHub (Aug 19, 2025): I really don't know. We just get the release .deb from their github and install it like every other package. We don't touch anything else. If something doesn't work properly, then its the app or .deb that has issues.

OVERLORD commented

2026-02-05 01:16:37 +03:00

@del13r commented on GitHub (Oct 14, 2025):

i also have this same issue

@del13r commented on GitHub (Oct 14, 2025): i also have this same issue

OVERLORD referenced this issue

2026-02-05 05:27:31 +03:00

[PR #1482] [MERGED] New script: SQL Server 2022 #3072

OVERLORD referenced this issue

2026-02-05 05:32:25 +03:00

[PR #1669] [MERGED] Fix: SQL Server 2022 Install #3168

Sign in to join this conversation.