starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

Paperless-NGX: No network connection but ping okay #636

New Issue
Closed
opened 2026-02-04 20:28:57 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-04 20:28:57 +03:00
Owner
Copy Link

Originally created by @e-tplus on GitHub (Mar 14, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Paperless-ngx LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/paperless-ngx.sh)"

📝 Provide a clear and concise description of the issue.

When I try to install Paperless-ngx, the script takes about 5 -6 hours. At the end I get "No network after 10 tries":

When I try to access the GUI at IP:8000, there is nothing. I can ping the IP and access the console. That's IP a:

root@paperless-ngx:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether bc:24:11:b4:37:ae brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.1.134/24 brd 192.168.1.255 scope global dynamic eth0 valid_lft 862622sec preferred_lft 862622sec root@paperless-ngx:~#

Proxmox shows no CPU use.

Tried 3 times, any ideas? Thanks for some help.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Install and wait.

❌ Paste the full error output (if available).

🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Privileged 🔐 Root Password: ******** 🆔 Container ID: 106 🏠 Hostname: paperless-ngx 💾 Disk Size: 20 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: yes ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;document;management 🔑 Root SSH Access: yes 🔍 Verbose Mode: no 🚀 Creating a Paperless-ngx LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using ext_hdd for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 106 was successfully created. ✔️ Started LXC Container ⠼ ✖️ No Network! ner OS ✖️ No Network After 10 Tries 📡 Check Network Settings

🖼️ Additional context (optional).

No response

Originally created by @e-tplus on GitHub (Mar 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Paperless-ngx LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/paperless-ngx.sh)" ### 📝 Provide a clear and concise description of the issue. When I try to install Paperless-ngx, the script takes about 5 -6 hours. At the end I get "No network after 10 tries": When I try to access the GUI at IP:8000, there is nothing. I can ping the IP and access the console. That's IP a: `root@paperless-ngx:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether bc:24:11:b4:37:ae brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.1.134/24 brd 192.168.1.255 scope global dynamic eth0 valid_lft 862622sec preferred_lft 862622sec root@paperless-ngx:~# ` Proxmox shows no CPU use. Tried 3 times, any ideas? Thanks for some help. ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Install and wait. ### ❌ Paste the full error output (if available). ` 🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Privileged 🔐 Root Password: ******** 🆔 Container ID: 106 🏠 Hostname: paperless-ngx 💾 Disk Size: 20 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: yes ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;document;management 🔑 Root SSH Access: yes 🔍 Verbose Mode: no 🚀 Creating a Paperless-ngx LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using ext_hdd for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 106 was successfully created. ✔️ Started LXC Container ⠼ ✖️ No Network! ner OS ✖️ No Network After 10 Tries 📡 Check Network Settings` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 20:28:57 +03:00
OVERLORD commented 2026-02-04 20:29:10 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 14, 2025):

Your container cant reach Network over DNS. Its not an Script issue. You need to try it on your lxc, not on main node

network_check() {
  set +e
  trap - ERR
  ipv4_connected=false
  ipv6_connected=false
  sleep 1
  # Check IPv4 connectivity to Google, Cloudflare & Quad9 DNS servers.
  if ping -c 1 -W 1 1.1.1.1 &>/dev/null || ping -c 1 -W 1 8.8.8.8 &>/dev/null || ping -c 1 -W 1 9.9.9.9 &>/dev/null; then
    msg_ok "IPv4 Internet Connected"
    ipv4_connected=true
  else
    msg_error "IPv4 Internet Not Connected"
  fi

  # Check IPv6 connectivity to Google, Cloudflare & Quad9 DNS servers.
  if ping6 -c 1 -W 1 2606:4700:4700::1111 &>/dev/null || ping6 -c 1 -W 1 2001:4860:4860::8888 &>/dev/null || ping6 -c 1 -W 1 2620:fe::fe &>/dev/null; then
    msg_ok "IPv6 Internet Connected"
    ipv6_connected=true
  else
    msg_error "IPv6 Internet Not Connected"
  fi

  # If both IPv4 and IPv6 checks fail, prompt the user
  if [[ $ipv4_connected == false && $ipv6_connected == false ]]; then
    read -r -p "No Internet detected,would you like to continue anyway? <y/N> " prompt
    if [[ "${prompt,,}" =~ ^(y|yes)$ ]]; then
      echo -e "${INFO}${RD}Expect Issues Without Internet${CL}"
    else
      echo -e "${NETWORK}Check Network Settings"
      exit 1
    fi
  fi
@MickLesk commented on GitHub (Mar 14, 2025): Your container cant reach Network over DNS. Its not an Script issue. You need to try it on your lxc, not on main node ```bash network_check() { set +e trap - ERR ipv4_connected=false ipv6_connected=false sleep 1 # Check IPv4 connectivity to Google, Cloudflare & Quad9 DNS servers. if ping -c 1 -W 1 1.1.1.1 &>/dev/null || ping -c 1 -W 1 8.8.8.8 &>/dev/null || ping -c 1 -W 1 9.9.9.9 &>/dev/null; then msg_ok "IPv4 Internet Connected" ipv4_connected=true else msg_error "IPv4 Internet Not Connected" fi # Check IPv6 connectivity to Google, Cloudflare & Quad9 DNS servers. if ping6 -c 1 -W 1 2606:4700:4700::1111 &>/dev/null || ping6 -c 1 -W 1 2001:4860:4860::8888 &>/dev/null || ping6 -c 1 -W 1 2620:fe::fe &>/dev/null; then msg_ok "IPv6 Internet Connected" ipv6_connected=true else msg_error "IPv6 Internet Not Connected" fi # If both IPv4 and IPv6 checks fail, prompt the user if [[ $ipv4_connected == false && $ipv6_connected == false ]]; then read -r -p "No Internet detected,would you like to continue anyway? <y/N> " prompt if [[ "${prompt,,}" =~ ^(y|yes)$ ]]; then echo -e "${INFO}${RD}Expect Issues Without Internet${CL}" else echo -e "${NETWORK}Check Network Settings" exit 1 fi fi ```
OVERLORD commented 2026-02-04 20:29:16 +03:00
Author
Owner
Copy Link

@e-tplus commented on GitHub (Mar 14, 2025):

I run pihole (with unbound) in another container. It's IP is correctly entered in resolv.conf.

When I ping e. g. google.com or 1.1.1.1 from the Paperless console it's resolved fine.

@e-tplus commented on GitHub (Mar 14, 2025): I run pihole (with unbound) in another container. It's IP is correctly entered in resolv.conf. When I ping e. g. google.com or 1.1.1.1 from the Paperless console it's resolved fine.
OVERLORD commented 2026-02-04 20:29:19 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 14, 2025):

Then try to disable all and try again, we have 6 Checks. All failed. Unfortunately, we can't do any more magic.

@MickLesk commented on GitHub (Mar 14, 2025): Then try to disable all and try again, we have 6 Checks. All failed. Unfortunately, we can't do any more magic.
OVERLORD commented 2026-02-04 20:29:21 +03:00
Author
Owner
Copy Link

@e-tplus commented on GitHub (Mar 14, 2025):

What should I disable? I tried all default settings with the same result.

@e-tplus commented on GitHub (Mar 14, 2025): What should I disable? I tried all default settings with the same result.
OVERLORD commented 2026-02-04 20:29:24 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 14, 2025):

Your DNS / AdBlock

@MickLesk commented on GitHub (Mar 14, 2025): Your DNS / AdBlock
OVERLORD commented 2026-02-04 20:29:33 +03:00
Author
Owner
Copy Link

@e-tplus commented on GitHub (Mar 15, 2025):

Is it normal that the installation takes about 6 hours?

@e-tplus commented on GitHub (Mar 15, 2025): Is it normal that the installation takes about 6 hours?
OVERLORD commented 2026-02-04 20:29:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 15, 2025):

No. Takes max. 10-15min

@MickLesk commented on GitHub (Mar 15, 2025): No. Takes max. 10-15min
OVERLORD commented 2026-02-04 20:29:44 +03:00
Author
Owner
Copy Link

@e-tplus commented on GitHub (Mar 15, 2025):

So it takes that long due to failed communication tests?

@e-tplus commented on GitHub (Mar 15, 2025): So it takes that long due to failed communication tests?
OVERLORD commented 2026-02-04 20:29:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 15, 2025):

Maybe. Try without any DNS AdBlock or something. We cant do anymore

@MickLesk commented on GitHub (Mar 15, 2025): Maybe. Try without any DNS AdBlock or something. We cant do anymore
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#636
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?