NginxProxyManager broken again for v2.13.5 #2026

New Issue

OVERLORD · 2026-02-05T03:24:53+03:00

OVERLORD commented

2026-02-05 03:24:53 +03:00

Originally created by @sammyke007 on GitHub (Nov 18, 2025).

✅ 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?

NginxProxyManager

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.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.0.17/c41e48ed2e1aa74a (running kernel: 6.17.2-1-pve)

📝 Provide a clear and concise description of the issue.

yarn seems to be failing on the newly added languages...
Log output:

    _   __      _               ____                           __  ___                                 
   / | / /___ _(_)___  _  __   / __ \_________  _  ____  __   /  |/  /___ _____  ____ _____ ____  _____
  /  |/ / __ `/ / __ \| |/_/  / /_/ / ___/ __ \| |/_/ / / /  / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/
 / /|  / /_/ / / / / />  <   / ____/ /  / /_/ />  </ /_/ /  / /  / / /_/ / / / / /_/ / /_/ /  __/ /    
/_/ |_/\__, /_/_/ /_/_/|_|  /_/   /_/   \____/_/|_|\__, /  /_/  /_/\__,_/_/ /_/\__,_/\__, /\___/_/     
      /____/                                      /____/                            /____/             

Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org trixie-security InRelease                                      
Hit:3 http://openresty.org/package/debian bookworm InRelease                                    
Hit:4 http://deb.debian.org/debian trixie-updates InRelease         
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
24 packages can be upgraded. Run 'apt list --upgradable' to see them.
Warning: http://openresty.org/package/debian/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details
Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details

changed 13 packages in 2s

28 packages are looking for funding
  run `npm fund` for details
  ✔️   Update Node.js 22
  ⏳   Updating yarn to latest version
changed 1 package in 708ms
  ✔️   Installed Node.js modules: yarn
  ✔️   nginxproxymanager is already up-to-date (v2.13.5)
  ✔️   Stopped Services
  ✔️   Cleaned old files
  ✔️   Set up Environment
yarn install v1.22.22
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.21s.
yarn run v1.22.22
$ tsc && vite build
src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations.

5 import langIt from "./lang/it.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:8:20 - error TS2307: Cannot find module './lang/nl.json' or its corresponding type declarations.

8 import langNl from "./lang/nl.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:12:20 - error TS2307: Cannot find module './lang/vi.json' or its corresponding type declarations.

12 import langVi from "./lang/vi.json";
                      ~~~~~~~~~~~~~~~~


Found 3 errors in the same file, starting at: src/locale/IntlProvider.tsx:5

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[ERROR] in line 128: exit code 0: while executing command $STD yarn build

root@nginxproxymanager:~#

🔄 Steps to reproduce the issue.

Try to update from v2.13.4 with:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"

❌ Paste the full error output (if available).

See above

🖼️ Additional context (optional).

No response

Originally created by @sammyke007 on GitHub (Nov 18, 2025). ### ✅ 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? NginxProxyManager ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.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? pve-manager/9.0.17/c41e48ed2e1aa74a (running kernel: 6.17.2-1-pve) ### 📝 Provide a clear and concise description of the issue. yarn seems to be failing on the newly added languages... Log output: ``` _ __ _ ____ __ ___ / | / /___ _(_)___ _ __ / __ \_________ _ ____ __ / |/ /___ _____ ____ _____ ____ _____ / |/ / __ `/ / __ \| |/_/ / /_/ / ___/ __ \| |/_/ / / / / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/ / /| / /_/ / / / / /> < / ____/ / / /_/ /> </ /_/ / / / / / /_/ / / / / /_/ / /_/ / __/ / /_/ |_/\__, /_/_/ /_/_/|_| /_/ /_/ \____/_/|_|\__, / /_/ /_/\__,_/_/ /_/\__,_/\__, /\___/_/ /____/ /____/ /____/ Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://openresty.org/package/debian bookworm InRelease Hit:4 http://deb.debian.org/debian trixie-updates InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease 24 packages can be upgraded. Run 'apt list --upgradable' to see them. Warning: http://openresty.org/package/debian/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details changed 13 packages in 2s 28 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 ⏳ Updating yarn to latest version changed 1 package in 708ms ✔️ Installed Node.js modules: yarn ✔️ nginxproxymanager is already up-to-date (v2.13.5) ✔️ Stopped Services ✔️ Cleaned old files ✔️ Set up Environment yarn install v1.22.22 [1/4] Resolving packages... success Already up-to-date. Done in 0.21s. yarn run v1.22.22 $ tsc && vite build src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations. 5 import langIt from "./lang/it.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:8:20 - error TS2307: Cannot find module './lang/nl.json' or its corresponding type declarations. 8 import langNl from "./lang/nl.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:12:20 - error TS2307: Cannot find module './lang/vi.json' or its corresponding type declarations. 12 import langVi from "./lang/vi.json"; ~~~~~~~~~~~~~~~~ Found 3 errors in the same file, starting at: src/locale/IntlProvider.tsx:5 error Command failed with exit code 2. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. [ERROR] in line 128: exit code 0: while executing command $STD yarn build root@nginxproxymanager:~# ``` ### 🔄 Steps to reproduce the issue. Try to update from v2.13.4 with: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)" ### ❌ Paste the full error output (if available). See above ### 🖼️ Additional context (optional). _No response_

OVERLORD added the bug external labels 2026-02-05 03:24:53 +03:00

OVERLORD closed this issue

2026-02-05 03:24:59 +03:00

OVERLORD commented

2026-02-05 03:25:03 +03:00

@MickLesk commented on GitHub (Nov 18, 2025):

Report it at npm repo, "src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations." say all.

@MickLesk commented on GitHub (Nov 18, 2025): Report it at npm repo, **"src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations."** say all.

OVERLORD commented

2026-02-05 03:25:05 +03:00

@sammyke007 commented on GitHub (Nov 18, 2025):

Report it at npm repo, "src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations." say all.

Done!
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4957

@sammyke007 commented on GitHub (Nov 18, 2025): > Report it at npm repo, **"src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations."** say all. Done! https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4957

OVERLORD commented

2026-02-05 03:25:08 +03:00

@MickLesk commented on GitHub (Nov 18, 2025):

The strange is, the file exist in tarball.

Can you enter to /opt/ng*/frontend/src/locale and do an ls -la?
and can you share the output of IntlProvider.tsx ?

@MickLesk commented on GitHub (Nov 18, 2025): The strange is, the file exist in tarball. Can you enter to /opt/ng*/frontend/src/locale and do an ls -la? and can you share the output of IntlProvider.tsx ?

OVERLORD commented

2026-02-05 03:25:12 +03:00

@sammyke007 commented on GitHub (Nov 18, 2025):

I "fixed" it manually by executing this first:

cp /opt/nginxproxymanager/frontend/src/locale/src/{nl,it,vi}.json \
   /opt/nginxproxymanager/frontend/src/locale/lang/

ls -la /opt/ng*/frontend/src/locale:

root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale# ls -la /opt/ng*/frontend/src/locale 
/opt/nginx-proxy-manager-2.13.1/frontend/src/locale:
total 36
drwxrwxr-x  5 root root 4096 Nov  5 06:40 .
drwxrwxr-x 11 root root 4096 Nov  5 06:40 ..
-rw-rw-r--  1 root root  313 Nov  5 06:40 DateTimeFormat.ts
-rw-rw-r--  1 root root 2045 Nov  5 06:40 IntlProvider.tsx
-rw-rw-r--  1 root root 1326 Nov  5 06:40 README.md
-rw-rw-r--  1 root root   66 Nov  5 06:40 index.ts
drwxrwxr-x  2 root root 4096 Nov  5 06:40 lang
drwxrwxr-x  2 root root 4096 Nov  5 06:40 scripts
drwxrwxr-x  3 root root 4096 Nov  5 06:40 src

/opt/nginxproxymanager/frontend/src/locale:
total 44
drwxr-xr-x  5 root root 4096 Nov  9 16:28 .
drwxr-xr-x 11 root root 4096 Nov  5 11:22 ..
-rw-r--r--  1 root root  313 Nov  5 11:22 DateTimeFormat.ts
-rw-r--r--  1 root root 3291 Nov 18 13:48 IntlProvider.tsx
-rw-r--r--  1 root root 1366 Nov 18 13:48 README.md
-rw-r--r--  1 root root 2045 Nov 18 13:48 Utils.test.tsx
-rw-r--r--  1 root root 1223 Nov 18 13:48 Utils.ts
-rw-r--r--  1 root root   57 Nov 18 13:48 index.ts
drwxr-xr-x  2 root root 4096 Nov 18 14:09 lang
drwxr-xr-x  2 root root 4096 Nov  5 11:22 scripts
drwxr-xr-x  3 root root 4096 Nov 18 13:48 src
root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale#

cat IntlProvider.tsx

root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale# cat IntlProvider.tsx 
import { createIntl, createIntlCache } from "react-intl";
import langDe from "./lang/de.json";
import langEn from "./lang/en.json";
import langEs from "./lang/es.json";
import langIt from "./lang/it.json";
import langJa from "./lang/ja.json";
import langList from "./lang/lang-list.json";
import langNl from "./lang/nl.json";
import langPl from "./lang/pl.json";
import langRu from "./lang/ru.json";
import langSk from "./lang/sk.json";
import langVi from "./lang/vi.json";
import langZh from "./lang/zh.json";

// first item of each array should be the language code,
// not the country code
// Remember when adding to this list, also update check-locales.js script
const localeOptions = [
        ["en", "en-US", langEn],
        ["de", "de-DE", langDe],
        ["es", "es-ES", langEs],
        ["ja", "ja-JP", langJa],
        ["it", "it-IT", langIt],
        ["nl", "nl-NL", langNl],
        ["pl", "pl-PL", langPl],
        ["ru", "ru-RU", langRu],
        ["sk", "sk-SK", langSk],
        ["vi", "vi-VN", langVi],
        ["zh", "zh-CN", langZh],
];

const loadMessages = (locale?: string): typeof langList & typeof langEn => {
        const thisLocale = (locale || "en").slice(0, 2);

        // ensure this lang exists in localeOptions above, otherwise fallback to en
        if (thisLocale === "en" || !localeOptions.some(([code]) => code === thisLocale)) {
                return Object.assign({}, langList, langEn);
        }

        return Object.assign({}, langList, langEn, localeOptions.find(([code]) => code === thisLocale)?.[2]);
};

const getFlagCodeForLocale = (locale?: string) => {
        const thisLocale = (locale || "en").slice(0, 2);

        // only add to this if your flag is different from the locale code
        const specialCases: Record<string, string> = {
                ja: "jp", // Japan
                zh: "cn", // China
        };

        if (specialCases[thisLocale]) {
                return specialCases[thisLocale].toUpperCase();
        }
        return thisLocale.toUpperCase();
};

const getLocale = (short = false) => {
        let loc = window.localStorage.getItem("locale");
        if (!loc) {
                loc = document.documentElement.lang;
        }
        if (short) {
                return loc.slice(0, 2);
        }
        // finally, fallback
        if (!loc) {
                loc = "en";
        }
        return loc;
};

const cache = createIntlCache();

const initialMessages = loadMessages(getLocale());
let intl = createIntl({ locale: getLocale(), messages: initialMessages }, cache);

const changeLocale = (locale: string): void => {
        const messages = loadMessages(locale);
        intl = createIntl({ locale, messages }, cache);
        window.localStorage.setItem("locale", locale);
        document.documentElement.lang = locale;
};

// This is a translation component that wraps the translation in a span with a data
// attribute so devs can inspect the element to see the translation ID
const T = ({
        id,
        data,
        tData,
}: {
        id: string;
        data?: Record<string, string | number | undefined>;
        tData?: Record<string, string>;
}) => {
        const translatedData: Record<string, string> = {};
        if (tData) {
                // iterate over tData and translate each value
                Object.entries(tData).forEach(([key, value]) => {
                        translatedData[key] = intl.formatMessage({ id: value });
                });
        }
        return (
                <span data-translation-id={id}>
                        {intl.formatMessage(
                                { id },
                                {
                                        ...data,
                                        ...translatedData,
                                },
                        )}
                </span>
        );
};

console.log("L:", localeOptions);

export { localeOptions, getFlagCodeForLocale, getLocale, createIntl, changeLocale, intl, T };
root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale#

@sammyke007 commented on GitHub (Nov 18, 2025): I "fixed" it manually by executing this first: ``` cp /opt/nginxproxymanager/frontend/src/locale/src/{nl,it,vi}.json \ /opt/nginxproxymanager/frontend/src/locale/lang/ ``` ls -la /opt/ng*/frontend/src/locale: ``` root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale# ls -la /opt/ng*/frontend/src/locale /opt/nginx-proxy-manager-2.13.1/frontend/src/locale: total 36 drwxrwxr-x 5 root root 4096 Nov 5 06:40 . drwxrwxr-x 11 root root 4096 Nov 5 06:40 .. -rw-rw-r-- 1 root root 313 Nov 5 06:40 DateTimeFormat.ts -rw-rw-r-- 1 root root 2045 Nov 5 06:40 IntlProvider.tsx -rw-rw-r-- 1 root root 1326 Nov 5 06:40 README.md -rw-rw-r-- 1 root root 66 Nov 5 06:40 index.ts drwxrwxr-x 2 root root 4096 Nov 5 06:40 lang drwxrwxr-x 2 root root 4096 Nov 5 06:40 scripts drwxrwxr-x 3 root root 4096 Nov 5 06:40 src /opt/nginxproxymanager/frontend/src/locale: total 44 drwxr-xr-x 5 root root 4096 Nov 9 16:28 . drwxr-xr-x 11 root root 4096 Nov 5 11:22 .. -rw-r--r-- 1 root root 313 Nov 5 11:22 DateTimeFormat.ts -rw-r--r-- 1 root root 3291 Nov 18 13:48 IntlProvider.tsx -rw-r--r-- 1 root root 1366 Nov 18 13:48 README.md -rw-r--r-- 1 root root 2045 Nov 18 13:48 Utils.test.tsx -rw-r--r-- 1 root root 1223 Nov 18 13:48 Utils.ts -rw-r--r-- 1 root root 57 Nov 18 13:48 index.ts drwxr-xr-x 2 root root 4096 Nov 18 14:09 lang drwxr-xr-x 2 root root 4096 Nov 5 11:22 scripts drwxr-xr-x 3 root root 4096 Nov 18 13:48 src root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale# ``` cat IntlProvider.tsx ``` root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale# cat IntlProvider.tsx import { createIntl, createIntlCache } from "react-intl"; import langDe from "./lang/de.json"; import langEn from "./lang/en.json"; import langEs from "./lang/es.json"; import langIt from "./lang/it.json"; import langJa from "./lang/ja.json"; import langList from "./lang/lang-list.json"; import langNl from "./lang/nl.json"; import langPl from "./lang/pl.json"; import langRu from "./lang/ru.json"; import langSk from "./lang/sk.json"; import langVi from "./lang/vi.json"; import langZh from "./lang/zh.json"; // first item of each array should be the language code, // not the country code // Remember when adding to this list, also update check-locales.js script const localeOptions = [ ["en", "en-US", langEn], ["de", "de-DE", langDe], ["es", "es-ES", langEs], ["ja", "ja-JP", langJa], ["it", "it-IT", langIt], ["nl", "nl-NL", langNl], ["pl", "pl-PL", langPl], ["ru", "ru-RU", langRu], ["sk", "sk-SK", langSk], ["vi", "vi-VN", langVi], ["zh", "zh-CN", langZh], ]; const loadMessages = (locale?: string): typeof langList & typeof langEn => { const thisLocale = (locale || "en").slice(0, 2); // ensure this lang exists in localeOptions above, otherwise fallback to en if (thisLocale === "en" || !localeOptions.some(([code]) => code === thisLocale)) { return Object.assign({}, langList, langEn); } return Object.assign({}, langList, langEn, localeOptions.find(([code]) => code === thisLocale)?.[2]); }; const getFlagCodeForLocale = (locale?: string) => { const thisLocale = (locale || "en").slice(0, 2); // only add to this if your flag is different from the locale code const specialCases: Record<string, string> = { ja: "jp", // Japan zh: "cn", // China }; if (specialCases[thisLocale]) { return specialCases[thisLocale].toUpperCase(); } return thisLocale.toUpperCase(); }; const getLocale = (short = false) => { let loc = window.localStorage.getItem("locale"); if (!loc) { loc = document.documentElement.lang; } if (short) { return loc.slice(0, 2); } // finally, fallback if (!loc) { loc = "en"; } return loc; }; const cache = createIntlCache(); const initialMessages = loadMessages(getLocale()); let intl = createIntl({ locale: getLocale(), messages: initialMessages }, cache); const changeLocale = (locale: string): void => { const messages = loadMessages(locale); intl = createIntl({ locale, messages }, cache); window.localStorage.setItem("locale", locale); document.documentElement.lang = locale; }; // This is a translation component that wraps the translation in a span with a data // attribute so devs can inspect the element to see the translation ID const T = ({ id, data, tData, }: { id: string; data?: Record<string, string | number | undefined>; tData?: Record<string, string>; }) => { const translatedData: Record<string, string> = {}; if (tData) { // iterate over tData and translate each value Object.entries(tData).forEach(([key, value]) => { translatedData[key] = intl.formatMessage({ id: value }); }); } return ( <span data-translation-id={id}> {intl.formatMessage( { id }, { ...data, ...translatedData, }, )} </span> ); }; console.log("L:", localeOptions); export { localeOptions, getFlagCodeForLocale, getLocale, createIntl, changeLocale, intl, T }; root@nginxproxymanager:/opt/nginxproxymanager/frontend/src/locale# ```

OVERLORD commented

2026-02-05 03:25:14 +03:00

@MickLesk commented on GitHub (Nov 18, 2025):

can you test following?

change /root/.nginx* to another version
run update again,

check if the frontend work fine / all data exist?

@MickLesk commented on GitHub (Nov 18, 2025): can you test following? change /root/.nginx* to another version run update again, check if the frontend work fine / all data exist?

OVERLORD commented

2026-02-05 03:25:18 +03:00

@sammyke007 commented on GitHub (Nov 18, 2025):

Change it back to eg 2.13.4 and update?

@sammyke007 commented on GitHub (Nov 18, 2025): Change it back to eg 2.13.4 and update?

OVERLORD commented

2026-02-05 03:25:23 +03:00

@MickLesk commented on GitHub (Nov 18, 2025):

yeah, all possible, you can enter x.x.x.x 😄 same effect

@MickLesk commented on GitHub (Nov 18, 2025): yeah, all possible, you can enter x.x.x.x :smile: same effect

OVERLORD commented

2026-02-05 03:25:26 +03:00

@sammyke007 commented on GitHub (Nov 18, 2025):

Failed with output:

    _   __      _               ____                           __  ___
   / | / /___ _(_)___  _  __   / __ \_________  _  ____  __   /  |/  /___ _____  ____ _____ ____  _____
  /  |/ / __ `/ / __ \| |/_/  / /_/ / ___/ __ \| |/_/ / / /  / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/
 / /|  / /_/ / / / / />  <   / ____/ /  / /_/ />  </ /_/ /  / /  / / /_/ / / / / /_/ / /_/ /  __/ /
/_/ |_/\__, /_/_/ /_/_/|_|  /_/   /_/   \____/_/|_|\__, /  /_/  /_/\__,_/_/ /_/\__,_/\__, /\___/_/
      /____/                                      /____/                            /____/

Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org trixie-security InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Ign:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Hit:5 http://openresty.org/package/debian bookworm InRelease
Ign:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Ign:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Err:4 https://deb.nodesource.com/node_22.x nodistro InRelease
  500  Internal Server Error [IP: 172.66.150.169 443]
24 packages can be upgraded. Run 'apt list --upgradable' to see them.
Warning: http://openresty.org/package/debian/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details
Warning: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease  500  Internal Server Error [IP: 172.66.150.169 443]
Warning: Some index files failed to download. They have been ignored, or old ones used instead.

changed 13 packages in 2s

28 packages are looking for funding
  run `npm fund` for details
  ✔️   Update Node.js 22
  ⏳   Updating yarn to latest version
changed 1 package in 668ms
  ✔️   Installed Node.js modules: yarn
  ✔️   Deployed: nginxproxymanager (2.13.5)
  ✔️   Stopped Services
  ✔️   Cleaned old files
  ✔️   Set up Environment
yarn install v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > @uiw/react-textarea-code-editor@3.1.1" has unmet peer dependency "@babel/runtime@>=7.10.0".
[4/4] Building fresh packages...
Done in 9.55s.
yarn run v1.22.22
$ tsc && vite build
src/locale/IntlProvider.tsx:2:20 - error TS2307: Cannot find module './lang/de.json' or its corresponding type declarations.

2 import langDe from "./lang/de.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:3:20 - error TS2307: Cannot find module './lang/en.json' or its corresponding type declarations.

3 import langEn from "./lang/en.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:4:20 - error TS2307: Cannot find module './lang/es.json' or its corresponding type declarations.

4 import langEs from "./lang/es.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations.

5 import langIt from "./lang/it.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:6:20 - error TS2307: Cannot find module './lang/ja.json' or its corresponding type declarations.

6 import langJa from "./lang/ja.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:7:22 - error TS2307: Cannot find module './lang/lang-list.json' or its corresponding type declarations.

7 import langList from "./lang/lang-list.json";
                       ~~~~~~~~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:8:20 - error TS2307: Cannot find module './lang/nl.json' or its corresponding type declarations.

8 import langNl from "./lang/nl.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:9:20 - error TS2307: Cannot find module './lang/pl.json' or its corresponding type declarations.

9 import langPl from "./lang/pl.json";
                     ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:10:20 - error TS2307: Cannot find module './lang/ru.json' or its corresponding type declarations.

10 import langRu from "./lang/ru.json";
                      ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:11:20 - error TS2307: Cannot find module './lang/sk.json' or its corresponding type declarations.

11 import langSk from "./lang/sk.json";
                      ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:12:20 - error TS2307: Cannot find module './lang/vi.json' or its corresponding type declarations.

12 import langVi from "./lang/vi.json";
                      ~~~~~~~~~~~~~~~~

src/locale/IntlProvider.tsx:13:20 - error TS2307: Cannot find module './lang/zh.json' or its corresponding type declarations.

13 import langZh from "./lang/zh.json";
                      ~~~~~~~~~~~~~~~~


Found 12 errors in the same file, starting at: src/locale/IntlProvider.tsx:2

error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[ERROR] in line 128: exit code 0: while executing command $STD yarn build

root@nginxproxymanager:/opt#

@sammyke007 commented on GitHub (Nov 18, 2025): Failed with output: ``` _ __ _ ____ __ ___ / | / /___ _(_)___ _ __ / __ \_________ _ ____ __ / |/ /___ _____ ____ _____ ____ _____ / |/ / __ `/ / __ \| |/_/ / /_/ / ___/ __ \| |/_/ / / / / /|_/ / __ `/ __ \/ __ `/ __ `/ _ \/ ___/ / /| / /_/ / / / / /> < / ____/ / / /_/ /> </ /_/ / / / / / /_/ / / / / /_/ / /_/ / __/ / /_/ |_/\__, /_/_/ /_/_/|_| /_/ /_/ \____/_/|_|\__, / /_/ /_/\__,_/_/ /_/\__,_/\__, /\___/_/ /____/ /____/ /____/ Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Ign:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://openresty.org/package/debian bookworm InRelease Ign:4 https://deb.nodesource.com/node_22.x nodistro InRelease Ign:4 https://deb.nodesource.com/node_22.x nodistro InRelease Err:4 https://deb.nodesource.com/node_22.x nodistro InRelease 500 Internal Server Error [IP: 172.66.150.169 443] 24 packages can be upgraded. Run 'apt list --upgradable' to see them. Warning: http://openresty.org/package/debian/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details Warning: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease 500 Internal Server Error [IP: 172.66.150.169 443] Warning: Some index files failed to download. They have been ignored, or old ones used instead. changed 13 packages in 2s 28 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 ⏳ Updating yarn to latest version changed 1 package in 668ms ✔️ Installed Node.js modules: yarn ✔️ Deployed: nginxproxymanager (2.13.5) ✔️ Stopped Services ✔️ Cleaned old files ✔️ Set up Environment yarn install v1.22.22 [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... warning " > @uiw/react-textarea-code-editor@3.1.1" has unmet peer dependency "@babel/runtime@>=7.10.0". [4/4] Building fresh packages... Done in 9.55s. yarn run v1.22.22 $ tsc && vite build src/locale/IntlProvider.tsx:2:20 - error TS2307: Cannot find module './lang/de.json' or its corresponding type declarations. 2 import langDe from "./lang/de.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:3:20 - error TS2307: Cannot find module './lang/en.json' or its corresponding type declarations. 3 import langEn from "./lang/en.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:4:20 - error TS2307: Cannot find module './lang/es.json' or its corresponding type declarations. 4 import langEs from "./lang/es.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:5:20 - error TS2307: Cannot find module './lang/it.json' or its corresponding type declarations. 5 import langIt from "./lang/it.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:6:20 - error TS2307: Cannot find module './lang/ja.json' or its corresponding type declarations. 6 import langJa from "./lang/ja.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:7:22 - error TS2307: Cannot find module './lang/lang-list.json' or its corresponding type declarations. 7 import langList from "./lang/lang-list.json"; ~~~~~~~~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:8:20 - error TS2307: Cannot find module './lang/nl.json' or its corresponding type declarations. 8 import langNl from "./lang/nl.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:9:20 - error TS2307: Cannot find module './lang/pl.json' or its corresponding type declarations. 9 import langPl from "./lang/pl.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:10:20 - error TS2307: Cannot find module './lang/ru.json' or its corresponding type declarations. 10 import langRu from "./lang/ru.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:11:20 - error TS2307: Cannot find module './lang/sk.json' or its corresponding type declarations. 11 import langSk from "./lang/sk.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:12:20 - error TS2307: Cannot find module './lang/vi.json' or its corresponding type declarations. 12 import langVi from "./lang/vi.json"; ~~~~~~~~~~~~~~~~ src/locale/IntlProvider.tsx:13:20 - error TS2307: Cannot find module './lang/zh.json' or its corresponding type declarations. 13 import langZh from "./lang/zh.json"; ~~~~~~~~~~~~~~~~ Found 12 errors in the same file, starting at: src/locale/IntlProvider.tsx:2 error Command failed with exit code 2. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. [ERROR] in line 128: exit code 0: while executing command $STD yarn build root@nginxproxymanager:/opt# ```

OVERLORD commented

2026-02-05 03:25:32 +03:00

@MickLesk commented on GitHub (Nov 18, 2025):

Okay same. Then its realy an "upstream" issue, because ive added an clean_install var, that remove the whole folder and deploy an new tarball

@MickLesk commented on GitHub (Nov 18, 2025): Okay same. Then its realy an "upstream" issue, because ive added an clean_install var, that remove the whole folder and deploy an new tarball

OVERLORD commented

2026-02-05 03:25:37 +03:00

@sammyke007 commented on GitHub (Nov 18, 2025):

Ok, I'll try to get mine back up again now :-D

@sammyke007 commented on GitHub (Nov 18, 2025): Ok, I'll try to get mine back up again now :-D

OVERLORD commented

2026-02-05 03:25:40 +03:00

@MickLesk commented on GitHub (Nov 18, 2025):

Thx 4 Help! So now we wait for feedback in npm-repo

@MickLesk commented on GitHub (Nov 18, 2025): Thx 4 Help! So now we wait for feedback in npm-repo

OVERLORD commented

2026-02-05 03:25:43 +03:00

@CrazyUs3r commented on GitHub (Nov 18, 2025):

I find Next error after Re rename src to lang

✔️ Stopped Services
✔️ Cleaned old files
✔️ Set up Environment
yarn install v1.22.22 [1/4] Resolving packages...
success Already up-to-date. Done in 0.18s.
yarn run v1.22.22
$ tsc && vite build
src/locale/IntlProvider.tsx:76:46 - error TS2322: Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, string> | Record<string, MessageFormatElement[]> | undefined'.
Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, MessageFormatElement[]>'.
Property '"locale-en-US"' is incompatible with index signature.
Type '{ defaultMessage: string; }' is missing the following properties from type 'MessageFormatElement[]': length, pop, push, concat, and 29 more.

76 let intl = createIntl({ locale: getLocale(), messages: initialMessages }, cache);
~~~~~~~~

node_modules/@formatjs/intl/src/types.d.ts:38:5
38 messages: Record<MessageIds, string> | Record<MessageIds, MessageFormatElement[]>;
~~~~~~~~
The expected type comes from property 'messages' which is declared here on type 'IntlConfig'

src/locale/IntlProvider.tsx:80:30 - error TS2322: Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, string> | Record<string, MessageFormatElement[]> | undefined'.
Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, MessageFormatElement[]>'.
Property '"locale-en-US"' is incompatible with index signature.
Type '{ defaultMessage: string; }' is missing the following properties from type 'MessageFormatElement[]': length, pop, push, concat, and 29 more.

80 intl = createIntl({ locale, messages }, cache);
~~~~~~~~

node_modules/@formatjs/intl/src/types.d.ts:38:5
38 messages: Record<MessageIds, string> | Record<MessageIds, MessageFormatElement[]>;
~~~~~~~~
The expected type comes from property 'messages' which is declared here on type 'IntlConfig'

src/modals/HelpModal.tsx:8:29 - error TS2307: Cannot find module 'src/locale/src/HelpDoc' or its corresponding type declarations.

8 import { getHelpFile } from "src/locale/src/HelpDoc";
~~~~~~~~~~~~~~~~~~~~~~~~

Found 3 errors in 2 files.

Errors Files
2 src/locale/IntlProvider.tsx:76
1 src/modals/HelpModal.tsx:8
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[ERROR] in line 128: exit code 0: while executing command $STD yarn build

@CrazyUs3r commented on GitHub (Nov 18, 2025): I find Next error after Re rename src to lang ✔️ Stopped Services ✔️ Cleaned old files ✔️ Set up Environment yarn install v1.22.22 [1/4] Resolving packages... success Already up-to-date. Done in 0.18s. yarn run v1.22.22 $ tsc && vite build src/locale/IntlProvider.tsx:76:46 - error TS2322: Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, string> | Record<string, MessageFormatElement[]> | undefined'. Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, MessageFormatElement[]>'. Property '"locale-en-US"' is incompatible with index signature. Type '{ defaultMessage: string; }' is missing the following properties from type 'MessageFormatElement[]': length, pop, push, concat, and 29 more. 76 let intl = createIntl({ locale: getLocale(), messages: initialMessages }, cache); ~~~~~~~~ node_modules/@formatjs/intl/src/types.d.ts:38:5 38 messages: Record<MessageIds, string> | Record<MessageIds, MessageFormatElement[]>; ~~~~~~~~ The expected type comes from property 'messages' which is declared here on type 'IntlConfig' src/locale/IntlProvider.tsx:80:30 - error TS2322: Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, string> | Record<string, MessageFormatElement[]> | undefined'. Type '{ "locale-en-US": { defaultMessage: string; }; "locale-es-ES": { defaultMessage: string; }; "locale-de-DE": { defaultMessage: string; }; "locale-ja-JP": { defaultMessage: string; }; "locale-ru-RU": { defaultMessage: string; }; ... 5 more ...; "locale-nl-NL": { ...; }; } & { ...; }' is not assignable to type 'Record<string, MessageFormatElement[]>'. Property '"locale-en-US"' is incompatible with index signature. Type '{ defaultMessage: string; }' is missing the following properties from type 'MessageFormatElement[]': length, pop, push, concat, and 29 more. 80 intl = createIntl({ locale, messages }, cache); ~~~~~~~~ node_modules/@formatjs/intl/src/types.d.ts:38:5 38 messages: Record<MessageIds, string> | Record<MessageIds, MessageFormatElement[]>; ~~~~~~~~ The expected type comes from property 'messages' which is declared here on type 'IntlConfig' src/modals/HelpModal.tsx:8:29 - error TS2307: Cannot find module 'src/locale/src/HelpDoc' or its corresponding type declarations. 8 import { getHelpFile } from "src/locale/src/HelpDoc"; ~~~~~~~~~~~~~~~~~~~~~~~~ Found 3 errors in 2 files. Errors Files 2 src/locale/IntlProvider.tsx:76 1 src/modals/HelpModal.tsx:8 error Command failed with exit code 2. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. [ERROR] in line 128: exit code 0: while executing command $STD yarn build

OVERLORD commented

2026-02-05 03:25:46 +03:00

@peterchs commented on GitHub (Nov 18, 2025):

Yes same error here after similar attempt to fix with an ln -s src to the missing lang dir.

Any way to easily rollback to 2.13.4? I dont have a snapshot :(

@peterchs commented on GitHub (Nov 18, 2025): Yes same error here after similar attempt to fix with an ln -s src to the missing lang dir. Any way to easily rollback to 2.13.4? I dont have a snapshot :(

OVERLORD commented

2026-02-05 03:25:54 +03:00

@sammyke007 commented on GitHub (Nov 18, 2025):

I have switched to docker for now.

@sammyke007 commented on GitHub (Nov 18, 2025): I have switched to docker for now.

OVERLORD commented

2026-02-05 03:26:00 +03:00

@djusHa commented on GitHub (Nov 19, 2025):

Add yarn locale-compile before yarn build in ttecks install script, then it should build.

msg_info "Building Frontend"
export NODE_OPTIONS="--max_old_space_size=2048 --openssl-legacy-provider"
cd /opt/nginxproxymanager/frontend
# Replace node-sass with sass in package.json before installation
sed -E -i 's/"node-sass" *: *"([^"]*)"/"sass": "\1"/g' package.json
$STD yarn install --network-timeout 600000
$STD yarn locale-compile <-- ADD THIS
$STD yarn build
...

@djusHa commented on GitHub (Nov 19, 2025): Add `yarn locale-compile` before `yarn build` in ttecks install script, then it should build. ``` msg_info "Building Frontend" export NODE_OPTIONS="--max_old_space_size=2048 --openssl-legacy-provider" cd /opt/nginxproxymanager/frontend # Replace node-sass with sass in package.json before installation sed -E -i 's/"node-sass" *: *"([^"]*)"/"sass": "\1"/g' package.json $STD yarn install --network-timeout 600000 $STD yarn locale-compile <-- ADD THIS $STD yarn build ... ```

OVERLORD commented

2026-02-05 03:26:03 +03:00

@est3ban129 commented on GitHub (Nov 19, 2025):

same problem here

@est3ban129 commented on GitHub (Nov 19, 2025): same problem here

OVERLORD commented

2026-02-05 03:26:10 +03:00

@MickLesk commented on GitHub (Nov 19, 2025):

We have now pinned the version (as with Immich) to the last known working version (2.13.4) until we finally get feedback from the developer. I don't want to add an extra Yarn step if it's not actually needed and might be destroyed again in the next release. 😄

@MickLesk commented on GitHub (Nov 19, 2025): We have now pinned the version (as with Immich) to the last known working version (2.13.4) until we finally get feedback from the developer. I don't want to add an extra Yarn step if it's not actually needed and might be destroyed again in the next release. :smile:

OVERLORD commented

2026-02-05 03:26:15 +03:00

@yuriw commented on GitHub (Nov 29, 2025):

Tried from v2.12.6 to v2.13.5

✓ Stopped Services
✓ Cleaned Old Files
✓ Downloaded NPM v2.13.5
/sed: can't read frontend/js/i18n/messages.json: No such file or directory

[ERROR] in line 98: exit code 0: while executing command sed -i 's|"fork-me": ".*"|"fork-me": "Proxmox VE Helper-Scripts"|' frontend/js/i18n/messages.json

@yuriw commented on GitHub (Nov 29, 2025): Tried from v2.12.6 to v2.13.5 ✓ Stopped Services ✓ Cleaned Old Files ✓ Downloaded NPM v2.13.5 /sed: can't read frontend/js/i18n/messages.json: No such file or directory [ERROR] in line 98: exit code 0: while executing command sed -i 's|"fork-me": ".*"|"fork-me": "Proxmox VE Helper-Scripts"|' frontend/js/i18n/messages.json <img width="1399" height="455" alt="Image" src="https://github.com/user-attachments/assets/d36fe1eb-b7b1-4ee0-8968-16c95cf80475" />

OVERLORD commented

2026-02-05 03:26:18 +03:00

@MickLesk commented on GitHub (Nov 29, 2025):

Tried from v2.12.6 to v2.13.5

✓ Stopped Services ✓ Cleaned Old Files ✓ Downloaded NPM v2.13.5 /sed: can't read frontend/js/i18n/messages.json: No such file or directory

[ERROR] in line 98: exit code 0: while executing command sed -i 's|"fork-me": ".*"|"fork-me": "Proxmox VE Helper-Scripts"|' frontend/js/i18n/messages.json

wrong script. wrong repo.

@MickLesk commented on GitHub (Nov 29, 2025): > Tried from v2.12.6 to v2.13.5 > > ✓ Stopped Services ✓ Cleaned Old Files ✓ Downloaded NPM v2.13.5 /sed: can't read frontend/js/i18n/messages.json: No such file or directory > > [ERROR] in line 98: exit code 0: while executing command sed -i 's|"fork-me": ".*"|"fork-me": "Proxmox VE Helper-Scripts"|' frontend/js/i18n/messages.json wrong script. wrong repo.

OVERLORD commented

2026-02-05 03:26:22 +03:00

@yuriw commented on GitHub (Nov 29, 2025):

@MickLesk any suggestions how to fix it?

Obviously it was a while when I first installed it it
Or I have to do a new setup?
TIA

@yuriw commented on GitHub (Nov 29, 2025): @MickLesk any suggestions how to fix it? Obviously it was a while when I first installed it it Or I have to do a new setup? TIA

OVERLORD commented

2026-02-05 03:26:24 +03:00

@MickLesk commented on GitHub (Nov 29, 2025):

Change your /usr/local/update. You Crawl the old tteck Repo.

@MickLesk commented on GitHub (Nov 29, 2025): Change your /usr/local/update. You Crawl the old tteck Repo.

OVERLORD commented

2026-02-05 03:26:26 +03:00

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

Change your /usr/local/update. You Crawl the old tteck Repo.

I did change:

root@nginx:~# cat /usr/bin/update
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"

Had to update to trixie
But was able to update NM

Thx @MickLesk !

@yuriw commented on GitHub (Nov 30, 2025): > Change your /usr/local/update. You Crawl the old tteck Repo. I did change: root@nginx:~# cat /usr/bin/update bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)" Had to update to trixie But was able to update NM Thx @MickLesk !

OVERLORD commented

2026-02-05 03:26:28 +03:00

@TheBToby commented on GitHub (Dec 1, 2025):

I'm facing the same issue. I used the new update script and manually updated to trixie. However, after this, the npm service does not start anymore (systemctl status) and I can't load the UI anymore. So, I had to restore a backup. Any ideas?

@TheBToby commented on GitHub (Dec 1, 2025): I'm facing the same issue. I used the new update script and manually updated to trixie. However, after this, the npm service does not start anymore (systemctl status) and I can't load the UI anymore. So, I had to restore a backup. Any ideas?

OVERLORD commented

2026-02-05 03:26:31 +03:00

@MickLesk commented on GitHub (Dec 1, 2025):

With our Update? There is an fixed Version before the Break. Without Logs and build Nobody can help you. And reminder, before update Always do snapshots.

@MickLesk commented on GitHub (Dec 1, 2025): With our Update? There is an fixed Version before the Break. Without Logs and build Nobody can help you. And reminder, before update Always do snapshots.

OVERLORD commented

2026-02-05 03:26:33 +03:00

@TheBToby commented on GitHub (Dec 1, 2025):

Sure! I updated to Trixie with the following commands:

sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
apt update
apt dist-upgrade
apt modernize-sources

Then I updated npm:

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

Getting this error:

x npm.service - Nginx Proxy Manager
     Loaded: loaded (/usr/lib/systemd/system/npm.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2025-12-01 21:09:59 CET; 38s ago
   Duration: 3ms
 Invocation: 7f614ccd21634eb4b3a6a43ef8da5719
    Process: 2374 ExecStartPre=mkdir -p /tmp/nginx/body /data/letsencrypt-acme-challenge (code=exited, status=0/SUCCESS)
    Process: 2375 ExecStart=/root/.nvm/versions/node/v23.11.0/bin/node index.js --abort_on_uncaught_exception --max_old_space_size=250 (code=exited, status=203/EXEC)
   Main PID: 2375 (code=exited, status=203/EXEC)

Dec 01 21:09:59 nginxproxymanager systemd[1]: npm.service: Scheduled restart job, restart counter is at 5.
Dec 01 21:09:59 nginxproxymanager systemd[1]: npm.service: Start request repeated too quickly.
Dec 01 21:09:59 nginxproxymanager systemd[1]: npm.service: Failed with result 'exit-code'.
Dec 01 21:09:59 nginxproxymanager systemd[1]: Failed to start npm.service - Nginx Proxy Manager.

What other logs would be helpful?

@TheBToby commented on GitHub (Dec 1, 2025): Sure! I updated to Trixie with the following commands: ```shell sed -i 's/bookworm/trixie/g' /etc/apt/sources.list apt update apt dist-upgrade apt modernize-sources ``` Then I updated npm: ```shell bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)" ``` Getting this error: ```shell x npm.service - Nginx Proxy Manager Loaded: loaded (/usr/lib/systemd/system/npm.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2025-12-01 21:09:59 CET; 38s ago Duration: 3ms Invocation: 7f614ccd21634eb4b3a6a43ef8da5719 Process: 2374 ExecStartPre=mkdir -p /tmp/nginx/body /data/letsencrypt-acme-challenge (code=exited, status=0/SUCCESS) Process: 2375 ExecStart=/root/.nvm/versions/node/v23.11.0/bin/node index.js --abort_on_uncaught_exception --max_old_space_size=250 (code=exited, status=203/EXEC) Main PID: 2375 (code=exited, status=203/EXEC) Dec 01 21:09:59 nginxproxymanager systemd[1]: npm.service: Scheduled restart job, restart counter is at 5. Dec 01 21:09:59 nginxproxymanager systemd[1]: npm.service: Start request repeated too quickly. Dec 01 21:09:59 nginxproxymanager systemd[1]: npm.service: Failed with result 'exit-code'. Dec 01 21:09:59 nginxproxymanager systemd[1]: Failed to start npm.service - Nginx Proxy Manager. ``` What other logs would be helpful?

OVERLORD commented

2026-02-05 03:26:35 +03:00

@TheBToby commented on GitHub (Dec 2, 2025):

Update: I set up a new LXC from scratch and migrated the configuration from the "old" to the new Nginx LXC. This works like a charm!

@TheBToby commented on GitHub (Dec 2, 2025): Update: I set up a new LXC from scratch and migrated the configuration from the "old" to the new Nginx LXC. This works like a charm!

OVERLORD commented

2026-02-05 03:26:39 +03:00

@yuriw commented on GitHub (Dec 2, 2025):

Update: I set up a new LXC from scratch and migrated the configuration from the "old" to the new Nginx LXC. This works like a charm!

Can you share the migration steps please?

@yuriw commented on GitHub (Dec 2, 2025): > Update: I set up a new LXC from scratch and migrated the configuration from the "old" to the new Nginx LXC. This works like a charm! Can you share the migration steps please?

OVERLORD commented

2026-02-05 03:26:42 +03:00

@TheBToby commented on GitHub (Dec 2, 2025):

Sure!
First, I made a backup of the following two directories from the "old" Nginx Proxy Manager LXC (maybe enable SSH first to download the folders):

/data
/etc/letsencrypt

Then, I created a new LXC from scratch using the default command (enable SSH again for upload of folders):

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

Upload and overwrite the two folders from the backup and restart the LXC.
Next, I stopped the "old" NPM LXC, assigned the fixed IP address of the old LXC to the new one (DHCP server), rebooted the new LXC... et voila!

@TheBToby commented on GitHub (Dec 2, 2025): Sure! First, I made a backup of the following two directories from the "old" Nginx Proxy Manager LXC (maybe enable SSH first to download the folders): ```shell /data /etc/letsencrypt ``` Then, I created a new LXC from scratch using the default command (enable SSH again for upload of folders): ```shell bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)" ``` Upload and overwrite the two folders from the backup and restart the LXC. Next, I stopped the "old" NPM LXC, assigned the fixed IP address of the old LXC to the new one (DHCP server), rebooted the new LXC... et voila!

OVERLORD commented

2026-02-05 03:26:45 +03:00

@yuriw commented on GitHub (Dec 2, 2025):

@TheBToby That's cool, thx!
Have you tried updating the certificate?
I use DuckDNS and it did not work after I updated the LXC

@yuriw commented on GitHub (Dec 2, 2025): @TheBToby That's cool, thx! Have you tried updating the certificate? I use DuckDNS and it did not work after I updated the LXC

OVERLORD commented

2026-02-05 03:26:50 +03:00

@TheBToby commented on GitHub (Dec 2, 2025):

@yuriw No, I did not update any certificates.

@TheBToby commented on GitHub (Dec 2, 2025): @yuriw No, I did not update any certificates.

OVERLORD commented

2026-02-05 03:26:58 +03:00

@miloumeeloo commented on GitHub (Dec 3, 2025):

Update: I set up a new LXC from scratch and migrated the configuration from the "old" to the new Nginx LXC. This works like a charm!

Thanks for the idea. I have both services openresty and npm working but i can't access the admin page (message: The API is not healthy) and i get errors when i try to install certbot plugins.

root@nginxproxymanager:/app/scripts# ./install-certbot-plugins dnsmulti
[03/12/2025] [13:14:11] [Certbot  ] › ▶  start     Installing dnsmulti...
[03/12/2025] [13:14:13] [Certbot  ] › ✖  error     ERROR: Exception:
Traceback (most recent call last):
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/cli/base_command.py", line 107, in _run_wrapper
    status = _inner_run()
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/cli/base_command.py", line 98, in _inner_run
    return self.run(options, args)
           ~~~~~~~~^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/cli/req_command.py", line 85, in wrapper
    return func(self, options, args)
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/commands/install.py", line 388, in run
    requirement_set = resolver.resolve(
        reqs, check_supported_wheels=not options.target_dir
    )
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 99, in resolve
    result = self._result = resolver.resolve(
                            ~~~~~~~~~~~~~~~~^
        collected.requirements, max_rounds=limit_how_complex_resolution_can_be
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/resolvers/resolution.py", line 601, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/resolvers/resolution.py", line 434, in resolve
    self._add_to_criteria(self.state.criteria, r, parent=None)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/resolvers/resolution.py", line 150, in _add_to_criteria
    if not criterion.candidates:
           ^^^^^^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/structs.py", line 194, in __bool__
    return bool(self._sequence)
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 165, in __bool__
    self._bool = any(self)
                 ~~~^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 149, in <genexpr>
    return (c for c in iterator if id(c) not in self._incompatible_ids)
                       ^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 39, in _iter_built
    candidate = func()
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 180, in _make_candidate_from_link
    base: BaseCandidate | None = self._make_base_candidate_from_link(
                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        link, template, name, version
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 226, in _make_base_candidate_from_link
    self._link_candidate_cache[link] = LinkCandidate(
                                       ~~~~~~~~~~~~~^
        link,
        ^^^^^
    ...<3 lines>...
        version=version,
        ^^^^^^^^^^^^^^^^
    )
    ^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 318, in __init__
    super().__init__(
    ~~~~~~~~~~~~~~~~^
        link=link,
        ^^^^^^^^^^
    ...<4 lines>...
        version=version,
        ^^^^^^^^^^^^^^^^
    )
    ^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 161, in __init__
    self.dist = self._prepare()
                ~~~~~~~~~~~~~^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 238, in _prepare
    dist = self._prepare_distribution()
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 329, in _prepare_distribution
    return preparer.prepare_linked_requirement(self._ireq, parallel_builds=True)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/operations/prepare.py", line 543, in prepare_linked_requirement
    return self._prepare_linked_requirement(req, parallel_builds)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/operations/prepare.py", line 658, in _prepare_linked_requirement
    dist = _get_prepared_distribution(
        req,
    ...<3 lines>...
        self.check_build_deps,
    )
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/operations/prepare.py", line 77, in _get_prepared_distribution
    abstract_dist.prepare_distribution_metadata(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        build_env_installer, build_isolation, check_build_deps
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/distributions/sdist.py", line 55, in prepare_distribution_metadata
    self._install_build_reqs(build_env_installer)
    ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/distributions/sdist.py", line 132, in _install_build_reqs
    build_reqs = self._get_build_requires_wheel()
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/distributions/sdist.py", line 107, in _get_build_requires_wheel
    return backend.get_requires_for_build_wheel()
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/utils/misc.py", line 694, in get_requires_for_build_wheel
    return super().get_requires_for_build_wheel(config_settings=cs)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_impl.py", line 196, in get_requires_for_build_wheel
    return self._call_hook(
           ~~~~~~~~~~~~~~~^
        "get_requires_for_build_wheel", {"config_settings": config_settings}
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_impl.py", line 402, in _call_hook
    raise BackendUnavailable(
    ...<4 lines>...
    )
pip._vendor.pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta'

[03/12/2025] [13:14:13] [Certbot  ] › ✖  error     Some plugins failed to install. Please check the logs above. Failing plugins: 
 - dnsmulti

@miloumeeloo commented on GitHub (Dec 3, 2025): > Update: I set up a new LXC from scratch and migrated the configuration from the "old" to the new Nginx LXC. This works like a charm! Thanks for the idea. I have both services openresty and npm working but i can't access the admin page (message: The API is not healthy) and i get errors when i try to install certbot plugins. ``` root@nginxproxymanager:/app/scripts# ./install-certbot-plugins dnsmulti [03/12/2025] [13:14:11] [Certbot ] › ▶ start Installing dnsmulti... [03/12/2025] [13:14:13] [Certbot ] › ✖ error ERROR: Exception: Traceback (most recent call last): File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/cli/base_command.py", line 107, in _run_wrapper status = _inner_run() File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/cli/base_command.py", line 98, in _inner_run return self.run(options, args) ~~~~~~~~^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/cli/req_command.py", line 85, in wrapper return func(self, options, args) File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/commands/install.py", line 388, in run requirement_set = resolver.resolve( reqs, check_supported_wheels=not options.target_dir ) File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 99, in resolve result = self._result = resolver.resolve( ~~~~~~~~~~~~~~~~^ collected.requirements, max_rounds=limit_how_complex_resolution_can_be ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/resolvers/resolution.py", line 601, in resolve state = resolution.resolve(requirements, max_rounds=max_rounds) File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/resolvers/resolution.py", line 434, in resolve self._add_to_criteria(self.state.criteria, r, parent=None) ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/resolvers/resolution.py", line 150, in _add_to_criteria if not criterion.candidates: ^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/resolvelib/structs.py", line 194, in __bool__ return bool(self._sequence) File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 165, in __bool__ self._bool = any(self) ~~~^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 149, in <genexpr> return (c for c in iterator if id(c) not in self._incompatible_ids) ^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 39, in _iter_built candidate = func() File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 180, in _make_candidate_from_link base: BaseCandidate | None = self._make_base_candidate_from_link( ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ link, template, name, version ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 226, in _make_base_candidate_from_link self._link_candidate_cache[link] = LinkCandidate( ~~~~~~~~~~~~~^ link, ^^^^^ ...<3 lines>... version=version, ^^^^^^^^^^^^^^^^ ) ^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 318, in __init__ super().__init__( ~~~~~~~~~~~~~~~~^ link=link, ^^^^^^^^^^ ...<4 lines>... version=version, ^^^^^^^^^^^^^^^^ ) ^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 161, in __init__ self.dist = self._prepare() ~~~~~~~~~~~~~^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 238, in _prepare dist = self._prepare_distribution() File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 329, in _prepare_distribution return preparer.prepare_linked_requirement(self._ireq, parallel_builds=True) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/operations/prepare.py", line 543, in prepare_linked_requirement return self._prepare_linked_requirement(req, parallel_builds) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/operations/prepare.py", line 658, in _prepare_linked_requirement dist = _get_prepared_distribution( req, ...<3 lines>... self.check_build_deps, ) File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/operations/prepare.py", line 77, in _get_prepared_distribution abstract_dist.prepare_distribution_metadata( ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ build_env_installer, build_isolation, check_build_deps ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/distributions/sdist.py", line 55, in prepare_distribution_metadata self._install_build_reqs(build_env_installer) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/distributions/sdist.py", line 132, in _install_build_reqs build_reqs = self._get_build_requires_wheel() File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/distributions/sdist.py", line 107, in _get_build_requires_wheel return backend.get_requires_for_build_wheel() ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_internal/utils/misc.py", line 694, in get_requires_for_build_wheel return super().get_requires_for_build_wheel(config_settings=cs) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^ File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_impl.py", line 196, in get_requires_for_build_wheel return self._call_hook( ~~~~~~~~~~~~~~~^ "get_requires_for_build_wheel", {"config_settings": config_settings} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/opt/certbot/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_impl.py", line 402, in _call_hook raise BackendUnavailable( ...<4 lines>... ) pip._vendor.pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta' [03/12/2025] [13:14:13] [Certbot ] › ✖ error Some plugins failed to install. Please check the logs above. Failing plugins: - dnsmulti ```

OVERLORD commented

2026-02-05 03:27:02 +03:00

@jpatje commented on GitHub (Dec 4, 2025):

I faced the exact same problem (as in the screenshot above). Text version of the error:

_✓ Downloaded NPM v2.13.5
/sed: can't read frontend/js/i18n/messages.json: No such file or directory

[ERROR] in line 98: exit code 0: while executing command sed -i 's|"fork-me": ".*"|"fork-me": "Proxmox VE Helper-Scripts"|' frontend/js/i18n/messages.json_

Decided to revert to a backup I made. Running v2.12.6 again now..
After restoring, I checked /usr/bin/update and it shows this:

bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/nginxproxymanager.sh)"

Should it be changed?

@jpatje commented on GitHub (Dec 4, 2025): I faced the exact same problem (as in the screenshot above). Text version of the error: _✓ Downloaded NPM v2.13.5 /sed: can't read frontend/js/i18n/messages.json: No such file or directory [ERROR] in line 98: exit code 0: while executing command sed -i 's|"fork-me": ".*"|"fork-me": "Proxmox VE Helper-Scripts"|' frontend/js/i18n/messages.json_ Decided to revert to a backup I made. Running v2.12.6 again now.. After restoring, I checked /usr/bin/update and it shows this: bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/nginxproxymanager.sh)" Should it be changed?

OVERLORD commented

2026-02-05 03:27:09 +03:00

@MickLesk commented on GitHub (Dec 4, 2025):

yes. since nearly over 1 year.

@MickLesk commented on GitHub (Dec 4, 2025): yes. since nearly over 1 year.

OVERLORD commented

2026-02-05 03:27:14 +03:00

@jpatje commented on GitHub (Dec 4, 2025):

Tried to spin up a new instance using the Proxmox Helper Scripts and migrate all settings to the new Nginx Proxy Manager.
In the end my self hosted websites weren't working anymore and I was unable to fix it.
Reverted the old version, I better not touch it anymore.

@jpatje commented on GitHub (Dec 4, 2025): Tried to spin up a new instance using the Proxmox Helper Scripts and migrate all settings to the new Nginx Proxy Manager. In the end my self hosted websites weren't working anymore and I was unable to fix it. Reverted the old version, I better not touch it anymore.

OVERLORD commented

2026-02-05 03:27:19 +03:00

@TheBToby commented on GitHub (Dec 5, 2025):

@TheBToby That's cool, thx! Have you tried updating the certificate? I use DuckDNS and it did not work after I updated the LXC

OK, I'm now running into issues with my Cloudflare origin certificates as well. It appears that the issue is solved in NPM 2.13.5 but the current update script only updates to 2.13.4. Therefore, I'm waiting for the script to support the latest version, hoping my issues get resolved by that.

@TheBToby commented on GitHub (Dec 5, 2025): > [@TheBToby](https://github.com/TheBToby) That's cool, thx! Have you tried updating the certificate? I use DuckDNS and it did not work after I updated the LXC OK, I'm now running into issues with my Cloudflare origin certificates as well. It appears that the issue is solved in NPM 2.13.5 but the current update script only updates to 2.13.4. Therefore, I'm waiting for the script to support the latest version, hoping my issues get resolved by that.

OVERLORD commented

2026-02-05 03:27:30 +03:00

@MickLesk commented on GitHub (Dec 5, 2025):

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4957

It could have been resolved long ago, but once again there is no feedback.

@MickLesk commented on GitHub (Dec 5, 2025): https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4957 It could have been resolved long ago, but once again there is no feedback.

OVERLORD commented

2026-02-05 03:27:36 +03:00

@jpatje commented on GitHub (Dec 5, 2025):

@TheBToby That's cool, thx! Have you tried updating the certificate? I use DuckDNS and it did not work after I updated the LXC

OK, I'm now running into issues with my Cloudflare origin certificates as well. It appears that the issue is solved in NPM 2.13.5 but the current update script only updates to 2.13.4. Therefore, I'm waiting for the script to support the latest version, hoping my issues get resolved by that.

I'm also using Cloudflare Origin certificate, which didn't work anymore. Probably not a coincidence. For the time-being I'm happy using the old version.
I did manage to update my internal Nginx Proxy Manager on Docker.

@jpatje commented on GitHub (Dec 5, 2025): > > [@TheBToby](https://github.com/TheBToby) That's cool, thx! Have you tried updating the certificate? I use DuckDNS and it did not work after I updated the LXC > > OK, I'm now running into issues with my Cloudflare origin certificates as well. It appears that the issue is solved in NPM 2.13.5 but the current update script only updates to 2.13.4. Therefore, I'm waiting for the script to support the latest version, hoping my issues get resolved by that. I'm also using Cloudflare Origin certificate, which didn't work anymore. Probably not a coincidence. For the time-being I'm happy using the old version. I did manage to update my internal Nginx Proxy Manager on Docker.

OVERLORD commented

2026-02-05 03:27:39 +03:00

@TheBToby commented on GitHub (Dec 5, 2025):

NginxProxyManager/nginx-proxy-manager#4957

It could have been resolved long ago, but once again there is no feedback.

Yes, sorry for creating the confusion. My bad. I did not notice that the script was changed to install the previous version 2.13.4. I landed here as I was upgrading from a way older version where the upgrade failed. Now I see that my issue was not related to this issue.
Again, sorry for the confusion!

Providing feedback on the pending issue on NPM is beyond my technical skills, though.

@TheBToby commented on GitHub (Dec 5, 2025): > [NginxProxyManager/nginx-proxy-manager#4957](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4957) > > It could have been resolved long ago, but once again there is no feedback. Yes, sorry for creating the confusion. My bad. I did not notice that the script was changed to install the previous version 2.13.4. I landed here as I was upgrading from a way older version where the upgrade failed. Now I see that my issue was not related to this issue. Again, sorry for the confusion! Providing feedback on the pending issue on NPM is beyond my technical skills, though.

OVERLORD commented

2026-02-05 03:27:42 +03:00

@MickLesk commented on GitHub (Dec 5, 2025):

I don't mean you, but we always find ourselves fighting a losing battle when it comes to issues with NPM. Because we almost never get any feedback. As an alternative, we offer NPMPlus, which is based on an alpine docker, but feels much leaner, faster, and less prone to errors.

https://community-scripts.github.io/ProxmoxVE/scripts?id=npmplus

@MickLesk commented on GitHub (Dec 5, 2025): I don't mean you, but we always find ourselves fighting a losing battle when it comes to issues with NPM. Because we almost never get any feedback. As an alternative, we offer NPMPlus, which is based on an alpine docker, but feels much leaner, faster, and less prone to errors. https://community-scripts.github.io/ProxmoxVE/scripts?id=npmplus

OVERLORD commented

2026-02-05 03:27:46 +03:00

@yuriw commented on GitHub (Dec 5, 2025):

So after I did direct update to trixie I coud not make to update certificate via DuckDNS plugin
I installed a new CT using the new script, added a new cert (DuckDNS) and copied over /data /etc/letsencrypt
And all seems fine so far.

I am a little unclear on how to update this CT, as I see no update script

Any suggestion welcome!

Just FYI

@yuriw commented on GitHub (Dec 5, 2025): So after I did direct update to trixie I coud not make to update certificate via DuckDNS plugin I installed a new CT using the new script, added a new cert (DuckDNS) and copied over /data /etc/letsencrypt And all seems fine so far. I am a little unclear on how to update this CT, as I see no update script Any suggestion welcome! Just FYI

OVERLORD commented

2026-02-05 03:27:48 +03:00

@MickLesk commented on GitHub (Dec 5, 2025):

What? Which Script?

@MickLesk commented on GitHub (Dec 5, 2025): What? Which Script?

OVERLORD commented

2026-02-05 03:27:51 +03:00

@yuriw commented on GitHub (Dec 5, 2025):

the script that updates the NPM CT

@yuriw commented on GitHub (Dec 5, 2025): the script that updates the NPM CT

OVERLORD commented

2026-02-05 03:27:53 +03:00

@MickLesk commented on GitHub (Dec 5, 2025):

Its Always included

@MickLesk commented on GitHub (Dec 5, 2025): Its Always included

OVERLORD commented

2026-02-05 03:27:55 +03:00

@GiladHi commented on GitHub (Dec 8, 2025):

Hi, I just installed NginxProxyManager from scratch using the helper-script on Proxmox version 9.1.2 (latest).

After the installation, I added a custom wildcard certificate. The certificate is working, and I can use it when adding a new proxy, but now when I'm trying to access the certificates tab, I'm just getting a blank page...

The version installed in still 2.13.4, and the update to 2.13.5 doesn't work.

@GiladHi commented on GitHub (Dec 8, 2025): Hi, I just installed NginxProxyManager from scratch using the helper-script on Proxmox version 9.1.2 (latest). After the installation, I added a custom wildcard certificate. The certificate is working, and I can use it when adding a new proxy, but now when I'm trying to access the certificates tab, I'm just getting a blank page... The version installed in still 2.13.4, and the update to 2.13.5 doesn't work.

OVERLORD commented

2026-02-05 03:27:56 +03:00

@BliXem1 commented on GitHub (Dec 8, 2025):

@MickLesk

Hmm NPMPlus you say?

/ | / / __ / |/ /___ / /_ _______
/ |/ / // / /|/ / __ / / / / / /
/ /| / / / / / // / / // ( )
// |// // // .//_,/___/
//
🧩 Using Advanced Install on node proxmox
💡 PVE Version 8.4.14 (Kernel: 6.8.12-15-pve)

✔️ Storage local (Free: 19.2GB Used: 10.7GB) [Template]
✔️ Storage local-lvm (Free: 1.3TB Used: 414.3GB) [Container]
✔️ Storage 'local-lvm' (lvmthin) validated
✔️ Template storage 'local' validated
✔️ Template search completed
✔️ Template alpine-3.22-default_20250617_amd64.tar.xz [online]
✔️ LXC Container 210 was successfully created.
✔️ Started LXC Container
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.0.25
✔️ Internet: ✔ IPv4 DNS: 140.82.121.3
✔️ Updated Container OS
✔️ Installed Dependencies
✖️ in line 24: exit code 2 (Misuse of shell builtins (e.g. syntax error))
→ apk add docker
--- Last 10 lines of silent log ---
(17/21) Installing docker-engine (29.1.1-r0)
Executing docker-engine-29.1.1-r0.pre-install
(18/21) Installing docker-openrc (29.1.1-r0)
ERROR: docker-openrc-29.1.1-r0: HTTP 404: Not Found
(19/21) Installing docker-cli (29.1.1-r0)
(20/21) Installing docker-cli-buildx (0.30.1-r0)
(21/21) Installing docker (29.1.1-r0)
Executing busybox-1.37.0-r29.trigger
Executing ca-certificates-20251003-r0.trigger
2 errors; 251 MiB in 95 packages

📋 View full log (78 lines): /root/.install-4535529d.log
✖️ Installation failed in container 210 (exit code: 2)

✔ Installation log: /tmp/install-lxc-210-4535529d.log

Remove broken container 210? (Y/n) [auto-remove in 60s]: y

Removing container 210
✔️ Container 210 removed

@BliXem1 commented on GitHub (Dec 8, 2025): @MickLesk Hmm NPMPlus you say? / | / / __ \/ |/ /___ / /_ _______ / |/ / /_/ / /|_/ / __ \/ / / / / ___/ / /| / ____/ / / / /_/ / / /_/ (__ ) /_/ |_/_/ /_/ /_/ .___/_/\__,_/____/ /_/ 🧩 Using Advanced Install on node proxmox 💡 PVE Version 8.4.14 (Kernel: 6.8.12-15-pve) ✔️ Storage local (Free: 19.2GB Used: 10.7GB) [Template] ✔️ Storage local-lvm (Free: 1.3TB Used: 414.3GB) [Container] ✔️ Storage 'local-lvm' (lvmthin) validated ✔️ Template storage 'local' validated ✔️ Template search completed ✔️ Template alpine-3.22-default_20250617_amd64.tar.xz [online] ✔️ LXC Container 210 was successfully created. ✔️ Started LXC Container ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.0.25 ✔️ Internet: ✔ IPv4 DNS: 140.82.121.3 ✔️ Updated Container OS ✔️ Installed Dependencies ✖️ in line 24: exit code 2 (Misuse of shell builtins (e.g. syntax error)) → apk add docker --- Last 10 lines of silent log --- (17/21) Installing docker-engine (29.1.1-r0) Executing docker-engine-29.1.1-r0.pre-install (18/21) Installing docker-openrc (29.1.1-r0) ERROR: docker-openrc-29.1.1-r0: HTTP 404: Not Found (19/21) Installing docker-cli (29.1.1-r0) (20/21) Installing docker-cli-buildx (0.30.1-r0) (21/21) Installing docker (29.1.1-r0) Executing busybox-1.37.0-r29.trigger Executing ca-certificates-20251003-r0.trigger 2 errors; 251 MiB in 95 packages ----------------------------------- 📋 View full log (78 lines): /root/.install-4535529d.log ✖️ Installation failed in container 210 (exit code: 2) ✔ Installation log: /tmp/install-lxc-210-4535529d.log Remove broken container 210? (Y/n) [auto-remove in 60s]: y Removing container 210 ✔️ Container 210 removed

OVERLORD commented

2026-02-05 03:28:01 +03:00

@BliXem1 commented on GitHub (Dec 8, 2025):

And I can't update too 2.13.5 either.

@BliXem1 commented on GitHub (Dec 8, 2025): And I can't update too 2.13.5 either.

OVERLORD commented

2026-02-05 03:28:03 +03:00

@MickLesk commented on GitHub (Dec 8, 2025):

your host is to old for the new docker. Only 9.0+ with latest app armor fixes.

@MickLesk commented on GitHub (Dec 8, 2025): your host is to old for the new docker. Only 9.0+ with latest app armor fixes.

OVERLORD commented

2026-02-05 03:28:05 +03:00

@TheBToby commented on GitHub (Dec 8, 2025):

I don't mean you, but we always find ourselves fighting a losing battle when it comes to issues with NPM. Because we almost never get any feedback. As an alternative, we offer NPMPlus, which is based on an alpine docker, but feels much leaner, faster, and less prone to errors.

https://community-scripts.github.io/ProxmoxVE/scripts?id=npmplus

I migrated to NPMplus (manually created new hosts as copy/paste did not work easily) → working fine so far!

@TheBToby commented on GitHub (Dec 8, 2025): > I don't mean you, but we always find ourselves fighting a losing battle when it comes to issues with NPM. Because we almost never get any feedback. As an alternative, we offer NPMPlus, which is based on an alpine docker, but feels much leaner, faster, and less prone to errors. > > https://community-scripts.github.io/ProxmoxVE/scripts?id=npmplus I migrated to NPMplus (manually created new hosts as copy/paste did not work easily) → working fine so far!

OVERLORD commented

2026-02-05 03:28:08 +03:00

@tremor021 commented on GitHub (Dec 8, 2025):

@BliXem1

@MickLesk

Hmm NPMPlus you say?

My granny always said that sometime you should remain quiet if you don't know what you're doing... :)

@tremor021 commented on GitHub (Dec 8, 2025): @BliXem1 > [@MickLesk](https://github.com/MickLesk) > > Hmm NPMPlus you say? My granny always said that sometime you should remain quiet if you don't know what you're doing... :)

OVERLORD commented

2026-02-05 03:28:16 +03:00

@GiladHi commented on GitHub (Dec 8, 2025):

It seems like the NPMPlus is based on NPM version 2.12.3, which it quite an old release...

@GiladHi commented on GitHub (Dec 8, 2025): It seems like the NPMPlus is based on NPM version 2.12.3, which it quite an old release...

OVERLORD commented

2026-02-05 03:28:19 +03:00

@durzo commented on GitHub (Dec 26, 2025):

For those considering migrating to NPMPlus, be aware that the maintainer has chosen to remove CloudFlare and AWS support from both ACME and realip. this was a deal breaker for me and keeps me using standard NPM.

@durzo commented on GitHub (Dec 26, 2025): For those considering migrating to NPMPlus, be aware that the maintainer has chosen to remove CloudFlare and AWS support from both ACME and realip. this was a deal breaker for me and keeps me using standard NPM.

OVERLORD commented

2026-02-05 03:28:23 +03:00

@durzo commented on GitHub (Dec 26, 2025):

I'm running 2.13.5 with fix from #10340 without issue, tested upgrading from 2.13.4 and fresh install.

@durzo commented on GitHub (Dec 26, 2025): I'm running 2.13.5 with fix from #10340 without issue, tested upgrading from 2.13.4 and fresh install.

OVERLORD commented

2026-02-05 03:28:29 +03:00

@CrazyWolf13 commented on GitHub (Dec 26, 2025):

@durzo any idea why they removed ACME support for cloudflare? Cloudflare is one of the bigger players for domains?

@CrazyWolf13 commented on GitHub (Dec 26, 2025): @durzo any idea why they removed ACME support for cloudflare? Cloudflare is one of the bigger players for domains?

OVERLORD commented

2026-02-05 03:28:34 +03:00

@durzo commented on GitHub (Dec 26, 2025):

@CrazyWolf13 Its mentioned in the README.md, and I asked here: https://github.com/ZoeyVid/NPMplus/discussions/2400

Looks like CloudFlare works for now, but will be disabled in the future while AWS (Route53/CloudFront) are already disabled.

It would not be my choice to remove support for arguably the biggest cloud providers in the world, but one has to respect the wishes of the project maintainer. For me and many others, this means simply not adopting NPM Plus, and instead using something like Zoraxy, Caddy, Traefik, or continue using NPM which works fine, but I wanted to deploy CrowdSec in my network which NPM Plus has out of the box.

@durzo commented on GitHub (Dec 26, 2025): @CrazyWolf13 Its mentioned in the README.md, and I asked here: https://github.com/ZoeyVid/NPMplus/discussions/2400 Looks like CloudFlare works for now, but will be disabled in the future while AWS (Route53/CloudFront) are already disabled. It would not be my choice to remove support for arguably the biggest cloud providers in the world, but one has to respect the wishes of the project maintainer. For me and many others, this means simply not adopting NPM Plus, and instead using something like Zoraxy, Caddy, Traefik, or continue using NPM which works fine, but I wanted to deploy CrowdSec in my network which NPM Plus has out of the box.

OVERLORD commented

2026-02-05 03:28:36 +03:00

@kwetnico commented on GitHub (Dec 26, 2025):

@CrazyWolf13 Its mentioned in the README.md, and I asked here: ZoeyVid/NPMplus#2400

Looks like CloudFlare works for now, but will be disabled in the future while AWS (Route53/CloudFront) are already disabled.

It would not be my choice to remove support for arguably the biggest cloud providers in the world, but one has to respect the wishes of the project maintainer. For me and many others, this means simply not adopting NPM Plus, and instead using something like Zoraxy, Caddy, Traefik, or continue using NPM which works fine, but I wanted to deploy CrowdSec in my network which NPM Plus has out of the box.

I can't update my version to NPM (always : 2.13.4.. :( )

@kwetnico commented on GitHub (Dec 26, 2025): > [@CrazyWolf13](https://github.com/CrazyWolf13) Its mentioned in the README.md, and I asked here: [ZoeyVid/NPMplus#2400](https://github.com/ZoeyVid/NPMplus/discussions/2400) > > Looks like CloudFlare works for now, but will be disabled in the future while AWS (Route53/CloudFront) are already disabled. > > It would not be my choice to remove support for arguably the biggest cloud providers in the world, but one has to respect the wishes of the project maintainer. For me and many others, this means simply not adopting NPM Plus, and instead using something like Zoraxy, Caddy, Traefik, or continue using NPM which works fine, but I wanted to deploy CrowdSec in my network which NPM Plus has out of the box. I can't update my version to NPM (always : 2.13.4.. :( ) <img width="702" height="362" alt="Image" src="https://github.com/user-attachments/assets/c5968795-12de-4a1c-8282-a3fce027faf2" />

OVERLORD commented

2026-02-05 03:28:47 +03:00

@CrazyWolf13 commented on GitHub (Dec 26, 2025):

@kwetnico the pr is not merged, is it?

@CrazyWolf13 commented on GitHub (Dec 26, 2025): @kwetnico the pr is not merged, is it?

OVERLORD commented

2026-02-05 03:28:49 +03:00

@kwetnico commented on GitHub (Dec 26, 2025):

@kwetnico the pr is not merged, is it?

ok :( thanks i will wait)

@kwetnico commented on GitHub (Dec 26, 2025): > [@kwetnico](https://github.com/kwetnico) the pr is not merged, is it? ok :( thanks i will wait)

OVERLORD commented

2026-02-05 03:28:52 +03:00

@CrazyWolf13 commented on GitHub (Dec 26, 2025):

@durzo I was kinda frustrated by the lack of attention NPM is getting and also didn't like the hacky NPMPlus, so far I've been mostly happy with zoraxy, some quirks I'm helping to resolve like OPNsense support and authentik forward auth, but once those are fully implemented it's a much better solution compared to NPM

@CrazyWolf13 commented on GitHub (Dec 26, 2025): @durzo I was kinda frustrated by the lack of attention NPM is getting and also didn't like the hacky NPMPlus, so far I've been mostly happy with zoraxy, some quirks I'm helping to resolve like OPNsense support and authentik forward auth, but once those are fully implemented it's a much better solution compared to NPM

OVERLORD commented

2026-02-05 03:28:55 +03:00

@durzo commented on GitHub (Dec 26, 2025):

@kwetnico if you cant wait for merge, you can run the script from my repo inside your NPM lxc to update to 2.13.5 (this is not official, do not run if you do not trust me):

bash -c "$(curl -fsSL https://raw.githubusercontent.com/durzo/ProxmoxVE/refs/heads/durzo-patch-1/ct/nginxproxymanager.sh)"

@durzo commented on GitHub (Dec 26, 2025): @kwetnico if you cant wait for merge, you can run the script from my repo inside your NPM lxc to update to 2.13.5 (this is not official, do not run if you do not trust me): ``` bash -c "$(curl -fsSL https://raw.githubusercontent.com/durzo/ProxmoxVE/refs/heads/durzo-patch-1/ct/nginxproxymanager.sh)" ```

OVERLORD commented

2026-02-05 03:29:01 +03:00

@durzo commented on GitHub (Dec 26, 2025):

@CrazyWolf13 I really like Zoraxy too, it would probably help if it was listed under "Webservers & Proxies" instead of "Network & Firewalls" like all the other reverse proxies

@durzo commented on GitHub (Dec 26, 2025): @CrazyWolf13 I really like Zoraxy too, it would probably help if it was listed under "Webservers & Proxies" instead of "Network & Firewalls" like all the other reverse proxies

OVERLORD commented

2026-02-05 03:29:05 +03:00

@CrazyWolf13 commented on GitHub (Dec 26, 2025):

PR is up:
https://github.com/community-scripts/ProxmoxVE/pull/10344

@CrazyWolf13 commented on GitHub (Dec 26, 2025): PR is up: https://github.com/community-scripts/ProxmoxVE/pull/10344

OVERLORD commented

2026-02-05 03:29:08 +03:00

@kwetnico commented on GitHub (Dec 26, 2025):

PR is up: #10344

same version :

@kwetnico commented on GitHub (Dec 26, 2025): > PR is up: [#10344](https://github.com/community-scripts/ProxmoxVE/pull/10344) same version : <img width="613" height="256" alt="Image" src="https://github.com/user-attachments/assets/17f46ef0-1473-4b64-b13d-a5875ecf5678" />

OVERLORD commented

2026-02-05 03:29:11 +03:00

@durzo commented on GitHub (Dec 26, 2025):

#10344 is for zoraxy, not NPM - we are just hijacking this bug thread, sorry!

@durzo commented on GitHub (Dec 26, 2025): #10344 is for zoraxy, not NPM - we are just hijacking this bug thread, sorry!

OVERLORD commented

2026-02-05 03:29:18 +03:00

@MickLesk commented on GitHub (Dec 26, 2025):

i know that the line fix it, but i dont want to merge it, because there maintainer doesnt respond and change the build path in dockerfile. So next release it break again

@MickLesk commented on GitHub (Dec 26, 2025): i know that the line fix it, but i dont want to merge it, because there maintainer doesnt respond and change the build path in dockerfile. So next release it break again

OVERLORD commented

2026-02-05 03:29:23 +03:00

@durzo commented on GitHub (Dec 27, 2025):

@CrazyWolf13 my updated PR is waiting on 1 more review, if you would be so kind :)

@durzo commented on GitHub (Dec 27, 2025): @CrazyWolf13 my updated PR is waiting on 1 more review, if you would be so kind :)

OVERLORD commented

2026-02-05 03:29:29 +03:00

@durzo commented on GitHub (Dec 27, 2025):

@kwetnico PR is merged, should work for you now

@durzo commented on GitHub (Dec 27, 2025): @kwetnico PR is merged, should work for you now

OVERLORD commented

2026-02-05 03:29:32 +03:00

@kwetnico commented on GitHub (Dec 27, 2025):

@kwetnico PR is merged, should work for you now

Yes thanks it's better 👍

@kwetnico commented on GitHub (Dec 27, 2025): > [@kwetnico](https://github.com/kwetnico) PR is merged, should work for you now Yes thanks it's better 👍 <img width="661" height="368" alt="Image" src="https://github.com/user-attachments/assets/e407667b-ce84-465b-9326-d794443a07c8" />

OVERLORD commented

2026-02-05 03:29:34 +03:00

@Atylaking commented on GitHub (Dec 31, 2025):

🧩 Using Advanced Install on node proxmox
💡 PVE Version 9.1.4 (Kernel: 6.17.4-1-pve)

💡 PVE Version 9.1.4 (Kernel: 6.17.4-1-pve)
🖥️ Operating System: debian
🌟 Version: 13
📦 Container Type: Unprivileged
🆔 Container ID: 105
🏠 Hostname: nginxproxymanager
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IPv4: 192.168.2.205/24
📡 IPv6: disable
🗂️ FUSE Support: no
📡 TUN/TAP Support: yes
📦 Nesting: Enabled
🎮 GPU Passthrough: no
💡 Timezone: America/Argentina/Buenos_Aires
🔍 Verbose Mode: no
🚀 Creating a Nginx Proxy Manager LXC using the above advanced settings
✔️ Storage local (Free: 69.8GB Used: 17.3GB) [Template]
✔️ Storage local-lvm (Free: 270.9GB Used: 41.3GB) [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
✔️ Set up Container OS
✔️ Network Connected: 192.168.2.205
✔️ 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
✔️ Installed Python Dependencies
✔️ Set up Certbot
✔️ Installed Openresty
✔️ Setup Node.js 22
✔️ Installed Node.js modules: yarn
✔️ Deployed: nginxproxymanager (2.13.5)
✔️ Set up Environment
✔️ Built Frontend
✖️ in line 144: exit code 1 (General error / Operation not permitted)
→ yarn install --network-timeout 600000
--- Last 10 lines of silent log ---
gyp ERR! stack at ChildProcess.onCpExit (/app/node_modules/node-gyp/lib/configure.js:259:16)
gyp ERR! stack at ChildProcess.emit (node:events:519:28)
gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)
gyp ERR! System Linux 6.17.4-1-pve
gyp ERR! command "/usr/bin/node" "/app/node_modules/sqlite3/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /app/node_modules/sqlite3
gyp ERR! node -v v22.21.0
gyp ERR! node-gyp -v v8.4.1
gyp ERR! not ok
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

This happend to me using this script: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"

@Atylaking commented on GitHub (Dec 31, 2025): 🧩 Using Advanced Install on node proxmox 💡 PVE Version 9.1.4 (Kernel: 6.17.4-1-pve) 💡 PVE Version 9.1.4 (Kernel: 6.17.4-1-pve) 🖥️ Operating System: debian 🌟 Version: 13 📦 Container Type: Unprivileged 🆔 Container ID: 105 🏠 Hostname: nginxproxymanager 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IPv4: 192.168.2.205/24 📡 IPv6: disable 🗂️ FUSE Support: no 📡 TUN/TAP Support: yes 📦 Nesting: Enabled 🎮 GPU Passthrough: no 💡 Timezone: America/Argentina/Buenos_Aires 🔍 Verbose Mode: no 🚀 Creating a Nginx Proxy Manager LXC using the above advanced settings ✔️ Storage local (Free: 69.8GB Used: 17.3GB) [Template] ✔️ Storage local-lvm (Free: 270.9GB Used: 41.3GB) [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 ✔️ Set up Container OS ✔️ Network Connected: 192.168.2.205 ✔️ 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 ✔️ Installed Python Dependencies ✔️ Set up Certbot ✔️ Installed Openresty ✔️ Setup Node.js 22 ✔️ Installed Node.js modules: yarn ✔️ Deployed: nginxproxymanager (2.13.5) ✔️ Set up Environment ✔️ Built Frontend ✖️ in line 144: exit code 1 (General error / Operation not permitted) → yarn install --network-timeout 600000 --- Last 10 lines of silent log --- gyp ERR! stack at ChildProcess.onCpExit (/app/node_modules/node-gyp/lib/configure.js:259:16) gyp ERR! stack at ChildProcess.emit (node:events:519:28) gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12) gyp ERR! System Linux 6.17.4-1-pve gyp ERR! command "/usr/bin/node" "/app/node_modules/sqlite3/node_modules/.bin/node-gyp" "rebuild" gyp ERR! cwd /app/node_modules/sqlite3 gyp ERR! node -v v22.21.0 gyp ERR! node-gyp -v v8.4.1 gyp ERR! not ok info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. This happend to me using this script: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nginxproxymanager.sh)"

OVERLORD commented

2026-02-05 03:29:40 +03:00

@MickLesk commented on GitHub (Dec 31, 2025):

Read Error and you See Network timeouts

@MickLesk commented on GitHub (Dec 31, 2025): Read Error and you See Network timeouts

OVERLORD referenced this issue

2026-02-05 05:41:31 +03:00

[PR #2026] [MERGED] [Github Action] Update CHANGELOG.md #3359

Sign in to join this conversation.

Branches Tags

main

github-action-update-changelog

pr-update-app-files

docker_deb13

feat/cloudinit-sshkeys

feat/sqlserver2025

automated/update-github-versions

add-script-opencloud-1770212555

add-script-openclaw-1770212634

github-action-archive-changelog

update_apps_tool

add-script-wishlist-1770193085

MickLesk-patch-2

add-script-writefreely-1770188758

add-script-wealthfolio-1770143943

fix/vaultwarden-update-script

remove_memos

disable_npm

feature/codeberg-functions-forgejo-readeck

add-script-rustypaste-1770019426

add-script-kitchenowl-1770017260

fix/2fauth-php-version

tools_func_addcodeberg

CrazyWolf13-patch-2

add-script-shelfmark-1769790178

CrazyWolf13-patch-1

add-script-ampache-1769790139

add-script-languagetool-1769790155

remove_php_deps

ref_koilection

fix/php-module-improvements

tremor021-patch-1

fix/open-archiver-meilisearch-migration

cloudflare_dns

MickLesk-patch-1

michelroegl-brunner-patch-2

fix/version-display

fix/debian13-root-ownership

feat/interactive_prompts

feature/smart-error-recovery

core_stable

update_docs

refactor/tools-func-stability

certbot_npm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2026