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

New Apache CouchDB with debian 13 fails #2317

New Issue
Closed
opened 2026-02-05 04:28:34 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 04:28:34 +03:00
Owner
Copy Link

Originally created by @NorbertHD on GitHub (Jan 13, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

Apache CouchDB

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

"curl: (22) The requested URL returned error: 404" error when executing install script.
The access URL (http://192.168.178.119:5984/_utils/) shown by the script doesn't work, no connection.
Auto login at the console doesn't work, login prompt is shown, but my host credentials don't work.

🔄 Steps to reproduce the issue.

Step1: execute install script

❌ Paste the full error output (if available).

🧩 Using Advanced Install on node pve

💡 PVE Version 9.1.4 (Kernel: 6.17.4-2-pve)
🖥️ Operating System: debian
🌟 Version: 13
📦 Container Type: Unprivileged
🆔 Container ID: 105
🏠 Hostname: apachecouchdb
💾 Disk Size: 10 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 4096 MiB
🌉 Bridge: vmbr0
📡 IPv4: dhcp
📡 IPv6: auto
🗂️ FUSE Support: no
📦 Nesting: Enabled
🎮 GPU Passthrough: no
💡 Timezone: Europe/Berlin
🔍 Verbose Mode: yes
🚀 Creating a Apache CouchDB LXC using the above advanced settings
✔️ Updated app defaults: /usr/local/community-scripts/defaults/apachecouchdb.vars
✔️ Storage local (Free: 79,6GB Used: 9,6GB) [Template]
✔️ Storage local-lvm (Free: 724,9GB Used: 69,5GB) [Container]
✔️ Storage 'local-lvm' (lvmthin) validated
✔️ Template storage 'local' validated
✔️ Template search completed
✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local]
✔️ LXC Container 105 was successfully created.
✔️ Started LXC Container
✔️ Network in LXC is reachable (ping)
✔️ Customized LXC Container
curl: (22) The requested URL returned error: 404
✔️ Completed successfully!

🚀 Apache CouchDB setup has been successfully initialized!
💡 Access it using the following URL:
🌐 http://192.168.178.119:5984/_utils/

🖼️ Additional context (optional).

No response

Originally created by @NorbertHD on GitHub (Jan 13, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Apache CouchDB ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/apache-couchdb.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. "curl: (22) The requested URL returned error: 404" error when executing install script. The access URL (http://192.168.178.119:5984/_utils/) shown by the script doesn't work, no connection. Auto login at the console doesn't work, login prompt is shown, but my host credentials don't work. ### 🔄 Steps to reproduce the issue. Step1: execute install script ### ❌ Paste the full error output (if available). 🧩 Using Advanced Install on node pve 💡 PVE Version 9.1.4 (Kernel: 6.17.4-2-pve) 🖥️ Operating System: debian 🌟 Version: 13 📦 Container Type: Unprivileged 🆔 Container ID: 105 🏠 Hostname: apachecouchdb 💾 Disk Size: 10 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 4096 MiB 🌉 Bridge: vmbr0 📡 IPv4: dhcp 📡 IPv6: auto 🗂️ FUSE Support: no 📦 Nesting: Enabled 🎮 GPU Passthrough: no 💡 Timezone: Europe/Berlin 🔍 Verbose Mode: yes 🚀 Creating a Apache CouchDB LXC using the above advanced settings ✔️ Updated app defaults: /usr/local/community-scripts/defaults/apachecouchdb.vars ✔️ Storage local (Free: 79,6GB Used: 9,6GB) [Template] ✔️ Storage local-lvm (Free: 724,9GB Used: 69,5GB) [Container] ✔️ Storage 'local-lvm' (lvmthin) validated ✔️ Template storage 'local' validated ✔️ Template search completed ✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local] ✔️ LXC Container 105 was successfully created. ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) ✔️ Customized LXC Container curl: (22) The requested URL returned error: 404 ✔️ Completed successfully! 🚀 Apache CouchDB setup has been successfully initialized! 💡 Access it using the following URL: 🌐 http://192.168.178.119:5984/_utils/ ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:28:34 +03:00
OVERLORD commented 2026-02-05 04:28:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 13, 2026):

fixed, just a typo

@MickLesk commented on GitHub (Jan 13, 2026): fixed, just a typo
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#2317
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?