MeTube service after fresh install or update fails to start

[romdim]

✅ Have you read and understood the above guidelines?

yes

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

MeTube

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/metube.sh)" or update on an old version

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/8.4.9/649acf70aab54798 (running kernel: 6.8.12-11-pve)

📝 Provide a clear and concise description of the issue.

After running update on an older version of MeTube or even with a fresh install everything run smoothly on the pve console but the service never starts within the LXC.

🔄 Steps to reproduce the issue.

Step1: run update within the LXC

Alternative

Step1: run the install command in your pve shell

❌ Paste the full error output (if available).

Sep 26 13:06:35 metube systemd[1]: Started metube.service - Metube - YouTube Downloader.
░░ Subject: A start job for unit metube.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit metube.service has finished successfully.
░░ 
░░ The job identifier is 787.
Sep 26 13:06:35 metube pipenv[16192]: Loading .env environment variables...
Sep 26 13:06:35 metube pipenv[16192]: Traceback (most recent call last):
Sep 26 13:06:35 metube pipenv[16192]:   File "/opt/metube/app/main.py", line 8, in <module>
Sep 26 13:06:35 metube pipenv[16192]:     from aiohttp import web
Sep 26 13:06:35 metube pipenv[16192]: ModuleNotFoundError: No module named 'aiohttp'
Sep 26 13:06:35 metube systemd[1]: metube.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit metube.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.
Sep 26 13:06:35 metube systemd[1]: metube.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit metube.service has entered the 'failed' state with result 'exit-code'.

🖼️ Additional context (optional).

No response

[michelroegl-brunner]

I can indeed reproduce this on a new install. But it is not realted with our script. Ther is a Problem with Metube, they seem to have a dependencie error. Nothing we can do here, you need to report that in the Metube Repo. It can not find a imported module.

Sep 26 13:06:35 metube pipenv[16192]: Loading .env environment variables...
Sep 26 13:06:35 metube pipenv[16192]: Traceback (most recent call last):
Sep 26 13:06:35 metube pipenv[16192]:   File "/opt/metube/app/main.py", line 8, in <module>
Sep 26 13:06:35 metube pipenv[16192]:     from aiohttp import web
Sep 26 13:06:35 metube pipenv[16192]: ModuleNotFoundError: No module named 'aiohttp'
Sep 26 13:06:35 metube systemd[1]: metube.service: Main process exited, code=exited, status=1/FAILURE

[vhsdream]

The developer moved away from pipenv to uv in the new release just 2 days ago. It's likely that we can make changes to accommodate that. I was going to install this today anyway, so I'll take a look at the current script and see if I can fix.

[MickLesk]

Simple. uv sync done 😄 i think @vhsdream you make an pr?

[vhsdream]

Not going to be that simple. Google made a change to their code and now all YTDL-type apps need to pivot by adding Deno to their apps, otherwise downloading is broken (for Youtube).

I have a successful uv-based install of this, and I chose to install Deno via NPM but that didn't work - 403 when downloading, so I'll try another method.

[vhsdream]

403 was a separate issue that can be worked-around with certain yt-dlp flags; and Deno isn't needed yet but I've left it in the PR because it could be needed any day now.