Login problem after upgrade to 26.5.1

Help
1

After updating a docker compose based installation by docker compose down and then using docker compose pull and docker compose up -d, I can’t relogin to the librenms instance using passwords that were working with the previous version. Previous version: 26.4.1 New version: 26.5.1. I have setup LDAP authentication against Microsoft Active directory and everything was working even across upgrades before.
Also the login window looks different and I get a warning about non secure transactions for this website so to be sure to send over data or not.

Here is the output from validate.php (I don’t believe this will help with what is going on)
librenms:/opt/librenms$ ./validate.php

Component Version
LibreNMS 26.5.1 (2026-05-21T10:11:11+03:00)
DB Schema 2026_05_06_145721_regenerate_devices_table_display_field (386)
PHP 8.4.21
Python 3.12.13
Database MariaDB 10.11.17-MariaDB-ubu2204
RRDTool 1.9.0
SNMP 5.9.5.2
===========================================

[OK] Installed from package; no Composer required
[OK] Database Connected
[OK] Database Schema is current
[OK] SQL Server meets minimum requirements
[OK] lower_case_table_names is enabled
[OK] MySQL engine is optimal
[OK] Database and column collations are correct
[OK] Database schema correct
[OK] MySQL and PHP time match
[OK] Active pollers found
[OK] Dispatcher Service is enabled
[OK] Locks are functional
[OK] No python wrapper pollers found
[OK] Redis is functional
[OK] rrd_dir is writable
[FAIL] Some RRD files have the incorrect step. 366/30112
[FIX]:
lnms maintenance:rrd-step all
RRD files with incorrect step:
(skipping the ip addresses mentioned - I had changed the polling interval)
and 351 more…
[OK] rrdtool version ok
[WARN] Non-git install, updates are manual or from package

1 Like
2

It seems to have been an issue with APP_TRUSTED_PROXIES.
I added the APP_TRUSTED_PROXIES=** in the .env file and then the env variable in the compose file in all the librenms related nodes (probably only needed in the main one):
- "APP_TRUSTED_PROXIES=${APP_TRUSTED_PROXIES}"
under
environment:
That fixes the issue.
See Environment Variables - LibreNMS Docs in the documentation. There was a relevant notification in the webui that pointed me towards that:

Trusted Proxies default change
In order to improve the default security of LibreNMS. The default trusted proxies (APP_TRUSTED_PROXIES) will be changed to 127.0.0.1 from * on the 6th of May, 2026 and the 26.5 release. If you use reverse proxeis, update your APP_TRUSTED_PROXIES setting to include your reverse proxy IPs to avoid any issues with the change is applied”

1 Like
3

FYI, you should not set APP_TRUSTED_PROXIES=* or APP_TRUSTED_PROXIES=** in production. This leaves your install vulnerable to authentication bypass in some situations.

And yes, you only need to set it in .env. However, .env is cached, so run lnms optimize to update the cache immediately.

Set it to the actual IP(s) of your reverse proxies.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.