#815 - [GH-ISSUE #3896] Nginx Proxy Manager - update [ERROR] in line 1459 - starred/ProxmoxVE

kerem commented

2026-02-26 12:46:46 +03:00

Owner

Originally created by @artemdanielov on GitHub (Apr 15, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3896

✅ Have you read and understood the above guidelines?

yes

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

Nginx Proxy Manager

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

📝 Provide a clear and concise description of the issue.

Hello!
After trying to update NPN using "Update" command or script, the NPM does not work anymore and i cant access web ui or update the LXC.

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Open LXC console, type Update or execute script.

❌ Paste the full error output (if available).

⠧ Building Frontendcurl: (22) The requested URL returned error: 400
[ERROR] in line 1459: exit code 0: while executing command "$@" >> "$LOGFILE" 2>&1

🖼️ Additional context (optional).

No response

Originally created by @artemdanielov on GitHub (Apr 15, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3896 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Nginx Proxy Manager ### 📂 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)" ### 📝 Provide a clear and concise description of the issue. Hello! After trying to update NPN using "Update" command or script, the NPM does not work anymore and i cant access web ui or update the LXC. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Open LXC console, type Update or execute script. ### ❌ Paste the full error output (if available). ⠧ Building Frontendcurl: (22) The requested URL returned error: 400 [ERROR] in line 1459: exit code 0: while executing command "$@" >> "$LOGFILE" 2>&1 ![Image](https://github.com/user-attachments/assets/072db2e9-cca5-429d-8061-a4c5b0dcb0d3) ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:46:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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

run as verbose. it breaks because /frontend folder is not found

@MickLesk commented on GitHub (Apr 15, 2025): run as verbose. it breaks because /frontend folder is not found

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@artemdanielov commented on GitHub (Apr 15, 2025):

run as verbose

how do i do that?

/frontend folder is not found

is there a way to fix it? it was working fine before i tried to update

@artemdanielov commented on GitHub (Apr 15, 2025): > run as verbose how do i do that? > /frontend folder is not found is there a way to fix it? it was working fine before i tried to update

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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

choose it in update dialogue...

@MickLesk commented on GitHub (Apr 15, 2025): choose it in update dialogue...

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@artemdanielov commented on GitHub (Apr 15, 2025):

so i got this at the end:

⠴ Building Frontend+ spin_i=6
+ sleep 0.1
++ kill 6608
++ printf '\e[?25h'
++ local exit_code=0
++ local line_number=1459
++ local 'command="$@" >> "$LOGFILE" 2>&1'
++ local 'error_message=\033[01;31m[ERROR]\033[m in line \033[01;31m1459\033[m: exit code \033[01;31m0\033[m: while executing command \033[33m"$@" >> "$LOGFILE" 2>&1\033[m'
++ post_update_to_api failed '"$@" >> "$LOGFILE" 2>&1'
++ command -v curl
++ '[' false = true ']'
++ local API_URL=http://api.community-scripts.org/upload/updatestatus
++ local status=failed
++ local 'error="$@" >> "$LOGFILE" 2>&1'
{
    "status": "$status",
    "error": "$error",
    "random_id": "$RANDOM_UUID"
}
EOF
+++ cat
++ JSON_PAYLOAD='{
    "status": "failed",
    "error": ""$@" >> "$LOGFILE" 2>&1",
    "random_id": "b8f8abb7-d614-4dbc-91ae-1c0df88c7873"
}'
+++ curl -fsSL -w '%{http_code}' -L -X POST http://api.community-scripts.org/upload/updatestatus --post301 --post302 -H 'Content-Type: application/json' -d '{
    "status": "failed",
    "error": ""$@" >> "$LOGFILE" 2>&1",
    "random_id": "b8f8abb7-d614-4dbc-91ae-1c0df88c7873"
}'
curl: (22) The requested URL returned error: 400
++ RESPONSE=400
++ true
++ POST_UPDATE_DONE=true
++ echo -e '\n\033[01;31m[ERROR]\033[m in line \033[01;31m1459\033[m: exit code \033[01;31m0\033[m: while executing command \033[33m"$@" >> "$LOGFILE" 2>&1\033[m\n'

[ERROR] in line 1459: exit code 0: while executing command "$@" >> "$LOGFILE" 2>&1

@artemdanielov commented on GitHub (Apr 15, 2025): so i got this at the end: ``` ⠴ Building Frontend+ spin_i=6 + sleep 0.1 ++ kill 6608 ++ printf '\e[?25h' ++ local exit_code=0 ++ local line_number=1459 ++ local 'command="$@" >> "$LOGFILE" 2>&1' ++ local 'error_message=\033[01;31m[ERROR]\033[m in line \033[01;31m1459\033[m: exit code \033[01;31m0\033[m: while executing command \033[33m"$@" >> "$LOGFILE" 2>&1\033[m' ++ post_update_to_api failed '"$@" >> "$LOGFILE" 2>&1' ++ command -v curl ++ '[' false = true ']' ++ local API_URL=http://api.community-scripts.org/upload/updatestatus ++ local status=failed ++ local 'error="$@" >> "$LOGFILE" 2>&1' { "status": "$status", "error": "$error", "random_id": "$RANDOM_UUID" } EOF +++ cat ++ JSON_PAYLOAD='{ "status": "failed", "error": ""$@" >> "$LOGFILE" 2>&1", "random_id": "b8f8abb7-d614-4dbc-91ae-1c0df88c7873" }' +++ curl -fsSL -w '%{http_code}' -L -X POST http://api.community-scripts.org/upload/updatestatus --post301 --post302 -H 'Content-Type: application/json' -d '{ "status": "failed", "error": ""$@" >> "$LOGFILE" 2>&1", "random_id": "b8f8abb7-d614-4dbc-91ae-1c0df88c7873" }' curl: (22) The requested URL returned error: 400 ++ RESPONSE=400 ++ true ++ POST_UPDATE_DONE=true ++ echo -e '\n\033[01;31m[ERROR]\033[m in line \033[01;31m1459\033[m: exit code \033[01;31m0\033[m: while executing command \033[33m"$@" >> "$LOGFILE" 2>&1\033[m\n' [ERROR] in line 1459: exit code 0: while executing command "$@" >> "$LOGFILE" 2>&1 ```

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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

whats that? How you run the scripts? Never seen such formatting before

@MickLesk commented on GitHub (Apr 15, 2025): whats that? How you run the scripts? Never seen such formatting before

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@artemdanielov commented on GitHub (Apr 15, 2025):

and this if turning verbous in update dialog:

ERROR in ./scss/styles.scss
Module build failed (from ./node_modules/.pnpm/mini-css-extract-plugin@0.9.0_webpack@4.47.0/node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleError: Module Error (from ./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js):
Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (127)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v9.0.0
    at Object.emitError (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/webpack@4.47.0_webpack-cli@3.3.12/node_modules/webpack/lib/NormalModule.js:173:6)
    at getSassImplementation (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/utils.js:53:21)
    at Object.loader (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/index.js:27:59)
 @ ./js/index.js 2:0-29
Child HtmlWebpackCompiler:
     2 assets
    Entrypoint HtmlWebpackPlugin_0 = __child-HtmlWebpackPlugin_0
    Entrypoint HtmlWebpackPlugin_1 = __child-HtmlWebpackPlugin_1
    [0] ./node_modules/.pnpm/ejs-webpack-loader@2.2.2/node_modules/ejs-webpack-loader!./html/index.ejs 6.53 KiB {0} [built]
    [1] ./node_modules/.pnpm/ejs-webpack-loader@2.2.2/node_modules/ejs-webpack-loader!./html/login.ejs 6.7 KiB {1} [built]
Child mini-css-extract-plugin node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!scss/styles.scss:
    Entrypoint mini-css-extract-plugin = *
    [0] ./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!./scss/styles.scss 1.05 KiB {0} [built] [failed] [2 errors]
    
    ERROR in ./scss/styles.scss (./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!./scss/styles.scss)
    Module Error (from ./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js):
    Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (127)
    For more information on which environments are supported please see:
    https://github.com/sass/node-sass/releases/tag/v9.0.0
    
    ERROR in ./scss/styles.scss (./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!./scss/styles.scss)
    Module build failed (from ./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js):
    Error: PostCSS received undefined instead of CSS string
        at new Input (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/input.js:38:13)
        at parse (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/parse.js:13:15)
        at new LazyResult (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/lazy-result.js:64:16)
        at Processor.<anonymous> (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/processor.js:142:12)
        at Processor.process (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/processor.js:121:23)
        at Object.loader (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/index.js:83:34)
 ELIFECYCLE  Command failed with exit code 2.
⠦ Building Frontend
[ERROR] in line 109: exit code 0: while executing command $STD pnpm run build

@artemdanielov commented on GitHub (Apr 15, 2025): and this if turning verbous in update dialog: ``` ERROR in ./scss/styles.scss Module build failed (from ./node_modules/.pnpm/mini-css-extract-plugin@0.9.0_webpack@4.47.0/node_modules/mini-css-extract-plugin/dist/loader.js): ModuleError: Module Error (from ./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js): Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (127) For more information on which environments are supported please see: https://github.com/sass/node-sass/releases/tag/v9.0.0 at Object.emitError (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/webpack@4.47.0_webpack-cli@3.3.12/node_modules/webpack/lib/NormalModule.js:173:6) at getSassImplementation (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/utils.js:53:21) at Object.loader (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/index.js:27:59) @ ./js/index.js 2:0-29 Child HtmlWebpackCompiler: 2 assets Entrypoint HtmlWebpackPlugin_0 = __child-HtmlWebpackPlugin_0 Entrypoint HtmlWebpackPlugin_1 = __child-HtmlWebpackPlugin_1 [0] ./node_modules/.pnpm/ejs-webpack-loader@2.2.2/node_modules/ejs-webpack-loader!./html/index.ejs 6.53 KiB {0} [built] [1] ./node_modules/.pnpm/ejs-webpack-loader@2.2.2/node_modules/ejs-webpack-loader!./html/login.ejs 6.7 KiB {1} [built] Child mini-css-extract-plugin node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!scss/styles.scss: Entrypoint mini-css-extract-plugin = * [0] ./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!./scss/styles.scss 1.05 KiB {0} [built] [failed] [2 errors] ERROR in ./scss/styles.scss (./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!./scss/styles.scss) Module Error (from ./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js): Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (127) For more information on which environments are supported please see: https://github.com/sass/node-sass/releases/tag/v9.0.0 ERROR in ./scss/styles.scss (./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js!./node_modules/.pnpm/sass-loader@10.5.2_node-sass@9.0.0_webpack@4.47.0/node_modules/sass-loader/dist/cjs.js!./scss/styles.scss) Module build failed (from ./node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/cjs.js): Error: PostCSS received undefined instead of CSS string at new Input (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/input.js:38:13) at parse (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/parse.js:13:15) at new LazyResult (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/lazy-result.js:64:16) at Processor.<anonymous> (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/processor.js:142:12) at Processor.process (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/postcss@7.0.39/node_modules/postcss/lib/processor.js:121:23) at Object.loader (/root/nginx-proxy-manager-2.12.3/frontend/node_modules/.pnpm/css-loader@3.6.0_webpack@4.47.0/node_modules/css-loader/dist/index.js:83:34) ELIFECYCLE Command failed with exit code 2. ⠦ Building Frontend [ERROR] in line 109: exit code 0: while executing command $STD pnpm run build ```

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@artemdanielov commented on GitHub (Apr 15, 2025):

whats that? How you run the scripts? Never seen such formatting before

sorry, that was verbose mode of bash (-vx)

@artemdanielov commented on GitHub (Apr 15, 2025): > whats that? How you run the scripts? Never seen such formatting before sorry, that was verbose mode of bash (-vx)

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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

it failed because pnpm. its not the first time in this script. That issue is known since maybe over an half year, but there is no newer version

@MickLesk commented on GitHub (Apr 15, 2025): it failed because pnpm. its not the first time in this script. That issue is known since maybe over an half year, but there is no newer version

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@artemdanielov commented on GitHub (Apr 15, 2025):

it failed because pnpm. its not the first time in this script. That issue is known since maybe over an half year, but there is no newer version

but how do i fix my lxc now? it starts up, console is working, but Nginx itself is not - cant access web ui, and proxy is not working..

@artemdanielov commented on GitHub (Apr 15, 2025): > it failed because pnpm. its not the first time in this script. That issue is known since maybe over an half year, but there is no newer version but how do i fix my lxc now? it starts up, console is working, but Nginx itself is not - cant access web ui, and proxy is not working..

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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

Backup? Snapshot?

or try this:
cd in your npm-folder/frontend and do fllowing:

pnpm install
pnpm upgrade
pnpm run build
cp -r dist/* /app/frontend
cp -r app-images/* /app/frontend/images

@MickLesk commented on GitHub (Apr 15, 2025): Backup? Snapshot? or try this: cd in your npm-folder/frontend and do fllowing: ```bash pnpm install pnpm upgrade pnpm run build cp -r dist/* /app/frontend cp -r app-images/* /app/frontend/images ```

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@artemdanielov commented on GitHub (Apr 15, 2025):

pnpm install
pnpm upgrade
pnpm run build
cp -r dist/* /app/frontend
cp -r app-images/* /app/frontend/images

didn't work, same errors.
so i just recovered lxc from back up. nether updating it again lol...

@artemdanielov commented on GitHub (Apr 15, 2025): > pnpm install > pnpm upgrade > pnpm run build > cp -r dist/* /app/frontend > cp -r app-images/* /app/frontend/images didn't work, same errors. so i just recovered lxc from back up. nether updating it again lol...

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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

better is not in the next time ^^ latest release is about 2month her and has more bugs then before..

@MickLesk commented on GitHub (Apr 15, 2025): better is not in the next time ^^ latest release is about 2month her and has more bugs then before..

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

@stevester-codes commented on GitHub (Apr 19, 2025):

Same issue, was this fixed?

@stevester-codes commented on GitHub (Apr 19, 2025): Same issue, was this fixed?

kerem commented

2026-02-26 12:46:46 +03:00

Author

Owner

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