Error when installing FileFlows #1890

Closed
opened 2025-11-20 05:19:20 -05:00 by saavagebueno · 3 comments
Owner

Originally created by @Waylikemark on GitHub (Sep 12, 2025).

Have you read and understood the above guidelines?

yes

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

FileFlows

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

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

⚙️ 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/9.0.9/117b893e0e6a4fee (running kernel: 6.14.11-1-pve)

📝 Provide a clear and concise description of the issue.

When trying to install the FileFlows script on PVE this results in an error (see below). Every step runs just fine up until it will install FileFlows itself then it runs into an error. Tested with both default settings and advanced settings both are not working. Also tried Unprivileged vs privileged and different storage options.

The script seems to fail when connecting to FileFlows.com. Pinging to fileflows.com from any device (including the PVE node) is possible. The PVE node is not connected to any pi-hole or something similar in case it should be relevant. PVE's DNS server is configured to 1.1.1.1 and 8.8.8.8.

🔄 Steps to reproduce the issue.

run: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/fileflows.sh)" on PVE shell. Either choose default settings or below advanced settings (which are basically default settings but without tags) to reproduce the error.


/ () / / / / _ _______
/ /
/ / / _ / /
/ / __ \ | /| / / /
/ __/ / / / __/ __/ / / /
/ / |/ |/ (
)
// ///___// //_/|/|__/____/

🧩 Using Advanced Settings on node martines
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 120
🏠 Hostname: fileflows
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IPv4: DHCP
📡 IPv6: SLAAC/AUTO
📡 APT-Cacher IP Address: Default
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: ;
🔑 Root SSH Access: yes
🗂️ Enable FUSE Support: yes
🔍 Verbose Mode: no
🚀 Creating a FileFlows LXC using the above advanced settings
✔️ Storage local (Free: 79.2GB Used: 7.9GB) [Template]
✔️ Storage local-lvm (Free: 750.7GB Used: 25.1GB) [Container]
✔️ Template debian-12-standard_12.7-1_amd64.tar.zst [local]
✔️ LXC Container 120 was successfully created.

⚙️ Configuring VAAPI passthrough for LXC container
⚠️ Container is unprivileged – VAAPI passthrough may not work without additional host configuration (e.g., idmap).
ℹ️ VAAPI enables GPU hardware acceleration (e.g., for video transcoding in Jellyfin or Plex).

➤ Automatically mount all available VAAPI devices? [Y/n]: y
✔️ Started LXC Container
✔️ Network in LXC is reachable (ping)
Extracting templates from packages: 100%
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.105 fd7c:7b69:eb40:ea48:be24:11ff:fe91:e2ad
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
✔️ Updated Container OS
✔️ Installed Dependencies
Do you need the intel-media-va-driver-non-free driver for HW encoding (Debian 12 only)? <y/N> n
✔️ Installed and Set Up Intel Hardware Acceleration
✔️ Installed ASP.NET Core Runtime
⠋ Setup FileFlowscurl: (7) Failed to connect to fileflows.com port 443 after 0 ms: Couldn't connect to server

[ERROR] in line 58: exit code 0: while executing command curl -fsSL https://fileflows.com/downloads/zip -o "$temp_file"
⠙ Setup FileFlows
[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

Paste the full error output (if available).

` Setup FileFlows'/usr/local/bin/ffmpeg' -> '/usr/bin/ffmpeg'
'/usr/local/bin/ffprobe' -> '/usr/bin/ffprobe'
curl: (7) Failed to connect to fileflows.com port 443 after 0 ms: Couldn't connect to server

[ERROR] in line 58: exit code 0: while executing command curl -fsSL https://fileflows.com/downloads/zip -o "$temp_file"

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"`

🖼️ Additional context (optional).

No response

Originally created by @Waylikemark on GitHub (Sep 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? FileFlows ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/fileflows.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.9/117b893e0e6a4fee (running kernel: 6.14.11-1-pve) ### 📝 Provide a clear and concise description of the issue. When trying to install the FileFlows script on PVE this results in an error (see below). Every step runs just fine up until it will install FileFlows itself then it runs into an error. Tested with both default settings and advanced settings both are not working. Also tried Unprivileged vs privileged and different storage options. The script seems to fail when connecting to FileFlows.com. Pinging to fileflows.com from any device (including the PVE node) is possible. The PVE node is not connected to any pi-hole or something similar in case it should be relevant. PVE's DNS server is configured to 1.1.1.1 and 8.8.8.8. ### 🔄 Steps to reproduce the issue. run: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/fileflows.sh)" on PVE shell. Either choose default settings or below advanced settings (which are basically default settings but without tags) to reproduce the error. _______ __ ________ / ____(_) /__ / ____/ /___ _ _______ / /_ / / / _ \/ /_ / / __ \ | /| / / ___/ / __/ / / / __/ __/ / / /_/ / |/ |/ (__ ) /_/ /_/_/\___/_/ /_/\____/|__/|__/____/ 🧩 Using Advanced Settings on node martines 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 120 🏠 Hostname: fileflows 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IPv4: DHCP 📡 IPv6: SLAAC/AUTO 📡 APT-Cacher IP Address: Default ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: ; 🔑 Root SSH Access: yes 🗂️ Enable FUSE Support: yes 🔍 Verbose Mode: no 🚀 Creating a FileFlows LXC using the above advanced settings ✔️ Storage local (Free: 79.2GB Used: 7.9GB) [Template] ✔️ Storage local-lvm (Free: 750.7GB Used: 25.1GB) [Container] ✔️ Template debian-12-standard_12.7-1_amd64.tar.zst [local] ✔️ LXC Container 120 was successfully created. ⚙️ Configuring VAAPI passthrough for LXC container ⚠️ Container is unprivileged – VAAPI passthrough may not work without additional host configuration (e.g., idmap). ℹ️ VAAPI enables GPU hardware acceleration (e.g., for video transcoding in Jellyfin or Plex). ➤ Automatically mount all available VAAPI devices? [Y/n]: y ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) Extracting templates from packages: 100% ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.105 fd7c:7b69:eb40:ea48:be24:11ff:fe91:e2ad ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Dependencies Do you need the intel-media-va-driver-non-free driver for HW encoding (Debian 12 only)? <y/N> n ✔️ Installed and Set Up Intel Hardware Acceleration ✔️ Installed ASP.NET Core Runtime ⠋ Setup FileFlowscurl: (7) Failed to connect to fileflows.com port 443 after 0 ms: Couldn't connect to server [ERROR] in line 58: exit code 0: while executing command curl -fsSL https://fileflows.com/downloads/zip -o "$temp_file" ⠙ Setup FileFlows [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### ❌ Paste the full error output (if available). ` ⏳ Setup FileFlows'/usr/local/bin/ffmpeg' -> '/usr/bin/ffmpeg' '/usr/local/bin/ffprobe' -> '/usr/bin/ffprobe' curl: (7) Failed to connect to fileflows.com port 443 after 0 ms: Couldn't connect to server [ERROR] in line 58: exit code 0: while executing command curl -fsSL https://fileflows.com/downloads/zip -o "$temp_file" [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:19:20 -05:00
Author
Owner

@MickLesk commented on GitHub (Sep 12, 2025):

Working fine Here. Did you have an AdBlock ? Your lxc could Not connect to fileflows

@MickLesk commented on GitHub (Sep 12, 2025): Working fine Here. Did you have an AdBlock ? Your lxc could Not connect to fileflows
Author
Owner

@Waylikemark commented on GitHub (Sep 12, 2025):

Working fine Here. Did you have an AdBlock ? Your lxc could Not connect to fileflows

I do have pi-hole but my PVE is not connected to it. When i run wget -O FileFlows.zip https://fileflows.com/downloads/zip in the LXC it refuses the connection but when in run in the shell of the PVE host it runs just fine.

@Waylikemark commented on GitHub (Sep 12, 2025): > Working fine Here. Did you have an AdBlock ? Your lxc could Not connect to fileflows I do have pi-hole but my PVE is not connected to it. When i run wget -O FileFlows.zip https://fileflows.com/downloads/zip in the LXC it refuses the connection but when in run in the shell of the PVE host it runs just fine.
Author
Owner

@Waylikemark commented on GitHub (Sep 12, 2025):

Solved. I changed the DNS setting in the script manually and now it works.

@Waylikemark commented on GitHub (Sep 12, 2025): Solved. I changed the DNS setting in the script manually and now it works.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1890