starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 01:36:05 +03:00

[GH-ISSUE #7887] NPMPlus gives Internal Errors when editing or adding proxy hosts #1668

New issue

Closed

opened 2026-02-26 12:49:48 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:49:48 +03:00

Owner

Originally created by @Drakonas on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7887

✅ Have you read and understood the above guidelines?

yes

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

NPMplus

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

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

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Alpine

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve)

📝 Provide a clear and concise description of the issue.

I created a fresh LXC without migrating, created my new credentials successfully, and started adding the proxy hosts by putting everything in manually, including the custom nginx configs for a couple of them. After a few entries, now when I add or edit any entry, I get an Internal Error in the popup.

After cancelling, nothing shows. Before, if I would immediately refresh the page, the entry shows up with "Unknown" status.

However, when attempting to reproduce just now, it wouldn't refresh at all. The nginx process seems to have just completely crashed instead. The server is offline after clicking Save.

Before, when it refreshed, if I tried to delete the entry it gave an error stating something like "Error: Does not exist: 7" or something like that. I cannot recall exactly.

I looked up the docker logs and this shows up a lot:

2025/09/24 12:10:10 [alert] 2662#2662: sched_setaffinity() failed (22: Invalid argument)
2025/09/24 12:10:10 [alert] 2695#2695: sched_setaffinity() failed (22: Invalid argument)

You can see more troubleshooting in this discussion.

🔄 Steps to reproduce the issue.

Step 1: Run the ProxmoxVE community script from the node's Shell. Use all defaults, set the timezone and ACME email.
Step 2: Use the created /opt/.npm-pw file's credentials to sign in, change the username, full name, email, and password.
Step 3: Start creating entries. A couple I've made have custom nginx configurations in the Advanced tab. I've supplied two here:

proxy_pass_header Authorization;
proxy_pass_header Server;
proxy_redirect off;
proxy_buffering off;
client_max_body_size 0;
proxy_read_timeout 36000s;

location = /.well-known/carddav {
    return 301 $scheme://$host:$server_port/remote.php/dav;
}
location = /.well-known/caldav {
    return 301 $scheme://$host:$server_port/remote.php/dav;
}

location / {
    proxy_pass $forward_scheme://$server:$port;  # Or whatever local IP and port ADS is listening on
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header X-AMP-Scheme $scheme;
    proxy_read_timeout 86400s;
    proxy_send_timeout 86400s;
    proxy_http_version 1.1;
    proxy_redirect off;
    proxy_buffering off;
    proxy_cookie_path / "/; Secure";
    client_max_body_size 10240M;

    ## Trusted Proxies Configuration
    ## Cloudflare Cloud IP Address Ranges https://www.cloudflare.com/ips/
    ## https://support.cloudflare.com/hc/en-us/articles/200170786-Restoring-original-visitor-IPs#S7Z4EJQFN997YRY
    set_real_ip_from 173.245.48.0/20;
    set_real_ip_from 103.21.244.0/22;
    set_real_ip_from 103.22.200.0/22;
    set_real_ip_from 103.31.4.0/22;
    set_real_ip_from 141.101.64.0/18;
    set_real_ip_from 108.162.192.0/18;
    set_real_ip_from 190.93.240.0/20;
    set_real_ip_from 188.114.96.0/20;
    set_real_ip_from 197.234.240.0/22;
    set_real_ip_from 198.41.128.0/17;
    set_real_ip_from 162.158.0.0/15;
    set_real_ip_from 104.16.0.0/13;
    set_real_ip_from 104.24.0.0/14;
    set_real_ip_from 172.64.0.0/13;
    set_real_ip_from 131.0.72.0/22;
    set_real_ip_from 2400:cb00::/32;
    set_real_ip_from 2606:4700::/32;
    set_real_ip_from 2803:f800::/32;
    set_real_ip_from 2405:b500::/32;
    set_real_ip_from 2405:8100::/32;
    set_real_ip_from 2a06:98c0::/29;
    set_real_ip_from 2c0f:f248::/32;
    real_ip_header CF-Connecting-IP;
    real_ip_recursive on;
}

Step 4: At some point creating one will fail with an Internal Error and nginx may or may not simply crash.
Step 5: Now creating any proxy host will fail even if the entire LXC is rebooted or the docker compose redeployed.

Step 6: Also, usually when the crash occurs, the entire console freezes, and the LXC CPU and memory max out at 100% as if the entire LXC is spiking with an infinite loop or memory leak.

❌ Paste the full error output (if available).

With the original LXC, nginx simply got killed after saving an entry.

2025-09-23T21:21:52.379888824Z  [Global   ] › ⬤  debug     CMD: nginx -tq
2025-09-23T21:21:53.754819908Z  [Global   ] › ⬤  debug     CMD: nginx -tq
2025-09-23T21:21:55.098685358Z  [Nginx    ] › ℹ  info      Reloading Nginx
2025-09-23T21:21:55.098977353Z  [Global   ] › ⬤  debug     CMD: nginx -s reload
2025-09-23T21:21:56.498823031Z  [Express  ] › ⚠  warning   nginx: [alert] kill(402, 1) failed (3: No such process)

After trying with a fresh LXC and migrating, these keep filling the log.

2025/09/24 14:09:03 [alert] 454#454: failed to create BPF map (1: Operation not permitted)
2025/09/24 14:09:03 [emerg] 454#454: ngx_quic_bpf_module failed to initialize properly, ignored.please check limits and note that nginx state now can be inconsistent and restart may be required
2025/09/24 14:09:03 [alert] 2745#2745: sched_setaffinity() failed (22: Invalid argument)
|2025-09-24T14:09:07.796: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid  | pid 2745] | entering init worker. ngx_exiting=0
|2025-09-24T14:09:07.796: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:438 [uid  | pid 2745] | Configured workers amount: 2
|2025-09-24T14:09:07.796: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:451 [uid  | pid 2745] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000
2025/09/24 14:09:03 [alert] 2746#2746: sched_setaffinity() failed (22: Invalid argument)
|2025-09-24T14:09:07.797: register_workers@ngx_cp_initializer.c:99 [uid  | pid 2745] | Initiating registration of 2 workers to the attachment
|2025-09-24T14:09:07.798: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid  | pid 2746] | entering init worker. ngx_exiting=0
[Nginx    ] › ℹ  info      Reloading Nginx
[Global   ] › ⬤  debug     CMD: nginx -s reload
|2025-09-24T14:09:09.951: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:466 [uid  | pid 1409] <session id 17> | entering fini worker. is_timer_active=0, ngx_exiting=1
2025/09/24 14:09:09 [alert] 454#454: failed to create BPF map (1: Operation not permitted)
2025/09/24 14:09:09 [emerg] 454#454: ngx_quic_bpf_module failed to initialize properly, ignored.please check limits and note that nginx state now can be inconsistent and restart may be required
2025/09/24 14:09:09 [alert] 3252#3252: sched_setaffinity() failed (22: Invalid argument)
|2025-09-24T14:09:13.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid  | pid 3252] | entering init worker. ngx_exiting=0
|2025-09-24T14:09:13.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:438 [uid  | pid 3252] | Configured workers amount: 2
|2025-09-24T14:09:13.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:451 [uid  | pid 3252] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000
|2025-09-24T14:09:13.080: register_workers@ngx_cp_initializer.c:99 [uid  | pid 3252] | Initiating registration of 2 workers to the attachment
2025/09/24 14:09:09 [alert] 3286#3286: sched_setaffinity() failed (22: Invalid argument)
|2025-09-24T14:09:13.087: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid  | pid 3286] | entering init worker. ngx_exiting=0
|2025-09-24T14:09:13.186: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:466 [uid  | pid 2746] | entering fini worker. is_timer_active=0, ngx_exiting=1

🖼️ Additional context (optional).

No response

Originally created by @Drakonas on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/7887 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? NPMplus ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/npmplus.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Alpine ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve) ### 📝 Provide a clear and concise description of the issue. I created a fresh LXC without migrating, created my new credentials successfully, and started adding the proxy hosts by putting everything in manually, including the custom nginx configs for a couple of them. After a few entries, now when I add or edit any entry, I get an Internal Error in the popup. <img width="494" height="446" alt="Image" src="https://github.com/user-attachments/assets/ecdbd19f-8c2d-4542-907a-164417af6969" /> After cancelling, nothing shows. Before, if I would immediately refresh the page, the entry shows up with "Unknown" status. <img width="1163" height="63" alt="Image" src="https://github.com/user-attachments/assets/3231d503-6071-41b8-83d2-430a9467aadd" /> However, when attempting to reproduce just now, it wouldn't refresh at all. The nginx process seems to have just completely crashed instead. The server is offline after clicking Save. Before, when it refreshed, if I tried to delete the entry it gave an error stating something like "Error: Does not exist: 7" or something like that. I cannot recall exactly. I looked up the docker logs and this shows up a lot: ``` 2025/09/24 12:10:10 [alert] 2662#2662: sched_setaffinity() failed (22: Invalid argument) 2025/09/24 12:10:10 [alert] 2695#2695: sched_setaffinity() failed (22: Invalid argument) ``` You can see more troubleshooting in [this discussion](https://github.com/ZoeyVid/NPMplus/discussions/1890). ### 🔄 Steps to reproduce the issue. Step 1: Run the ProxmoxVE community script from the node's Shell. Use all defaults, set the timezone and ACME email. Step 2: Use the created /opt/.npm-pw file's credentials to sign in, change the username, full name, email, and password. Step 3: Start creating entries. A couple I've made have custom nginx configurations in the Advanced tab. I've supplied two here: ``` proxy_pass_header Authorization; proxy_pass_header Server; proxy_redirect off; proxy_buffering off; client_max_body_size 0; proxy_read_timeout 36000s; location = /.well-known/carddav { return 301 $scheme://$host:$server_port/remote.php/dav; } location = /.well-known/caldav { return 301 $scheme://$host:$server_port/remote.php/dav; } ``` ``` location / { proxy_pass $forward_scheme://$server:$port; # Or whatever local IP and port ADS is listening on proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header X-AMP-Scheme $scheme; proxy_read_timeout 86400s; proxy_send_timeout 86400s; proxy_http_version 1.1; proxy_redirect off; proxy_buffering off; proxy_cookie_path / "/; Secure"; client_max_body_size 10240M; ## Trusted Proxies Configuration ## Cloudflare Cloud IP Address Ranges https://www.cloudflare.com/ips/ ## https://support.cloudflare.com/hc/en-us/articles/200170786-Restoring-original-visitor-IPs#S7Z4EJQFN997YRY set_real_ip_from 173.245.48.0/20; set_real_ip_from 103.21.244.0/22; set_real_ip_from 103.22.200.0/22; set_real_ip_from 103.31.4.0/22; set_real_ip_from 141.101.64.0/18; set_real_ip_from 108.162.192.0/18; set_real_ip_from 190.93.240.0/20; set_real_ip_from 188.114.96.0/20; set_real_ip_from 197.234.240.0/22; set_real_ip_from 198.41.128.0/17; set_real_ip_from 162.158.0.0/15; set_real_ip_from 104.16.0.0/13; set_real_ip_from 104.24.0.0/14; set_real_ip_from 172.64.0.0/13; set_real_ip_from 131.0.72.0/22; set_real_ip_from 2400:cb00::/32; set_real_ip_from 2606:4700::/32; set_real_ip_from 2803:f800::/32; set_real_ip_from 2405:b500::/32; set_real_ip_from 2405:8100::/32; set_real_ip_from 2a06:98c0::/29; set_real_ip_from 2c0f:f248::/32; real_ip_header CF-Connecting-IP; real_ip_recursive on; } ``` Step 4: At some point creating one will fail with an Internal Error and nginx may or may not simply crash. Step 5: Now creating any proxy host will fail even if the entire LXC is rebooted or the docker compose redeployed. ### **_Step 6: Also, usually when the crash occurs, the entire console freezes, and the LXC CPU and memory max out at 100% as if the entire LXC is spiking with an infinite loop or memory leak._** ### ❌ Paste the full error output (if available). With the original LXC, nginx simply got killed after saving an entry. ``` 2025-09-23T21:21:52.379888824Z [Global ] › ⬤ debug CMD: nginx -tq 2025-09-23T21:21:53.754819908Z [Global ] › ⬤ debug CMD: nginx -tq 2025-09-23T21:21:55.098685358Z [Nginx ] › ℹ info Reloading Nginx 2025-09-23T21:21:55.098977353Z [Global ] › ⬤ debug CMD: nginx -s reload 2025-09-23T21:21:56.498823031Z [Express ] › ⚠ warning nginx: [alert] kill(402, 1) failed (3: No such process) ``` After trying with a fresh LXC and migrating, these keep filling the log. ``` 2025/09/24 14:09:03 [alert] 454#454: failed to create BPF map (1: Operation not permitted) 2025/09/24 14:09:03 [emerg] 454#454: ngx_quic_bpf_module failed to initialize properly, ignored.please check limits and note that nginx state now can be inconsistent and restart may be required 2025/09/24 14:09:03 [alert] 2745#2745: sched_setaffinity() failed (22: Invalid argument) |2025-09-24T14:09:07.796: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid | pid 2745] | entering init worker. ngx_exiting=0 |2025-09-24T14:09:07.796: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:438 [uid | pid 2745] | Configured workers amount: 2 |2025-09-24T14:09:07.796: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:451 [uid | pid 2745] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000 2025/09/24 14:09:03 [alert] 2746#2746: sched_setaffinity() failed (22: Invalid argument) |2025-09-24T14:09:07.797: register_workers@ngx_cp_initializer.c:99 [uid | pid 2745] | Initiating registration of 2 workers to the attachment |2025-09-24T14:09:07.798: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid | pid 2746] | entering init worker. ngx_exiting=0 [Nginx ] › ℹ info Reloading Nginx [Global ] › ⬤ debug CMD: nginx -s reload |2025-09-24T14:09:09.951: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:466 [uid | pid 1409] <session id 17> | entering fini worker. is_timer_active=0, ngx_exiting=1 2025/09/24 14:09:09 [alert] 454#454: failed to create BPF map (1: Operation not permitted) 2025/09/24 14:09:09 [emerg] 454#454: ngx_quic_bpf_module failed to initialize properly, ignored.please check limits and note that nginx state now can be inconsistent and restart may be required 2025/09/24 14:09:09 [alert] 3252#3252: sched_setaffinity() failed (22: Invalid argument) |2025-09-24T14:09:13.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid | pid 3252] | entering init worker. ngx_exiting=0 |2025-09-24T14:09:13.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:438 [uid | pid 3252] | Configured workers amount: 2 |2025-09-24T14:09:13.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:451 [uid | pid 3252] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000 |2025-09-24T14:09:13.080: register_workers@ngx_cp_initializer.c:99 [uid | pid 3252] | Initiating registration of 2 workers to the attachment 2025/09/24 14:09:09 [alert] 3286#3286: sched_setaffinity() failed (22: Invalid argument) |2025-09-24T14:09:13.087: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:419 [uid | pid 3286] | entering init worker. ngx_exiting=0 |2025-09-24T14:09:13.186: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:466 [uid | pid 2746] | entering fini worker. is_timer_active=0, ngx_exiting=1 ``` ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:49:48 +03:00

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@MickLesk commented on GitHub (Sep 24, 2025):

Report this to NPMPlus Repo. Its 100% the Same. Its Just an docker compose. Nothing relevant or related to Script or LXC

@MickLesk commented on GitHub (Sep 24, 2025): Report this to NPMPlus Repo. Its 100% the Same. Its Just an docker compose. Nothing relevant or related to Script or LXC

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#1668

No description provided.

Rows
Columns