-
|
I've been using NPMplus for a while now! I just updated to latest (2026-04-21-r2) and I can't access the web ui, it loads for a while and says "The API is not healthy." While this is happening, my proxy hosts appear to be working. Here's a portion of the log I grabbed the release's docker compose file and changed the yml to have the same settings (openappsec, crowdsec, and everything to make them work) and it spins up fine without using my old data directory (/opt/npmplus is a named volume, and is created with the stack. All other directories are named volumes in the same way) and I can set a new admin user/password and navigate the web ui.
However, when I use my old data directory (all other named volumes are fresh, created with the stack) I get this "connect to unix:/run/npmplus.sock failed (no such file or directory)" error. How can I fix this? Am I able to copy over my proxy hosts, certificates, and access lists to a fresh install? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
My initial issue is very different than the one mentioned in that thread, I only mentioned the "could not connect to nano service" message because I thought they could be related. |
Beta Was this translation helpful? Give feedback.
-
|
It appears as though the container doesn't connect to the socket? I never see "Backend PID listening on unix socket..." when using my (old) data volume while running the openappsec suite of services (Or just set NGINX_LOAD_OPENAPPSEC_ATTACHMENT_MODULE=true in the environment variables). |
Beta Was this translation helpful? Give feedback.
-
|
can you please post the full startup log? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry it took a while to get back. Here's my startup logs after a few minutes. |
Beta Was this translation helpful? Give feedback.
could be related to #3200