-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
β Have you read and understood the above guidelines?
Yes
π What is the name of the script you are using?
MySpeed
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myspeed.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.
The MySpeed LXC container on Proxmox (installed via tteck community fails to start the web interface. The frontend directory is missing, and the backend crashes with a Sequelize Validation error.
The install script pulls the latest release ZIP from GitHub, installs Node.js v22, installs dependencies, and starts a systemd service with ExecStart=/usr/bin/node server. However, runtime issues prevent the application from functioning correctly.
Observed Behavior
/opt/myspeed/client/ does not exist (frontend fails)
Running npm run dev fails with:
sh: 1: cd: can't cd to client
Running the backend directly shows:
Successfully connected to the database file
An error occurred: Validation error
π Steps to reproduce the issue.
- Start the LXC container: pct start 123
- Attach to it: pct exec 123 -- bash
- Navigate to the app folder: cd /opt/myspeed
- Run the server: npm run server
- Observe the backend crash with Validation error
β Paste the full error output (if available).
Successfully connected to the database file
An error occurred: Validation error
[nodemon] app crashed - waiting for file changes before starting...
Using DEBUG=* node server shows that Sequelize attempts to backup, drop, and recreate multiple tables (integration_data, config, nodes, speedtests), and then fails after reinserting data.
Despite running many INSERT INTO ... SELECT ... FROM ... statements successfully, the app crashes with no stack trace by default.
πΌοΈ Additional context (optional).
- The app uses SQLite as its database and Sequelize ORM.
- Issue may stem from missing client/ in the ZIP, schema/data mismatch in SQLite, or Node version compatibility.
- Repeated table migrations seen in Sequelize debug output (e.g. backup-drop-recreate cycles for integration_data, nodes, config, speedtests).
Environment
- Node.js v22 (installed by setup_nodejs)
- OS: Debian 12-based LXC on Proxmox
- App: Latest MySpeed release ZIP (from GitHub)
Filesystem & Install Script Observations
- The extracted contents from the release ZIP in /opt/myspeed do not include the client/ directory.
- The install script attempts to write version info to /opt/${APPLICATION}_version.txt, but ${APPLICATION} is never defined, so the version file is never created.
- As a result, there is no way to confirm which release version was actually installed.