Feedback on installation and use of NPMplus 2026-01-16-r2-8ab7314-2.13.6

[alainq79]

Hello,

NPMplus

Version: 2026-01-16-r2-8ab7314-2.13.6

Date: Sat Jan 17 07:38:56 CET 2026

---

User

When you read my feedback, please, don't forget this:

Brain version: 1971 (no update).
Skill level: between beginner and advanced user.
English level: very low (Google trad is my friend).

Homelab: no ; only product machine.
web browser: Firefox

What i'm looking for: Beginner users friendly reverse proxy and multilayer protection for my NAS.
In my imagination, i see this: https://tenor.com/fr/view/droopy-infinite-door-tex-avery-open-gif-17288093

I learn how to use Nginx Proxy Manager with youtube followind Christian Lempa's tutoriel: https://www.youtube.com/watch?v=P3imFC7GSr0

Don't forget, most of the time, i don't understand what i'm doing.

Base: Feedback on installation and use of NPMplus products #251

---

My two cents:

first log = OK
but, after first log:
https://npm.mysite.fr/login => "Oops... You just found an error page"
Clic on button: "Take me home" => Back to dashboard = OK
If i log out and log in, same thing.

All my Proxy Host work well. (Nextcloud AIO, Vaultwarden, Jellyfin and 19 others).

dark mode + light mode => Better for the eyes, thanks to you.

---

Traductions: FR

windows=>path=>to => suggested change (suggestion de changement)

Certificats => ajouter certificat => Ajouter Certbot via HTTP => Reuse Key (Réutiliser la clé)
Certificats => ajouter certificat => Ajouter Certbot via DNS => Reuse Key (Réutiliser la clé)

Hôtes => Ajouter Hôte proxy => Détails => Options => Enable fancyindex/compression by upstream (Activer Fancyindex/Compression par Upstream)
Hôtes => Ajouter Hôte proxy => Emplacement personnalisé => Forward Hostname / IP / Path (Forward Hostname / IP / Chemin)
Hôtes => Ajouter Hôte proxy => Emplacement personnalisé => Options => Enable fancyindex/compression by upstream (Activer Fancyindex/Compression par Upstream)

---

Geoblocking example

I try to follow the README.md out of the box:
change to http_top.conf:

geoip2 /data/goaccess/geoip/GeoLite2-Country.mmdb {
  auto_reload 60m;
  $geoip2_country_iso_code country iso_code;
}

# whitelist example, you can add as many country codes as you want, country code list: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#XY
map $geoip2_country_iso_code $geoip2_country_rule {
  default no;
  FR yes;
#  XY yes;
#  '' yes; # if you want to allow IPs with unknown country codes, if you don't do this make sure to allow private IPs
}

# blacklist example, you can add as many country codes as you want, country code list: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#XY
#map $geoip2_country_iso_code $geoip2_country_rule {
#  default yes;
#  AA no;
#  XY no;
#  '' no; # if you want to block IPs with unknown country codes, if you do this make sure to allow private IPs
#}

# uncomment if you block/don't allow IPs with unknown country codes
geo $geo_is_private_ip {
  default no;
  127.0.0.0/8 yes;
#  10.0.0.0/8 yes;
  172.16.0.0/12 yes;
  192.168.0.0/16 yes;
#  169.254.0.0/16 yes;
#  ::1/128 yes;
#  fc00::/7 yes;
#  fec0::/10 yes;
}

Restart and:

Version:  2026-01-17-r1-946a9a2-2.13.6

Date:     Sat Jan 17 11:59:38 CET 2026

-------------------------------------

'/usr/local/nginx/conf/conf.d/crowdsec.conf.disabled' -> '/usr/local/nginx/conf/conf.d/crowdsec.conf'

no DEFAULT_CERT_ID set, using dummycerts.

'/usr/local/nginx/conf/conf.d/goaccess.conf.disabled' -> '/usr/local/nginx/conf/conf.d/goaccess.conf'

-------------------------------------
User:     root
PUID:     0
User ID:  0
PGID:     0
Group ID: 0
-------------------------------------
nginx: [emerg] unknown "lan-ip" variable
nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed

Conclusion: Out of the box, it is too hard for me. It work if i copy/past/change exemple in #730 🌍 Setting Up GeoIP Blocking in NPMplus by xxcite81.

geoip2 /data/goaccess/geoip/GeoLite2-Country.mmdb {
        auto_reload 60m;
        $geoip2_data_country_code default=US country iso_code;
        }

map $geoip2_data_country_code $allowed_country {
        default no;
        US yes;
        DE yes;
        AU yes;
        }

geo $lan-ip {
        default no;
        192.168.0.0/16 yes;
        172.16.0.0/12 yes;
        10.0.0.0/8 yes;
        }

map $http_upgrade $connection_upgrade_keepalive {
        default upgrade;
        '' '';
        }

I can uncomment few lines, but change somethings is very hard for me. Code seems to be some kind of hieroglyphs.

---

Anubis

Try config host with anubis =>fail.

finish with:

---

OPEN-APPSEC

Always the same: no connection with NPMplus ??

same question on docker compose.yaml line 173 : - "registered_server=NPMplus"

But my NPMplus is calling: "container_name: npmplus" on line 4

Should i change the line 173 ?

---

Conclusion

To my point of view, you're doing a good job as an engineer.
But you need to find a good teacher to showcase your great work to your target audience.
I would have liked to help you with this task. But to teach well, you must first understand your subject.

Thank you again for your work.

[alainq79]

I forget

Crowdsec

Work well.

[Zoey2936]

https://npm.mysite.fr/login => "Oops... You just found an error page"
Clic on button: "Take me home" => Back to dashboard = OK
If i log out and log in, same thing.

this sounds interesting, I can't reproduce this, but this should not happen

Traductions: FR

I think you are talking about the french translation quality? It is nearly identical to the upstream translation, since I don't speak french, if you want you can create a PR to improve it, either here or to upstream

Geoblocking example

the issues you had could be because you already had hosts based on the other example

Anubis

the auth_request line needs to be in a custom location with the path /, it doesn't work in the advanced config since with this you create an infinite loop:
you try to access the site => nginx trys to ask anubis => to ask anubis you need to be allowed by anubis => infinite loop

OPEN-APPSEC

I must say I don't know much about openappsec, I compile their module and provide it to the people, I don't use it myself, from my understanding the value of registered_server is cosmetic and doesn't matter, but I could be wrong. But it should be unrelated to the containe rname in anycase.

I know the docs are not perfect, but this is also why I try to help the people if they open discussions

[alainq79]

Error: Promised response from onMessage listener went out of scope

[alainq79]

I had a clue about the first subjet:

https://npm.mysite.fr/login => "Oops... You just found an error page"
Clic on button: "Take me home" => Back to dashboard = OK
If i log out and log in, same thing.

In the fisrt deployment of NPMplus, I uncommented and filled in the lines the lines 82 and 83.

      - "INITIAL_ADMIN_EMAIL=XXXXXXX@XXX" 
      - "INITIAL_ADMIN_PASSWORD=XXXXXXXX" 

When I comment the lines again, the error disappears.

#      - "INITIAL_ADMIN_EMAIL=<initial@email.tld>" 
#      - "INITIAL_ADMIN_PASSWORD=<initial-password>" 

[Zoey2936]

that is interestinf since they are only used here:

const setupDefaultUser = async () => {
	const initialAdminEmail = process.env.INITIAL_ADMIN_EMAIL;
	const initialAdminPassword = process.env.INITIAL_ADMIN_PASSWORD;

	// This will only create a new user when there are no active users in the database
	// and the INITIAL_ADMIN_EMAIL and INITIAL_ADMIN_PASSWORD environment variables are set.
	// Otherwise, users should be shown the setup wizard in the frontend.
	// I'm keeping this legacy behavior in case some people are automating deployments.

	if (!initialAdminEmail || !initialAdminPassword) {
		return Promise.resolve();
	}

	const userIsetup = await isSetup();
	if (!userIsetup) {
		// Create a new user and set password
		logger.info(`Creating a new user: ${initialAdminEmail} with password: ${initialAdminPassword}`);

		const data = {
			is_deleted: 0,
			email: initialAdminEmail,
			name: "Administrator",
			nickname: "Admin",
			avatar: "",
			roles: ["admin"],
		};

		const user = await userModel.query().insertAndFetch(data);

		await authModel.query().insert({
			user_id: user.id,
			type: "password",
			secret: initialAdminPassword,
			meta: {},
		});

		await userPermissionModel.query().insert({
			user_id: user.id,
			visibility: "all",
			proxy_hosts: "manage",
			redirection_hosts: "manage",
			dead_hosts: "manage",
			streams: "manage",
			access_lists: "manage",
			certificates: "manage",
		});
		logger.info("Initial admin setup completed");
	}
};

and as you may see it does nothing if a user already exists and are ignored in that case

[Zoey2936]

can you maybe readd them again and please confirm again for me if it breaks again?

[alainq79]

Before I readd the two line, i check if it's always good at 20h40.
The error came back.
Then i try to add and administrator user, then:

When i click on Cancel, then:

F5 to reload:

= crash NPMplus
Restart NPMplus container without the two ligne = crash
readd the two lines and restart the container = OK
But it's impossible to create a new user. 4i've got this again:

If you want to reproduce, i'm doing this:

• First install NPMplus in décember 2025 with the two line: admin email and password. => work well no error.
• 17/01/2026: update to npmplus 2026-01-16-r2-8ab7314-2.13.6
• first log error
• 18/01/2026 morning: comment the two line => all work well with no error.
• 18/01/2026 evening: error after login came back.
• 20h30: try to create new user fail with error .JSON
• crash container
• Restart NPMplus container with Portainer and without the two line = Unhealthy
• Restart Npmplus container with the two line = OK
• Error steel here = Yes
• can create new user = No

I hope, i can help you to understand.
If you need, i can send you the logs file.

[Zoey2936]

yes log would be useful

[alainq79]

Log without the two line:

|_\_||_|  |_|_|_||  _/|_| \__|/__/

                 |_|

-------------------------------------

Version:  2026-01-17-r3-6053d73-2.13.6

Date:     Sun Jan 18 21:42:27 CET 2026

-------------------------------------

no DEFAULT_CERT_ID set, using dummycerts.

removed '/usr/local/nginx/logs/nginx.pid'

removed '/run/goaccess.sock'

removed '/run/npmplus.sock'

-------------------------------------

User:     root

PUID:     0

User ID:  0

PGID:     0

Group ID: 0

-------------------------------------

Starting services...

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

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-01-18 21:42

  Last rotated at 2026-01-18 06:14

  log does not need rotating (log has been rotated at 2026-01-18 06:14, which is less than a day ago)

considering log /data/nginx/logs/error.log

  Now: 2026-01-18 21:42

  Last rotated at 2026-01-18 06:14

  log does not need rotating (log has been rotated at 2026-01-18 06:14, which is less than a day ago)

considering log /data/nginx/logs/stream.log

  Now: 2026-01-18 21:42

  Last rotated at 2026-01-17 07:00

  log does not need rotating (log is empty)

 [SETTING UP STORAGE /data/nginx/logs/access.log] {0} @ {0/s}
2026/01/18 21:42:28 [notice] 267#267: parsed a resolver: "127.0.0.53" in /usr/local/nginx/conf/nginx.conf:41

2026/01/18 21:42:28 [notice] 267#267: parsed a resolver: "127.0.0.53" in /usr/local/nginx/conf/nginx.conf:289

2026/01/18 21:42:28 [error] 267#267: [lua] crowdsec.lua:229: init(): APPSEC is enabled on '127.0.0.1:7422'

2026/01/18 21:42:28 [alert] 267#267: [lua] crowdsec.conf:2):8: [Crowdsec] Initialisation done

|2026-01-18T21:42:28.564: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 286] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.564: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 279] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.564: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:504 [uid  | pid 279] | Configured workers amount: 12

|2026-01-18T21:42:28.564: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:522 [uid  | pid 279] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000

|2026-01-18T21:42:28.564: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:536 [uid  | pid 279] | Nginx version does not support async mode

|2026-01-18T21:42:28.564: register_workers@ngx_cp_initializer.c:107 [uid  | pid 279] | Initiating registration of 12 workers to the attachment

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 350] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 344] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 410] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 380] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 280] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 351] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 429] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 456] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 298] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.572: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 504] | entering init worker. ngx_exiting=0

 [PARSING /data/nginx/logs/access.log] {2179} @ {0/s}
 [PARSING /data/nginx/logs/access.log] {5064} @ {0/s}
|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 456] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.568: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 298] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:28.572: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 504] | entering init worker. ngx_exiting=0

 [PARSING /data/nginx/logs/access.log] {2179} @ {0/s}
 [PARSING /data/nginx/logs/access.log] {5064} @ {0/s}


WebSocket server ready to accept new client connections

[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 4 /usr/local/nginx/conf/conf.d/default.conf

[Certbot       ] › ▶  start     Installing cloudflare...

[Global        ] › ⬤  debug     CMD: pip install --upgrade --no-cache-dir certbot-dns-cloudflare

[Certbot       ] › ☒  complete  Installed cloudflare

[Global        ] › ℹ  info      IP Ranges fetch is disabled by environment variable

[SSL           ] › ℹ  info      Certbot Renewal Timer initialized

[SSL           ] › ℹ  info      Renewing Certbot TLS certs close to expiry...

[Global        ] › ⬤  debug     CMD: certbot --config /etc/certbot.ini renew --server https://acme-v02.api.letsencrypt.org/directory --quiet

[Global        ] › ⬤  debug     CMD: nginx -tq

[Global        ] › ℹ  info      Backend PID 268 listening on unix socket...

[Global        ] › ⬤  debug     CMD: nginx -s reload

2026/01/18 21:42:30 [error] 267#267: [lua] crowdsec.lua:229: init(): APPSEC is enabled on '127.0.0.1:7422'

2026/01/18 21:42:30 [alert] 267#267: [lua] crowdsec.conf:2):8: [Crowdsec] Initialisation done

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 696] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:504 [uid  | pid 696] | Configured workers amount: 12

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:522 [uid  | pid 696] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000

|2026-01-18T21:42:30.516: register_workers@ngx_cp_initializer.c:107 [uid  | pid 696] | Initiating registration of 12 workers to the attachment

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:536 [uid  | pid 696] | Nginx version does not support async mode

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 711] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 697] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.516: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 761] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.520: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 814] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.520: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 829] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.520: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 843] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.520: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 730] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.520: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 786] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.520: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 934] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.524: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 901] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.524: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 865] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 380] | |2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 280] | entering fini worker. is_timer_active=0, ngx_exiting=1

entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 344] | |2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 286] | entering fini worker. is_timer_active=0, ngx_exiting=1

entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 351] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 504] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 456] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 298] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.620: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 429] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.624: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 410] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:30.632: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 350] | entering fini worker. is_timer_active=0, ngx_exiting=1

[Global        ] › ⬤  debug     CMD: nginx -tq
[Global        ] › ⬤  debug     CMD: nginx -s reload

[SSL           ] › ℹ  info      Renew Complete

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-1/fullchain.pem -subject -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-2/fullchain.pem -subject -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-1/fullchain.pem -issuer -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-2/fullchain.pem -issuer -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-1/fullchain.pem -dates -noout

2026/01/18 21:42:30 [error] 267#267: [lua] crowdsec.lua:229: init(): APPSEC is enabled on '127.0.0.1:7422'

2026/01/18 21:42:30 [alert] 267#267: [lua] crowdsec.conf:2):8: [Crowdsec] Initialisation done

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-2/fullchain.pem -dates -noout

|2026-01-18T21:42:30.980: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1102] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.980: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1104] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:30.980: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1152] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.980: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1166] | |2026-01-18T21:42:31.980: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1123] | entering init worker. ngx_exiting=0

entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1101] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:504 [uid  | pid 1101] | Configured workers amount: 12

|2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:522 [uid  | pid 1101] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000

|2026-01-18T21:42:31.984: register_workers@ngx_cp_initializer.c:107 [uid  | pid 1101] | Initiating registration of 12 workers to the attachment

|2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:536 [uid  | pid 1101] | Nginx version does not support async mode

|2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1300] | |2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1189] | entering init worker. ngx_exiting=0

entering init worker. ngx_exiting=0
|2026-01-18T21:42:31.984: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1302] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.988: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1435] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.992: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1301] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.992: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1411] | entering init worker. ngx_exiting=0

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 697] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 843] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 730] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 761] | |2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 901] | entering fini worker. is_timer_active=0, ngx_exiting=1

entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 934] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 786] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 829] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 865] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 711] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:31.088: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 814] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:38.492: ngx_send_keep_alive@ngx_http_cp_attachment_module.c:362 [uid  | pid 279] | exiting without re-sched of ngx_send_keep_alive . ngx_exiting=1

|2026-01-18T21:42:38.492: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 279] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:38.492: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:560 [uid  | pid 279] | Timer successfully deleted

|2026-01-18T21:42:40.452: ngx_send_keep_alive@ngx_http_cp_attachment_module.c:362 [uid  | pid 696] | exiting without re-sched of ngx_send_keep_alive . ngx_exiting=1

|2026-01-18T21:42:40.452: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 696] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:42:40.452: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:560 [uid  | pid 696] | Timer successfully deleted

[alainq79]

Log with the two line:

Version:  2026-01-17-r3-6053d73-2.13.6

Date:     Sun Jan 18 21:34:22 CET 2026

-------------------------------------

no DEFAULT_CERT_ID set, using dummycerts.

removed '/usr/local/nginx/logs/nginx.pid'

removed '/run/goaccess.sock'

removed '/run/npmplus.sock'

-------------------------------------

User:     root

PUID:     0

User ID:  0

PGID:     0

Group ID: 0

-------------------------------------

Starting services...

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

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-01-18 21:34

  Last rotated at 2026-01-18 06:14

  log does not need rotating (log has been rotated at 2026-01-18 06:14, which is less than a day ago)

considering log /data/nginx/logs/error.log

  Now: 2026-01-18 21:34

  Last rotated at 2026-01-18 06:14

  log does not need rotating (log has been rotated at 2026-01-18 06:14, which is less than a day ago)

considering log /data/nginx/logs/stream.log

  Now: 2026-01-18 21:34

  Last rotated at 2026-01-17 07:00

  log does not need rotating (log is empty)

 [SETTING UP STORAGE /data/nginx/logs/access.log] {0} @ {0/s}
2026/01/18 21:34:23 [notice] 268#268: parsed a resolver: "127.0.0.53" in /usr/local/nginx/conf/nginx.conf:41

2026/01/18 21:34:23 [notice] 268#268: parsed a resolver: "127.0.0.53" in /usr/local/nginx/conf/nginx.conf:289

2026/01/18 21:34:23 [error] 268#268: [lua] crowdsec.lua:229: init(): APPSEC is enabled on '127.0.0.1:7422'

2026/01/18 21:34:23 [alert] 268#268: [lua] crowdsec.conf:2):8: [Crowdsec] Initialisation done

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 280] | |2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 281] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 282] | entering init worker. ngx_exiting=0

entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 339] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 302] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 279] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:504 [uid  | pid 279] | Configured workers amount: 12

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:522 [uid  | pid 279] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000

|2026-01-18T21:34:23.732: register_workers@ngx_cp_initializer.c:107 [uid  | pid 279] | Initiating registration of 12 workers to the attachment

|2026-01-18T21:34:23.732: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:536 [uid  | pid 279] | Nginx version does not support async mode

|2026-01-18T21:34:23.736: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 451] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.736: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 472] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.736: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 415] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.736: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 501] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:23.736: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 486] | entering init worker. ngx_exiting=0

 [PARSING /data/nginx/logs/access.log] {2048} @ {0/s}
|2026-01-18T21:34:23.744: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 378] | entering init worker. ngx_exiting=0

 [PARSING /data/nginx/logs/access.log] {4513} @ {0/s}


WebSocket server ready to accept new client connections

[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 4 /usr/local/nginx/conf/conf.d/default.conf

[Certbot       ] › ▶  start     Installing cloudflare...

[Global        ] › ⬤  debug     CMD: pip install --upgrade --no-cache-dir certbot-dns-cloudflare

[Certbot       ] › ☒  complete  Installed cloudflare

[Global        ] › ℹ  info      IP Ranges fetch is disabled by environment variable

[SSL           ] › ℹ  info      Certbot Renewal Timer initialized

[SSL           ] › ℹ  info      Renewing Certbot TLS certs close to expiry...

[Global        ] › ⬤  debug     CMD: certbot --config /etc/certbot.ini renew --server https://acme-v02.api.letsencrypt.org/directory --quiet

[Global        ] › ⬤  debug     CMD: nginx -tq

[Global        ] › ℹ  info      Backend PID 269 listening on unix socket...

[Global        ] › ⬤  debug     CMD: nginx -s reload
2026/01/18 21:34:25 [error] 268#268: [lua] crowdsec.lua:229: init(): APPSEC is enabled on '127.0.0.1:7422'

2026/01/18 21:34:25 [alert] 268#268: [lua] crowdsec.conf:2):8: [Crowdsec] Initialisation done

|2026-01-18T21:34:25.624: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 707] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.624: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 696] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.624: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:504 [uid  | pid 696] | Configured workers amount: 12

|2026-01-18T21:34:25.624: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:522 [uid  | pid 696] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000

|2026-01-18T21:34:25.628: register_workers@ngx_cp_initializer.c:107 [uid  | pid 696] | Initiating registration of 12 workers to the attachment

|2026-01-18T21:34:25.628: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:536 [uid  | pid 696] | Nginx version does not support async mode

|2026-01-18T21:34:25.628: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 697] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.628: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 743] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.628: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 795] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.628: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 829] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.632: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 859] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.632: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 922] | |2026-01-18T21:34:25.632: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 887] | entering init worker. ngx_exiting=0

entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.632: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 965] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.632: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1002] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.636: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1043] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 302] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 486] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 501] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 472] | |2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 282] | entering fini worker. is_timer_active=0, ngx_exiting=1

entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 415] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 451] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 339] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.732: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 281] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.736: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 280] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:25.736: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 378] | entering fini worker. is_timer_active=0, ngx_exiting=1

[Global        ] › ⬤  debug     CMD: nginx -tq

[Global        ] › ⬤  debug     CMD: nginx -s reload

[SSL           ] › ℹ  info      Renew Complete

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-1/fullchain.pem -subject -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-2/fullchain.pem -subject -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-1/fullchain.pem -issuer -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-2/fullchain.pem -issuer -noout

2026/01/18 21:34:26 [error] 268#268: [lua] crowdsec.lua:229: init(): APPSEC is enabled on '127.0.0.1:7422'

2026/01/18 21:34:26 [alert] 268#268: [lua] crowdsec.conf:2):8: [Crowdsec] Initialisation done

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-1/fullchain.pem -dates -noout

[Global        ] › ⬤  debug     CMD: openssl x509 -in /data/tls/certbot/live/npm-2/fullchain.pem -dates -noout

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1106] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1101] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:504 [uid  | pid 1101] | Configured workers amount: 12

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:522 [uid  | pid 1101] | Timer successfully added. Keep alive interval: 300000, timer interval: 10000

|2026-01-18T21:34:26.072: register_workers@ngx_cp_initializer.c:107 [uid  | pid 1101] | Initiating registration of 12 workers to the attachment

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:536 [uid  | pid 1101] | Nginx version does not support async mode

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1129] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.072: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1194] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.076: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1159] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.076: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1249] | |2026-01-18T21:34:26.076: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1278] | entering init worker. ngx_exiting=0

entering init worker. ngx_exiting=0
|2026-01-18T21:34:26.076: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1270] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1219] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1412] | |2026-01-18T21:34:26.080: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1376] | entering init worker. ngx_exiting=0

entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.092: ngx_cp_attachment_init_worker@ngx_http_cp_attachment_module.c:485 [uid  | pid 1448] | entering init worker. ngx_exiting=0

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 707] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 859] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 697] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 965] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 743] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 1002] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 887] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.180: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 1043] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.184: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 795] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.192: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 829] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:26.556: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 922] <session id 3> | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:33.648: ngx_send_keep_alive@ngx_http_cp_attachment_module.c:362 [uid  | pid 279] | exiting without re-sched of ngx_send_keep_alive . ngx_exiting=1

|2026-01-18T21:34:33.648: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 279] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:33.648: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:560 [uid  | pid 279] | Timer successfully deleted

|2026-01-18T21:34:35.564: ngx_send_keep_alive@ngx_http_cp_attachment_module.c:362 [uid  | pid 696] | exiting without re-sched of ngx_send_keep_alive . ngx_exiting=1

|2026-01-18T21:34:35.568: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:545 [uid  | pid 696] | entering fini worker. is_timer_active=0, ngx_exiting=1

|2026-01-18T21:34:35.568: ngx_cp_attachment_fini_worker@ngx_http_cp_attachment_module.c:560 [uid  | pid 696] | Timer successfully deleted

[Zoey2936]

can show the request sent by your browser (F12) and the response of NPMplus?

[alainq79]

I was unable to reproduce the failure, as the container refused to start if the lines were not configured correctly.
When it started normally, it gave this result =>

Maybe, i've an idea... or not

This morning, I edit the administrator account and change email adress=> it work !
then create a new administrator user => Now, it work !

when i'm login with the first account, i try to edit 1st account then =>

when i'm login with the first account, i try to edit 2nd account then =>

when i'm login with the second account, i try to edit 1st account then =>

when i'm login with the second account, i try to edit 2nd account then =>

Everything seems to be working normally.

In my opinion, the first user needs to change their email address for the program to work normally.
But this remark is no longer relevant if we are starting from a new installation from 19/01/2026.

[alainq79]

Geoblocking example

the issues you had could be because you already had hosts based on the other example

Despite following your advice, I was unable to follow the online example in the README.md file.
Then, I deleted the NPMplus container, as well as the directory that contained it.
I did a fresh install of NPMplus (actually it's much better than before).
I reconnected to Crowdsec, it seems to be working.

I then tried to install geoblocking by following the instructions in the README.md file.
Copy/Past into: /opt/npmplus/custom_nginx/http_top.conf

geoip2 /data/goaccess/geoip/GeoLite2-Country.mmdb {
  auto_reload 60m;
  $geoip2_country_iso_code country iso_code;
}

# whitelist example, you can add as many country codes as you want, country code list: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#XY
map $geoip2_country_iso_code $geoip2_country_rule {
  default no;
  FR yes;
#  XY yes;
#  '' yes; # if you want to allow IPs with unknown country codes, if you don't do this make sure to allow private IPs
}

# blacklist example, you can add as many country codes as you want, country code list: https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#XY
#map $geoip2_country_iso_code $geoip2_country_rule {
#  default yes;
#  AA no;
#  XY no;
#  '' no; # if you want to block IPs with unknown country codes, if you do this make sure to allow private IPs
#}

# uncomment if you block/don't allow IPs with unknown country codes
geo $geo_is_private_ip {
  default no;
  127.0.0.0/8 yes;
  10.0.0.0/8 yes;
  172.16.0.0/12 yes;
  192.168.0.0/16 yes;
  169.254.0.0/16 yes;
#  ::1/128 yes;
#  fc00::/7 yes;
#  fec0::/10 yes;
}

Put the script in :

Try to connect with tor => fail = normal
Try to connect with firefox private IP => OK
Try to connect with smartphone on GSM =>OK
Work perferctly.
When someone does good work, you should tell them. You and the others who helped you did a good job.

I still have Anubis to do (tomorrow), I can only help you with the French translation, editing a PR is too complicated for me.

I need to find a good Youtuber to explain PHP-FMP and load balancing to me, and understand the benefit it might or might not have on my installation.

[alainq79]

Anubis

the auth_request line needs to be in a custom location with the path /, it doesn't work in the advanced config since with this you create an infinite loop:
you try to access the site => nginx trys to ask anubis => to ask anubis you need to be allowed by anubis => infinite loop

Finally, I found the solution for Anubis. Now it works!
It's easier for me to have a visual reference point, like the two that will follow.
The idea came to me while watching your Nextcloud AIO proxy tutorial (https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md).

The first one, without geoblocking:

3. Put this in the advanced tab or create a custom location / (or the location you want to use), set your proxy settings, then press the gear button and paste the following in the new text field:

auth_request /.within.website/x/cmd/anubis/api/check;
error_page 401 403 =200 /.within.website/?redir=$request_uri;

Example:

4. Then press the Add Location button
5. Create a location with the path /.within.website, this should proxy to your anubis, example: http://127.0.0.1:8923, then press the gear button and paste the following in the new text field

proxy_redirect ~^[^/]+/.*$ /;
proxy_method GET;
proxy_pass_request_body off;
proxy_set_header Content-Length "";

Example:

The second one with geobloking: