OpenAppSec attachment module in NPMplus nginx -tq/nginx -s reload issue

[UncleNet41]

Hello and thanks for the awesome product! Been using till march, switched from fully local to

After upgrading NPMplus to 2026-06-05-b2 NPMplus stopped working due to a conflict with OpenAppSec module preventing the container start. The mantainer did a little debug and succeded in making the module load correctly and fixing the functionality with the release

However, the module is now causing two issues with the NPMplus webui:

• it makes NPMplus hang after saving every change despite correctly processing it: if i reload the page, the modification is there
• it prevents the creation of new hosts: if i disable the module, new hosts can be correctly created and go online, while if i try the same with the module loaded it just creates an host which stays offline no matter what i do.

Additional troubleshooting: if i try to revert to another version:

• openappsec version 1.1.33: no WAF functionality, still the same bugs in the NPMplus webui
• openappsec version 1.1.34 (latest atm, BUT! in the openappsec webui it says 1.1.35. another possible bug? see screenshot): WAF functionality ok, still the same bugs in the NPMplus webui

So, to sum it up:

• NPMplus version 2026-06-07-b2
• OpenAppSec agent 1.1.34 (but 1.1.35 on your webui?)
• NPMplus is in host mode
• OpenAppsec is in network_mode: service:npmplus

Here the logs:

 _ _  ___  __ __       _
| \ || . \|  \  \ ___ | | _ _  ___
|   ||  _/|     || . \| || | |[_-[
|_\_||_|  |_|_|_||  _/|_| \__|/__/
                 |_|
-------------------------------------
Version:  2026-06-07-b2-78adb0b-2.15.1
Date:     Sun Jun  7 10:28:56 CEST 2026
-------------------------------------

no DEFAULT_CERT_ID set, using dummycerts.
'/usr/local/nginx/conf/conf.d/goaccess.conf.disabled' -> '/usr/local/nginx/conf/conf.d/goaccess.conf'

-------------------------------------
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
-------------------------------------

Running in stand-alone mode...

npm-5  	updated	
npm-6  	updated	
npm-8  	updated	
npm-9  	updated	
LINEAGE	RESULT 	REASON

Starting services...
 [SETTING UP STORAGE /data/nginx/logs/access.log] {0} @ {0/s}
reading config file /etc/logrotate
acquired lock on state file /data/nginx/logs/logrotate.state
Reading state from file: /data/nginx/logs/logrotate.state
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state

Handling 1 logs

rotating pattern: /data/nginx/logs/*.log after 1 days empty log files are not rotated, (7 rotations), old logs are removed
considering log /data/nginx/logs/access.log
  Now: 2026-06-07 10:28
  Last rotated at 2026-06-07 09:11
  log does not need rotating (log has been rotated at 2026-06-07 09:11, which is less than a day ago)
considering log /data/nginx/logs/error.log
  Now: 2026-06-07 10:28
  Last rotated at 2026-06-07 09:11
  log does not need rotating (log has been rotated at 2026-06-07 09:11, which is less than a day ago)
considering log /data/nginx/logs/stream.log
  Now: 2026-06-07 10:28
  Last rotated at 2026-03-20 00:00
  log does not need rotating (log is empty)
2026/06/07 10:28:57 [notice] 349#349: parsed a resolver: "192.168.1.118" in /usr/local/nginx/conf/nginx.conf:39
2026/06/07 10:28:57 [notice] 349#349: parsed a resolver: "192.168.1.132" in /usr/local/nginx/conf/nginx.conf:39
2026/06/07 10:28:57 [notice] 349#349: parsed a resolver: "192.168.1.118" in /usr/local/nginx/conf/nginx.conf:317
2026/06/07 10:28:57 [notice] 349#349: parsed a resolver: "192.168.1.132" in /usr/local/nginx/conf/nginx.conf:317
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:487 [uid  | pid 349] | |2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:487 [uid  | pid 349] | entering init worker. ngx_exiting=0
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:506 [uid  | pid 349] | Configured workers amount: 4
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:525 [uid  | pid 349] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:487 [uid  | pid 349] | |2026-06-07T10:28:57.952: register_workers@ngx_cp_initializer.c:234 [uid  | pid 349] | Initiating registration of 4 workers to the attachment
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:540 [uid  | pid 349] | entering init worker. ngx_exiting=0
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:540 [uid  | pid 349] | Nginx version does not support async mode
Nginx version does not support async mode
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:487 [uid  | pid 349] | entering init worker. ngx_exiting=0
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:540 [uid  | pid 349] | Nginx version does not support async mode
entering init worker. ngx_exiting=0
|2026-06-07T10:28:57.952: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:540 [uid  | pid 349] | Nginx version does not support async mode


WebSocket server ready to accept new client connections
|2026-06-07T10:28:58.336: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:557 [uid  | pid 349] | Request headers received
|2026-06-07T10:28:58.336: reset_failure_state@ngx_cp_failing_state.c:73 [uid  | pid 349] | Resetting failing interval to default. Interval: 20 seconds
|2026-06-07T10:28:58.336: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:282 [uid  | pid 349] | NGINX attachment state: enabled
|2026-06-07T10:28:58.336: init_cp_session_data@ngx_cp_hooks.c:69 [uid  | pid 349] | Initializing new session data ctx for session ID 1
|2026-06-07T10:28:58.336: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:579 [uid  | pid 349] <session id 3> | Request header filter handling session ID: 3
|2026-06-07T10:28:58.336: enforce_sessions_rate@ngx_cp_hooks.c:396 [uid  | pid 349] <session id 3> | Handling new session. Number of last minute sessions: 0 
|2026-06-07T10:28:58.336: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:597 [uid  | pid 349] <session id 3> | spawn ngx_http_cp_registration_thread
|2026-06-07T10:28:58.336: ngx_cp_run_in_thread_timeout@ngx_cp_thread.c:59 [uid  | pid 349] <session id 3> | Executing cb in dedicated thread, fn=ngx_http_cp_registration_thread
|2026-06-07T10:28:58.336: init_general_config@ngx_cp_utils.c:1132 [uid  | pid 349] <session id 3> | Setting debug level to: 2
|2026-06-07T10:28:58.336: init_general_config@ngx_cp_utils.c:1254 [uid  | pid 349] <session id 3> | Successfully loaded configuration. inspection mode: 0, debug level: 2, failure mode: fail-open, fail mode timeout: 50 msec, failure wait mode: fail-open, fail mode wait timeout: 150 msec, sessions per minute limit verdict: Accpet, max sessions per minute: 0, req max processing time: 3000 msec, res max processing time: 3000 msec, registration thread timeout: 100 msec, req header thread timeout: 100 msec, req body thread timeout: 150 msec, res header thread timeout: 100 msec, res body thread timeout: 150 msec, wait thread timeout: 150 msec, static resources path: /dev/shm/static_resources, num of nginx ipc elements: 200, keep alive interval msec: 150000 msec, min retries for verdict: 3, max retries for verdict: 15, num retries for hold verdict: 3, polling time for hold verdict: 1, body size trigger for request: 200000, decompression pool size: 262144 bytes, recompression pool size: 16384 bytes, async mode: 0
|2026-06-07T10:28:58.336: set_unique_id@ngx_cp_initializer.c:810 [uid 2 | pid 349] <session id 3> | Successfully set attachment's unique_id: '2' (int: 2)
|2026-06-07T10:28:58.336: ngx_cp_attachment_init_process@ngx_cp_initializer.c:857 [uid 2 | pid 349] <session id 3> | Failed to register to Attachments Manager service
[Global        ] › ℹ  info      Using Sqlite: /data/npmplus/database.sqlite
[Global        ] › ℹ  info      Checking for keys file: /data/npmplus/keys.json
[Global        ] › ℹ  info      Keys file exists OK
[Migrate       ] › ℹ  info      Current database version: none
[Nginx         ] › ⬤  debug     Wrote config: /usr/local/nginx/conf/conf.d/default.conf
[Global        ] › ⬤  debug     CMD: nginxbeautifier -s 2 /usr/local/nginx/conf/conf.d/default.conf
[Certbot       ] › ▶  start     Installing duckdns...
[Global        ] › ⬤  debug     CMD: pip install --upgrade --no-cache-dir certbot-dns-duckdns
[Certbot       ] › ☒  complete  Installed duckdns
[Certbot       ] › ▶  start     Installing dynu...
[Global        ] › ⬤  debug     CMD: pip install --upgrade --no-cache-dir certbot-dns-dynu
[Certbot       ] › ☒  complete  Installed dynu
[Global        ] › ℹ  info      Cloudflares IPs are NOT trusted
[TLS           ] › ℹ  info      Certbot Renewal Timer initialized
[TLS           ] › ℹ  info      Renewing Certbot TLS certs close to expiry...
[Global        ] › ⬤  debug     CMD: certbot --config /etc/certbot.ini renew --server https://acme.zerossl.com/v2/DV90 --quiet
[Global        ] › ⬤  debug     CMD: certbot-ocsp-fetcher.sh -c /data/tls/certbot/live -o /data/tls/certbot/live --no-reload-webserver --quiet
[Global        ] › ℹ  info      Backend PID 346 listening on unix socket...
|2026-06-07T10:29:02.952: get_docker_id@ngx_cp_initializer.c:537 [uid  | pid 349] | opened file /proc/self/cgroup
[Global        ] › ⬤  debug     CMD: nginx -tq
|2026-06-07T10:29:03.032: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:557 [uid  | pid 349] | Request headers received
|2026-06-07T10:29:03.032: reset_failure_state@ngx_cp_failing_state.c:73 [uid  | pid 349] | Resetting failing interval to default. Interval: 20 seconds
|2026-06-07T10:29:03.032: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:282 [uid  | pid 349] | NGINX attachment state: enabled
|2026-06-07T10:29:03.032: init_cp_session_data@ngx_cp_hooks.c:69 [uid  | pid 349] | Initializing new session data ctx for session ID 1
|2026-06-07T10:29:03.032: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:579 [uid  | pid 349] <session id 3> | Request header filter handling session ID: 3
|2026-06-07T10:29:03.032: enforce_sessions_rate@ngx_cp_hooks.c:396 [uid  | pid 349] <session id 3> | Handling new session. Number of last minute sessions: 0 
|2026-06-07T10:29:03.032: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:597 [uid  | pid 349] <session id 3> | spawn ngx_http_cp_registration_thread
|2026-06-07T10:29:03.032: ngx_cp_run_in_thread_timeout@ngx_cp_thread.c:59 [uid  | pid 349] <session id 3> | Executing cb in dedicated thread, fn=ngx_http_cp_registration_thread
|2026-06-07T10:29:03.032: init_general_config@ngx_cp_utils.c:1132 [uid  | pid 349] <session id 3> | Setting debug level to: 2
|2026-06-07T10:29:03.032: init_general_config@ngx_cp_utils.c:1254 [uid  | pid 349] <session id 3> | Successfully loaded configuration. inspection mode: 0, debug level: 2, failure mode: fail-open, fail mode timeout: 50 msec, failure wait mode: fail-open, fail mode wait timeout: 150 msec, sessions per minute limit verdict: Accpet, max sessions per minute: 0, req max processing time: 3000 msec, res max processing time: 3000 msec, registration thread timeout: 100 msec, req header thread timeout: 100 msec, req body thread timeout: 150 msec, res header thread timeout: 100 msec, res body thread timeout: 150 msec, wait thread timeout: 150 msec, static resources path: /dev/shm/static_resources, num of nginx ipc elements: 200, keep alive interval msec: 150000 msec, min retries for verdict: 3, max retries for verdict: 15, num retries for hold verdict: 3, polling time for hold verdict: 1, body size trigger for request: 200000, decompression pool size: 262144 bytes, recompression pool size: 16384 bytes, async mode: 0
|2026-06-07T10:29:03.032: set_unique_id@ngx_cp_initializer.c:810 [uid 4 | pid 349] <session id 3> | Successfully set attachment's unique_id: '4' (int: 4)
|2026-06-07T10:29:03.036: register_to_attachments_manager@ngx_cp_initializer.c:746 [uid  | pid 349] | Successfully registered on client. socket: 38, instance ID: 1, instances amount: 4, received path: /dev/shm/check-point/cp-nano-http-transaction-handler-1
|2026-06-07T10:29:03.060: init_signaling_socket@ngx_cp_initializer.c:377 [uid 4 | pid 349] <session id 3> | Could not connect to nano service. Path: /dev/shm/check-point/cp-nano-http-transaction-handler-4, Error: Connection refused
|2026-06-07T10:29:03.220: init_signaling_socket@ngx_cp_initializer.c:377 [uid 4 | pid 349] <session id 5> | Could not connect to nano service. Path: /dev/shm/check-point/cp-nano-http-transaction-handler-4, Error: Connection refused
|2026-06-07T10:29:05.016: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:557 [uid  | pid 349] | Request headers received
|2026-06-07T10:29:05.016: reset_failure_state@ngx_cp_failing_state.c:73 [uid  | pid 349] | Resetting failing interval to default. Interval: 20 seconds
|2026-06-07T10:29:05.016: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:282 [uid  | pid 349] | NGINX attachment state: enabled
|2026-06-07T10:29:05.016: init_cp_session_data@ngx_cp_hooks.c:69 [uid  | pid 349] | Initializing new session data ctx for session ID 1
|2026-06-07T10:29:05.016: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:579 [uid  | pid 349] <session id 3> | Request header filter handling session ID: 3
|2026-06-07T10:29:05.016: enforce_sessions_rate@ngx_cp_hooks.c:396 [uid  | pid 349] <session id 3> | Handling new session. Number of last minute sessions: 0 
|2026-06-07T10:29:05.016: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:597 [uid  | pid 349] <session id 3> | spawn ngx_http_cp_registration_thread
|2026-06-07T10:29:05.016: ngx_cp_run_in_thread_timeout@ngx_cp_thread.c:59 [uid  | pid 349] <session id 3> | Executing cb in dedicated thread, fn=ngx_http_cp_registration_thread
|2026-06-07T10:29:05.016: init_general_config@ngx_cp_utils.c:1132 [uid  | pid 349] <session id 3> | Setting debug level to: 2
|2026-06-07T10:29:05.016: init_general_config@ngx_cp_utils.c:1254 [uid  | pid 349] <session id 3> | Successfully loaded configuration. inspection mode: 0, debug level: 2, failure mode: fail-open, fail mode timeout: 50 msec, failure wait mode: fail-open, fail mode wait timeout: 150 msec, sessions per minute limit verdict: Accpet, max sessions per minute: 0, req max processing time: 3000 msec, res max processing time: 3000 msec, registration thread timeout: 100 msec, req header thread timeout: 100 msec, req body thread timeout: 150 msec, res header thread timeout: 100 msec, res body thread timeout: 150 msec, wait thread timeout: 150 msec, static resources path: /dev/shm/static_resources, num of nginx ipc elements: 200, keep alive interval msec: 150000 msec, min retries for verdict: 3, max retries for verdict: 15, num retries for hold verdict: 3, polling time for hold verdict: 1, body size trigger for request: 200000, decompression pool size: 262144 bytes, recompression pool size: 16384 bytes, async mode: 0
|2026-06-07T10:29:05.016: set_unique_id@ngx_cp_initializer.c:810 [uid 1 | pid 349] <session id 3> | Successfully set attachment's unique_id: '1' (int: 1)
|2026-06-07T10:29:05.016: init_signaling_socket@ngx_cp_initializer.c:377 [uid 1 | pid 349] <session id 3> | Could not connect to nano service. Path: /dev/shm/check-point/cp-nano-http-transaction-handler-1, Error: Connection refused
[TLS           ] › ⚠  warning   Certbot completed with errors: Error: Failed to renew certificate npm-6 with error: File not found: /tmp/certbot-credentials/credentials-6
All renewals failed. The following certificates could not be renewed:
  /data/tls/certbot/live/npm-6/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
[Global        ] › ⬤  debug     CMD: certbot-ocsp-fetcher.sh -c /data/tls/certbot/live -o /data/tls/certbot/live --no-reload-webserver --quiet
[Global        ] › ⬤  debug     CMD: nginx -tq
|2026-06-07T10:29:08.072: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:557 [uid  | pid 349] | Request headers received
|2026-06-07T10:29:08.072: reset_failure_state@ngx_cp_failing_state.c:73 [uid  | pid 349] | Resetting failing interval to default. Interval: 20 seconds
|2026-06-07T10:29:08.072: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:282 [uid  | pid 349] | NGINX attachment state: enabled
|2026-06-07T10:29:08.072: init_cp_session_data@ngx_cp_hooks.c:69 [uid  | pid 349] | Initializing new session data ctx for session ID 1
|2026-06-07T10:29:08.072: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:579 [uid  | pid 349] <session id 3> | Request header filter handling session ID: 3
|2026-06-07T10:29:08.072: enforce_sessions_rate@ngx_cp_hooks.c:396 [uid  | pid 349] <session id 3> | Handling new session. Number of last minute sessions: 0 
|2026-06-07T10:29:08.072: ngx_http_cp_req_header_handler_sync@ngx_cp_hooks.c:597 [uid  | pid 349] <session id 3> | spawn ngx_http_cp_registration_thread
|2026-06-07T10:29:08.072: ngx_cp_run_in_thread_timeout@ngx_cp_thread.c:59 [uid  | pid 349] <session id 3> | Executing cb in dedicated thread, fn=ngx_http_cp_registration_thread
|2026-06-07T10:29:08.076: init_general_config@ngx_cp_utils.c:1132 [uid  | pid 349] <session id 3> | Setting debug level to: 2
|2026-06-07T10:29:08.076: init_general_config@ngx_cp_utils.c:1254 [uid  | pid 349] <session id 3> | Successfully loaded configuration. inspection mode: 0, debug level: 2, failure mode: fail-open, fail mode timeout: 50 msec, failure wait mode: fail-open, fail mode wait timeout: 150 msec, sessions per minute limit verdict: Accpet, max sessions per minute: 0, req max processing time: 3000 msec, res max processing time: 3000 msec, registration thread timeout: 100 msec, req header thread timeout: 100 msec, req body thread timeout: 150 msec, res header thread timeout: 100 msec, res body thread timeout: 150 msec, wait thread timeout: 150 msec, static resources path: /dev/shm/static_resources, num of nginx ipc elements: 200, keep alive interval msec: 150000 msec, min retries for verdict: 3, max retries for verdict: 15, num retries for hold verdict: 3, polling time for hold verdict: 1, body size trigger for request: 200000, decompression pool size: 262144 bytes, recompression pool size: 16384 bytes, async mode: 0
|2026-06-07T10:29:08.076: set_unique_id@ngx_cp_initializer.c:810 [uid 3 | pid 349] <session id 3> | Successfully set attachment's unique_id: '3' (int: 3)
|2026-06-07T10:29:08.108: init_signaling_socket@ngx_cp_initializer.c:447 [uid 3 | pid 349] <session id 3> | Paired affinity disabled, sending target_core=-1 to service
|2026-06-07T10:29:08.120: init_signaling_socket@ngx_cp_initializer.c:476 [uid 3 | pid 349] <session id 3> | Successfully connected on client socket 35
|2026-06-07T10:29:08.120: ngx_cp_attachment_init_process@ngx_cp_initializer.c:885 [uid 3 | pid 349] <session id 3> | Initializing IPC channel
|2026-06-07T10:29:08.120: ngx_cp_attachment_init_process@ngx_cp_initializer.c:945 [uid 3 | pid 349] <session id 3> | NGINX attachment (UID='3') successfully registered to nano service after 1 attempts.
|2026-06-07T10:29:24.548: init_signaling_socket@ngx_cp_initializer.c:447 [uid 2 | pid 349] <session id 5> | Paired affinity disabled, sending target_core=-1 to service
|2026-06-07T10:29:24.552: init_signaling_socket@ngx_cp_initializer.c:476 [uid 2 | pid 349] <session id 5> | Successfully connected on client socket 41
|2026-06-07T10:29:24.552: ngx_cp_attachment_init_process@ngx_cp_initializer.c:885 [uid 2 | pid 349] <session id 5> | Initializing IPC channel
|2026-06-07T10:29:24.552: ngx_cp_attachment_init_process@ngx_cp_initializer.c:945 [uid 2 | pid 349] <session id 5> | NGINX attachment (UID='2') successfully registered to nano service after 2 attempts.
|2026-06-07T10:29:27.020: init_signaling_socket@ngx_cp_initializer.c:447 [uid 4 | pid 349] <session id 9> | Paired affinity disabled, sending target_core=-1 to service
|2026-06-07T10:29:27.028: init_signaling_socket@ngx_cp_initializer.c:476 [uid 4 | pid 349] <session id 9> | Successfully connected on client socket 37
|2026-06-07T10:29:27.028: ngx_cp_attachment_init_process@ngx_cp_initializer.c:885 [uid 4 | pid 349] <session id 9> | Initializing IPC channel
|2026-06-07T10:29:27.028: ngx_cp_attachment_init_process@ngx_cp_initializer.c:945 [uid 4 | pid 349] <session id 9> | NGINX attachment (UID='4') successfully registered to nano service after 4 attempts.
|2026-06-07T10:29:34.424: reset_attachment_config@ngx_cp_utils.c:1263 [uid 2 | pid 349] <session id 73> | Resetting attachment configuration
|2026-06-07T10:29:34.424: init_general_config@ngx_cp_utils.c:1254 [uid 2 | pid 349] <session id 73> | Successfully loaded configuration. inspection mode: 0, debug level: 2, failure mode: fail-open, fail mode timeout: 50 msec, failure wait mode: fail-open, fail mode wait timeout: 150 msec, sessions per minute limit verdict: Accpet, max sessions per minute: 0, req max processing time: 3000 msec, res max processing time: 3000 msec, registration thread timeout: 100 msec, req header thread timeout: 100 msec, req body thread timeout: 150 msec, res header thread timeout: 100 msec, res body thread timeout: 150 msec, wait thread timeout: 150 msec, static resources path: /dev/shm/static_resources, num of nginx ipc elements: 200, keep alive interval msec: 150000 msec, min retries for verdict: 3, max retries for verdict: 15, num retries for hold verdict: 3, polling time for hold verdict: 1, body size trigger for request: 200000, decompression pool size: 262144 bytes, recompression pool size: 16384 bytes, async mode: 0
|2026-06-07T10:29:35.780: init_signaling_socket@ngx_cp_initializer.c:447 [uid 1 | pid 349] <session id 5> | Paired affinity disabled, sending target_core=-1 to service
|2026-06-07T10:29:35.780: init_signaling_socket@ngx_cp_initializer.c:476 [uid 1 | pid 349] <session id 5> | Successfully connected on client socket 40
|2026-06-07T10:29:35.780: ngx_cp_attachment_init_process@ngx_cp_initializer.c:885 [uid 1 | pid 349] <session id 5> | Initializing IPC channel
|2026-06-07T10:29:35.780: ngx_cp_attachment_init_process@ngx_cp_initializer.c:945 [uid 1 | pid 349] <session id 5> | NGINX attachment (UID='1') successfully registered to nano service after 2 attempts.
|2026-06-07T10:29:37.780: reset_attachment_config@ngx_cp_utils.c:1263 [uid 4 | pid 349] <session id 13> | Resetting attachment configuration
|2026-06-07T10:29:37.780: init_general_config@ngx_cp_utils.c:1254 [uid 4 | pid 349] <session id 13> | Successfully loaded configuration. inspection mode: 0, debug level: 2, failure mode: fail-open, fail mode timeout: 50 msec, failure wait mode: fail-open, fail mode wait timeout: 150 msec, sessions per minute limit verdict: Accpet, max sessions per minute: 0, req max processing time: 3000 msec, res max processing time: 3000 msec, registration thread timeout: 100 msec, req header thread timeout: 100 msec, req body thread timeout: 150 msec, res header thread timeout: 100 msec, res body thread timeout: 150 msec, wait thread timeout: 150 msec, static resources path: /dev/shm/static_resources, num of nginx ipc elements: 200, keep alive interval msec: 150000 msec, min retries for verdict: 3, max retries for verdict: 15, num retries for hold verdict: 3, polling time for hold verdict: 1, body size trigger for request: 200000, decompression pool size: 262144 bytes, recompression pool size: 16384 bytes, async mode: 0
|2026-06-07T10:29:37.904: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 4 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:29:37.984: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 4 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:29:39.208: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 2 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:29:46.240: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 2 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:29:57.120: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 2 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:29:57.916: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 2 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:30:05.288: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 2 | pid 349] | Reconfiguring the local NGINX attachment state
|2026-06-07T10:30:47.668: is_ngx_cp_attachment_disabled@ngx_http_cp_attachment_module.c:280 [uid 4 | pid 349] | Reconfiguring the local NGINX attachment state

should you need anything to pinpoint the issue, let me know. thanks again!