[GH-ISSUE #8804] Homarr installation failed

kerem commented

2026-02-26 12:50:38 +03:00

Owner

Originally created by @htrungngx on GitHub (Nov 1, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/8804

Originally assigned to: @CrazyWolf13 on GitHub.

✅ Have you read and understood the above guidelines?

yes

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

Homarr

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

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

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

Proxmox 9

📝 Provide a clear and concise description of the issue.

The root symptom might be (connect ECONNREFUSED 127.0.1.1:443) there’s an attempt to connect to 127.0.1.1 explicitly and nothing is listening on 443

🔄 Steps to reproduce the issue.

Run Homarr script with default mode

❌ Paste the full error output (if available).

Progress: resolved 0, reused 0, downloaded 1937, added 3113, done
node_modules/cpu-features: Running install script, done in 4.3s
node_modules/esbuild: Running postinstall script, done in 93ms
node_modules/sharp: Running install script, done in 133ms
node_modules/tree-sitter: Running install script, done in 119ms
node_modules/@swagger-api/apidom-parser-adapter-yaml-1-2/node_modules/tree-sitter: Running install script, done in 152ms
node_modules/better-sqlite3: Running install script, done in 786ms
node_modules/bcrypt: Running install script, done in 101ms
node_modules/ssh2: Running install script, done in 2.3s
node_modules/@tree-sitter-grammars/tree-sitter-yaml: Running install script, done in 85ms
node_modules/tree-sitter-json: Running install script, done in 87ms
packages/definitions postinstall$ tsx ./src/docs/codegen.ts
│ node:internal/deps/undici/undici:14900
│       Error.captureStackTrace(err);
│             ^
│ TypeError: fetch failed
│     at node:internal/deps/undici/undici:14900:13
│     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
│     at async fetchSitemapAsync (/opt/homarr/packages/definitions/src/docs/codegen.ts:27:20)
│     at async main (/opt/homarr/packages/definitions/src/docs/codegen.ts:66:22) {
│   [cause]: Error: connect ECONNREFUSED 127.0.1.1:443
│       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
│     errno: -111,
│     code: 'ECONNREFUSED',
│     syscall: 'connect',
│     address: '127.0.1.1',
│     port: 443
│   }
│ }
│ Node.js v22.21.0
└─ Failed in 479ms at /opt/homarr/packages/definitions
 ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 49: exit code 0: while executing command $STD pnpm install --recursive --frozen-lockfile --shamefully-hoist

[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 @htrungngx on GitHub (Nov 1, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/8804 Originally assigned to: @CrazyWolf13 on GitHub. ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Homarr ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homarr.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? Proxmox 9 ### 📝 Provide a clear and concise description of the issue. The root symptom might be (connect ECONNREFUSED 127.0.1.1:443) there’s an attempt to connect to 127.0.1.1 explicitly and nothing is listening on 443 ### 🔄 Steps to reproduce the issue. Run Homarr script with default mode ### ❌ Paste the full error output (if available). ``` Progress: resolved 0, reused 0, downloaded 1937, added 3113, done node_modules/cpu-features: Running install script, done in 4.3s node_modules/esbuild: Running postinstall script, done in 93ms node_modules/sharp: Running install script, done in 133ms node_modules/tree-sitter: Running install script, done in 119ms node_modules/@swagger-api/apidom-parser-adapter-yaml-1-2/node_modules/tree-sitter: Running install script, done in 152ms node_modules/better-sqlite3: Running install script, done in 786ms node_modules/bcrypt: Running install script, done in 101ms node_modules/ssh2: Running install script, done in 2.3s node_modules/@tree-sitter-grammars/tree-sitter-yaml: Running install script, done in 85ms node_modules/tree-sitter-json: Running install script, done in 87ms packages/definitions postinstall$ tsx ./src/docs/codegen.ts │ node:internal/deps/undici/undici:14900 │ Error.captureStackTrace(err); │ ^ │ TypeError: fetch failed │ at node:internal/deps/undici/undici:14900:13 │ at process.processTicksAndRejections (node:internal/process/task_queues:105:5) │ at async fetchSitemapAsync (/opt/homarr/packages/definitions/src/docs/codegen.ts:27:20) │ at async main (/opt/homarr/packages/definitions/src/docs/codegen.ts:66:22) { │ [cause]: Error: connect ECONNREFUSED 127.0.1.1:443 │ at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) { │ errno: -111, │ code: 'ECONNREFUSED', │ syscall: 'connect', │ address: '127.0.1.1', │ port: 443 │ } │ } │ Node.js v22.21.0 └─ Failed in 479ms at /opt/homarr/packages/definitions ELIFECYCLE Command failed with exit code 1. [ERROR] in line 49: exit code 0: while executing command $STD pnpm install --recursive --frozen-lockfile --shamefully-hoist [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_

kerem

2026-02-26 12:50:38 +03:00

closed this issue
added the
not a script issue
label

kerem commented

2026-02-26 12:50:38 +03:00

Author

Owner

@CrazyWolf13 commented on GitHub (Nov 1, 2025):

Hi, unsure why it's doing this, I've just run the homarr installation and update without issues, I'd suggest re-trying the installation, maybe it was termporary issue, also try with more ressources via advanced if you have older Hardware.

@CrazyWolf13 commented on GitHub (Nov 1, 2025): Hi, unsure why it's doing this, I've just run the homarr installation and update without issues, I'd suggest re-trying the installation, maybe it was termporary issue, also try with more ressources via advanced if you have older Hardware.

kerem commented

2026-02-26 12:50:38 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

Hi, unsure why it's doing this, I've just run the homarr installation and update without issues, I'd suggest re-trying the installation, maybe it was termporary issue, also try with more ressources via advanced if you have older Hardware.

strange to me as well,

I don't think hardware is smth should I concern because currently my setup is G3 Plus from GMK with 16 RAM so It should work well. Retried installation many times. Im curious that can I do script but point to older Homarr version ?

@htrungngx commented on GitHub (Nov 2, 2025): > Hi, unsure why it's doing this, I've just run the homarr installation and update without issues, I'd suggest re-trying the installation, maybe it was termporary issue, also try with more ressources via advanced if you have older Hardware. strange to me as well, I don't think hardware is smth should I concern because currently my setup is G3 Plus from GMK with 16 RAM so It should work well. Retried installation many times. Im curious that can I do script but point to older Homarr version ?

kerem commented

2026-02-26 12:50:38 +03:00

Author

Owner

@CrazyWolf13 commented on GitHub (Nov 2, 2025):

@htrungngx that seems very weird indeed.

Can you share the full log when running via advanced mode and enable verbose?

@CrazyWolf13 commented on GitHub (Nov 2, 2025): @htrungngx that seems very weird indeed. Can you share the full log when running via advanced mode and enable verbose?

kerem commented

2026-02-26 12:50:38 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

  🧩  Using Advanced Settings on node htrung
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  🔐  Root Password: ********
  🆔  Container ID: 104
  🏠  Hostname: homarr
  💾  Disk Size: 8 GB
  🧠  CPU Cores: 3
  🛠️  RAM Size: 6144 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: community-script;arr;dashboard
  🔑  Root SSH Access: no
  🗂️  Enable FUSE Support: no
  🔍  Verbose Mode: yes
  🚀  Creating a homarr LXC using the above advanced settings
  💡  Configuration file already exists at /opt/community-scripts/homarr.conf
  💡  Writing configuration to /opt/community-scripts/homarr.conf
  ✔️   Storage local (Free: 82.4GB  Used: 4.7GB) [Template]
  ✔️   Storage local-lvm (Free: 335.1GB  Used: 4.7GB) [Container]
  ✔️   Template debian-12-standard_12.12-1_amd64.tar.zst [local]
  ✔️   LXC Container 104 was successfully created.
  ✔️   Started LXC Container
   💡   No network in LXC yet (try 1/10) – waiting...
  ✔️   Network in LXC is reachable (ping)
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 192.168.0.195 fdcc:92c0:854:114e:be24:11ff:fef3:d5d5 
  ✔️   IPv4 Internet Connected
   ✖️   IPv6 Internet Not Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )

...

1 package is looking for funding
  run `npm fund` for details
  ✔️   Installed Node.js modules: pnpm@10.19.0
  ✔️   Deployed: homarr (1.43.1)
  ⏳   Installing Homarr (Patience)Scope: all 44 workspace projects
Lockfile is up to date, resolution step is skipped
.                                        |    +3113 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

   ╭──────────────────────────────────────────╮
   │                                          │
   │   Update available! 10.19.0 → 10.20.0.   │
   │   Changelog: https://pnpm.io/v/10.20.0   │
   │     To update, run: pnpm add -g pnpm     │
   │                                          │
   ╰──────────────────────────────────────────╯

Downloading turbo-linux-64@2.5.8: 14.33 MB/14.33 MB, done
Downloading next@15.5.6: 30.31 MB/30.31 MB, done
Downloading @img/sharp-libvips-linux-x64@1.2.0: 7.42 MB/7.42 MB, done
Downloading @img/sharp-libvips-linuxmusl-x64@1.2.0: 7.54 MB/7.54 MB, done
Downloading @next/swc-linux-x64-musl@15.5.6: 47.31 MB/47.31 MB, done
Downloading @next/swc-linux-x64-gnu@15.5.6: 47.36 MB/47.36 MB, done
Progress: resolved 0, reused 0, downloaded 1937, added 3113, done
node_modules/cpu-features: Running install script, done in 4.7s
node_modules/esbuild: Running postinstall script, done in 99ms
node_modules/sharp: Running install script, done in 134ms
node_modules/tree-sitter: Running install script, done in 146ms
node_modules/@swagger-api/apidom-parser-adapter-yaml-1-2/node_modules/tree-sitter: Running install script, done in 130ms
node_modules/better-sqlite3: Running install script, done in 675ms
node_modules/bcrypt: Running install script, done in 95ms
node_modules/ssh2: Running install script, done in 2.3s
node_modules/@tree-sitter-grammars/tree-sitter-yaml: Running install script, done in 87ms
node_modules/tree-sitter-json: Running install script, done in 91ms
packages/definitions postinstall$ tsx ./src/docs/codegen.ts
│ node:internal/deps/undici/undici:14900
│       Error.captureStackTrace(err);
│             ^
│ TypeError: fetch failed
│     at node:internal/deps/undici/undici:14900:13
│     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
│     at async fetchSitemapAsync (/opt/homarr/packages/definitions/src/docs/codegen.ts:27:20)
│     at async main (/opt/homarr/packages/definitions/src/docs/codegen.ts:66:22) {
│   [cause]: Error: connect ECONNREFUSED 127.0.1.1:443
│       at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
│     errno: -111,
│     code: 'ECONNREFUSED',
│     syscall: 'connect',
│     address: '127.0.1.1',
│     port: 443
│   }
│ }
│ Node.js v22.21.0
└─ Failed in 485ms at /opt/homarr/packages/definitions
 ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 49: exit code 0: while executing command $STD pnpm install --recursive --frozen-lockfile --shamefully-hoist

[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)"

@CrazyWolf13 Still same output as above,

@htrungngx commented on GitHub (Nov 2, 2025): ``` 🧩 Using Advanced Settings on node htrung 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 104 🏠 Hostname: homarr 💾 Disk Size: 8 GB 🧠 CPU Cores: 3 🛠️ RAM Size: 6144 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: community-script;arr;dashboard 🔑 Root SSH Access: no 🗂️ Enable FUSE Support: no 🔍 Verbose Mode: yes 🚀 Creating a homarr LXC using the above advanced settings 💡 Configuration file already exists at /opt/community-scripts/homarr.conf 💡 Writing configuration to /opt/community-scripts/homarr.conf ✔️ Storage local (Free: 82.4GB Used: 4.7GB) [Template] ✔️ Storage local-lvm (Free: 335.1GB Used: 4.7GB) [Container] ✔️ Template debian-12-standard_12.12-1_amd64.tar.zst [local] ✔️ LXC Container 104 was successfully created. ✔️ Started LXC Container 💡 No network in LXC yet (try 1/10) – waiting... ✔️ Network in LXC is reachable (ping) ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.0.195 fdcc:92c0:854:114e:be24:11ff:fef3:d5d5 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ... 1 package is looking for funding run `npm fund` for details ✔️ Installed Node.js modules: pnpm@10.19.0 ✔️ Deployed: homarr (1.43.1) ⏳ Installing Homarr (Patience)Scope: all 44 workspace projects Lockfile is up to date, resolution step is skipped . | +3113 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ╭──────────────────────────────────────────╮ │ │ │ Update available! 10.19.0 → 10.20.0. │ │ Changelog: https://pnpm.io/v/10.20.0 │ │ To update, run: pnpm add -g pnpm │ │ │ ╰──────────────────────────────────────────╯ Downloading turbo-linux-64@2.5.8: 14.33 MB/14.33 MB, done Downloading next@15.5.6: 30.31 MB/30.31 MB, done Downloading @img/sharp-libvips-linux-x64@1.2.0: 7.42 MB/7.42 MB, done Downloading @img/sharp-libvips-linuxmusl-x64@1.2.0: 7.54 MB/7.54 MB, done Downloading @next/swc-linux-x64-musl@15.5.6: 47.31 MB/47.31 MB, done Downloading @next/swc-linux-x64-gnu@15.5.6: 47.36 MB/47.36 MB, done Progress: resolved 0, reused 0, downloaded 1937, added 3113, done node_modules/cpu-features: Running install script, done in 4.7s node_modules/esbuild: Running postinstall script, done in 99ms node_modules/sharp: Running install script, done in 134ms node_modules/tree-sitter: Running install script, done in 146ms node_modules/@swagger-api/apidom-parser-adapter-yaml-1-2/node_modules/tree-sitter: Running install script, done in 130ms node_modules/better-sqlite3: Running install script, done in 675ms node_modules/bcrypt: Running install script, done in 95ms node_modules/ssh2: Running install script, done in 2.3s node_modules/@tree-sitter-grammars/tree-sitter-yaml: Running install script, done in 87ms node_modules/tree-sitter-json: Running install script, done in 91ms packages/definitions postinstall$ tsx ./src/docs/codegen.ts │ node:internal/deps/undici/undici:14900 │ Error.captureStackTrace(err); │ ^ │ TypeError: fetch failed │ at node:internal/deps/undici/undici:14900:13 │ at process.processTicksAndRejections (node:internal/process/task_queues:105:5) │ at async fetchSitemapAsync (/opt/homarr/packages/definitions/src/docs/codegen.ts:27:20) │ at async main (/opt/homarr/packages/definitions/src/docs/codegen.ts:66:22) { │ [cause]: Error: connect ECONNREFUSED 127.0.1.1:443 │ at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) { │ errno: -111, │ code: 'ECONNREFUSED', │ syscall: 'connect', │ address: '127.0.1.1', │ port: 443 │ } │ } │ Node.js v22.21.0 └─ Failed in 485ms at /opt/homarr/packages/definitions ELIFECYCLE Command failed with exit code 1. [ERROR] in line 49: exit code 0: while executing command $STD pnpm install --recursive --frozen-lockfile --shamefully-hoist [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)" ``` @CrazyWolf13 Still same output as above,

kerem commented

2026-02-26 12:50:38 +03:00

Author

Owner

@CrazyWolf13 commented on GitHub (Nov 2, 2025):

@htrungngx I've informed the homarr team (@Meierschlumpf and @manuel-rw ), maybe they have an idea why it's failing here.

I'm still unable to recreate this issue though.

In the meantime can you try running in default (Verbose) to ensure no special configuration from you may break anything here.
Also can you try running the following inside a homarr installation after it failed:

cd /opt/homarr
pnpm tsx packages/definitions/src/docs/codegen.ts

@CrazyWolf13 commented on GitHub (Nov 2, 2025): @htrungngx I've informed the homarr team (@Meierschlumpf and @manuel-rw ), maybe they have an idea why it's failing here. I'm still unable to recreate this issue though. In the meantime can you try running in default (Verbose) to ensure no special configuration from you may break anything here. Also can you try running the following inside a homarr installation after it failed: ```bash cd /opt/homarr pnpm tsx packages/definitions/src/docs/codegen.ts ```

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

root@homarr:/opt/homarr# pnpm tsx packages/definitions/src/docs/codegen.ts
node:internal/deps/undici/undici:14900
      Error.captureStackTrace(err);
            ^

TypeError: fetch failed
    at node:internal/deps/undici/undici:14900:13
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async fetchSitemapAsync (/opt/homarr/packages/definitions/src/docs/codegen.ts:27:20)
    at async main (/opt/homarr/packages/definitions/src/docs/codegen.ts:66:22) {
  [cause]: Error: connect ECONNREFUSED 127.0.1.1:443
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '127.0.1.1',
    port: 443
  }
}

Node.js v22.21.0

seems better but how to reinstall on same lxc ?

@htrungngx commented on GitHub (Nov 2, 2025): ``` root@homarr:/opt/homarr# pnpm tsx packages/definitions/src/docs/codegen.ts node:internal/deps/undici/undici:14900 Error.captureStackTrace(err); ^ TypeError: fetch failed at node:internal/deps/undici/undici:14900:13 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async fetchSitemapAsync (/opt/homarr/packages/definitions/src/docs/codegen.ts:27:20) at async main (/opt/homarr/packages/definitions/src/docs/codegen.ts:66:22) { [cause]: Error: connect ECONNREFUSED 127.0.1.1:443 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '127.0.1.1', port: 443 } } Node.js v22.21.0 ``` seems better but how to reinstall on same lxc ?

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Meierschlumpf commented on GitHub (Nov 2, 2025):

It's very weird that you get a econnrefused for localhost, because the only thing that happens in the codegen file is, that we fetch the https://homarr.dev sitemap to generate some types

@Meierschlumpf commented on GitHub (Nov 2, 2025): It's very weird that you get a econnrefused for localhost, because the only thing that happens in the codegen file is, that we fetch the https://homarr.dev sitemap to generate some types

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Meierschlumpf commented on GitHub (Nov 2, 2025):

Do you have some proxy env variables set? Like HTTP_PROXY or HTTPS_PROXY?

@Meierschlumpf commented on GitHub (Nov 2, 2025): Do you have some proxy env variables set? Like HTTP_PROXY or HTTPS_PROXY?

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@CrazyWolf13 commented on GitHub (Nov 2, 2025):

Do you use apt-cacher proxy in some way?
I think I saw that above?

@CrazyWolf13 commented on GitHub (Nov 2, 2025): Do you use apt-cacher proxy in some way? I think I saw that above?

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

hmm, i did not setup anything relates about proxy(s) checked all envs

@htrungngx commented on GitHub (Nov 2, 2025): hmm, i did not setup anything relates about proxy(s) checked all envs

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Meierschlumpf commented on GitHub (Nov 2, 2025):

Can you check what happens when you make a curl request? curl https://homarr.dev/sitemap.xml

@Meierschlumpf commented on GitHub (Nov 2, 2025): Can you check what happens when you make a curl request? `curl https://homarr.dev/sitemap.xml`

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

root@homarr:/opt/homarr# curl https://homarr.dev/sitemap.xml
curl: (7) Failed to connect to homarr.dev port 443 after 0 ms: Couldn't connect to server

@htrungngx commented on GitHub (Nov 2, 2025): ``` root@homarr:/opt/homarr# curl https://homarr.dev/sitemap.xml curl: (7) Failed to connect to homarr.dev port 443 after 0 ms: Couldn't connect to server ```

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@manuel-rw commented on GitHub (Nov 2, 2025):

Sounds like either firewall or misconfigured network adapter to me?
Can you also make sure that your firewall is blocking none of these requests?

@manuel-rw commented on GitHub (Nov 2, 2025): Sounds like either firewall or misconfigured network adapter to me? Can you also make sure that your firewall is blocking none of these requests?

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

I did not have any firewall config, only assign dns

root@homarr:~# env | grep -i proxy
cat /etc/resolv.conf
nameserver 9.9.9.9
nameserver 192.168.0.50 (adguard home)

@htrungngx commented on GitHub (Nov 2, 2025): I did not have any firewall config, only assign dns ``` root@homarr:~# env | grep -i proxy cat /etc/resolv.conf nameserver 9.9.9.9 nameserver 192.168.0.50 (adguard home) ```

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

root@homarr:/opt/homarr# curl https://homarr.dev/sitemap.xml
curl: (7) Failed to connect to homarr.dev port 443 after 0 ms: Couldn't connect to server

have an entry somewhere overriding homarr.dev → 127.0.1.1 so deleted it in /etc/hosts then able to curl again curl -4 https://homarr.dev/sitemap.xml

@htrungngx commented on GitHub (Nov 2, 2025): > root@homarr:/opt/homarr# curl https://homarr.dev/sitemap.xml curl: (7) Failed to connect to homarr.dev port 443 after 0 ms: Couldn't connect to server have an entry somewhere overriding homarr.dev → 127.0.1.1 so deleted it in /etc/hosts then able to curl again `curl -4 https://homarr.dev/sitemap.xml `

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Meierschlumpf commented on GitHub (Nov 2, 2025):

Okay so now it should work with the installation then

@Meierschlumpf commented on GitHub (Nov 2, 2025): Okay so now it should work with the installation then

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 2, 2025):

root@homarr:~# cat /etc/hosts
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters
# --- BEGIN PVE ---
127.0.1.1 homarr.dev homarr
# --- END PVE ---

this should not be correct, by default it auto adds this into /etc/host. default hostname is homarr then 127.0.1.1 homarr only

@htrungngx commented on GitHub (Nov 2, 2025): ``` root@homarr:~# cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # --- BEGIN PVE --- 127.0.1.1 homarr.dev homarr # --- END PVE --- ``` this should not be correct, by default it auto adds this into `/etc/host`. default hostname is homarr then `127.0.1.1 homarr` only

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Meierschlumpf commented on GitHub (Nov 2, 2025):

@CrazyWolf13 is this something you've added? Also shouldn't it be 127.0.0.1 instead of 127.0.1.1?

@Meierschlumpf commented on GitHub (Nov 2, 2025): @CrazyWolf13 is this something you've added? Also shouldn't it be `127.0.0.1` instead of `127.0.1.1`?

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@michelroegl-brunner commented on GitHub (Nov 2, 2025):

Should not matter if 127.0.0.1 or 127.0.1.1 as the whole 127.0.0.0/8 subnet is reserved for Link-local addressing

@michelroegl-brunner commented on GitHub (Nov 2, 2025): Should not matter if 127.0.0.1 or 127.0.1.1 as the whole 127.0.0.0/8 subnet is reserved for Link-local addressing

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@CrazyWolf13 commented on GitHub (Nov 2, 2025):

@Meierschlumpf Not we don't touch those files, this is inherited from the users node dns setup, which we also don't touch.

@htrungngx
By default proxmox seems to add an entry to the lxc looking like this:

Example from my container:

root@homarr:~# cat /etc/hosts
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters
# --- BEGIN PVE ---
10.10.20.21 homarr.home homarr
# --- END PVE ---

This part:

# --- BEGIN PVE ---
10.10.20.21 homarr.home homarr
# --- END PVE ---

Seems to reflect the following:

{LXC_IP}    {LXC_Hostname}.{DNS_Search_Domain}    {LXC_HOSTNAME}

You seem to have set dev as DNS search domain on your host, is that possible?

.dev is a LIVE TLD, I have no idea why you would set this as DNS search domain locally?
Here are some that you can use for local setups:

https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml

@CrazyWolf13 commented on GitHub (Nov 2, 2025): @Meierschlumpf Not we don't touch those files, this is inherited from the users node dns setup, which we also don't touch. @htrungngx By default proxmox seems to add an entry to the lxc looking like this: Example from my container: ```bash root@homarr:~# cat /etc/hosts 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters # --- BEGIN PVE --- 10.10.20.21 homarr.home homarr # --- END PVE --- ``` This part: ```bash # --- BEGIN PVE --- 10.10.20.21 homarr.home homarr # --- END PVE --- ``` Seems to reflect the following: ```bash {LXC_IP} {LXC_Hostname}.{DNS_Search_Domain} {LXC_HOSTNAME} ``` You seem to have set `dev` as DNS search domain on your host, is that possible? .dev is a LIVE TLD, I have no idea why you would set this as DNS search domain locally? Here are some that you can use for local setups: https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 3, 2025):

@CrazyWolf13 I will check my router setup again but other scripts work well except the Homarr one. changed the host and reinstalled manually solved the issue. But i think it's better to modify the logic here

@htrungngx commented on GitHub (Nov 3, 2025): @CrazyWolf13 I will check my router setup again but other scripts work well except the Homarr one. changed the host and reinstalled manually solved the issue. But i think it's better to modify the logic here

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 3, 2025):

My domain is ABC.dev and somehow it auto appends postfix into

@htrungngx commented on GitHub (Nov 3, 2025): My domain is ABC.dev and somehow it auto appends postfix into

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@htrungngx commented on GitHub (Nov 3, 2025):

But anw, thank you you guys, I will close this issue 👏🏻

@htrungngx commented on GitHub (Nov 3, 2025): But anw, thank you you guys, I will close this issue 👏🏻

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Lorondos commented on GitHub (Nov 22, 2025):

Hmm, this just happened to me now with the latest update, ran default update command to update to 1.44 from 1.43.3., have no custom config and broken. Not dug into it yet, was bad gateway at one point, done a reboot and now unable to connect. I will try some of troubleshooting steps here.

@Lorondos commented on GitHub (Nov 22, 2025): Hmm, this just happened to me now with the latest update, ran default update command to update to 1.44 from 1.43.3., have no custom config and broken. Not dug into it yet, was bad gateway at one point, done a reboot and now unable to connect. I will try some of troubleshooting steps here.

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@chicungunya commented on GitHub (Nov 30, 2025):

@Lorondos same! What did you do finally? Thanks!

@chicungunya commented on GitHub (Nov 30, 2025): @Lorondos same! What did you do finally? Thanks!

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@Lorondos commented on GitHub (Nov 30, 2025):

@Lorondos same! What did you do finally? Thanks!

I had to reinstall in the end, issue is the build/install process requires a large amount of RAM to not fail, 8GB+ to be exact, likely could of salvaged it at that point but gave up and reinstalled. Marked it with a note now to increase the RAM to 8GB for upgrades and create a snapshot before updating.

They are working on trying to bring it down in terms of memory it uses, might be that addresses the large amount required during the build/install process via pnpm.

@Lorondos commented on GitHub (Nov 30, 2025): > [@Lorondos](https://github.com/Lorondos) same! What did you do finally? Thanks! I had to reinstall in the end, issue is the build/install process requires a large amount of RAM to not fail, 8GB+ to be exact, likely could of salvaged it at that point but gave up and reinstalled. Marked it with a note now to increase the RAM to 8GB for upgrades and create a snapshot before updating. They are working on trying to bring it down in terms of memory it uses, might be that addresses the large amount required during the build/install process via pnpm.

kerem commented

2026-02-26 12:50:39 +03:00

Author

Owner

@manuel-rw commented on GitHub (Nov 30, 2025):

Correct, we are working on this and after the change, memory can be decreased to 1GB

@manuel-rw commented on GitHub (Nov 30, 2025): Correct, we are working on this and after the change, memory can be decreased to 1GB

kerem referenced this issue

2026-02-26 13:33:57 +03:00

[PR #2148] [MERGED] Fix: Trillium Update Function & Harmonize Installation #3570

kerem referenced this issue

2026-02-26 13:34:31 +03:00

[PR #2380] [MERGED] Missing ";" in ct/trilium.sh #3742