Whoops, looks like something went wrong. Check your librenms.log - Librenms Portal

[QuocSi_Dao]

Component	Version
LibreNMS	25.10.0-dev.10+8a259d148 (2025-09-18T11:49:07+07:00)
DB Schema	2025_07_29_025425_hr_device_table_add_type_default (354)
PHP	8.4.12
Python	3.10.12
Database	MariaDB 10.6.22-MariaDB-0ubuntu0.22.04.1
RRDTool	1.7.2
SNMP	5.9.1
===========================================
[OK] Composer Version: 2.8.11
[OK] Dependencies up-to-date.
[WARN] You have no devices.

    [FIX]: 
    Consider adding a device such as localhost: /addhost

[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] Locks are functional
[OK] Python poller wrapper is polling
[OK] Redis is unavailable
[OK] rrd_dir is writable
[OK] rrdtool version ok<!–

it is quite headache for me two days without finding root cause of this issue. But validation is fine. But still encountering “Whoops, looks like something went wrong. Check your librenms.log”

[QuocSi_Dao]

Moreover, I don’t see this file librenms.vhost in /etc/nginx/sites-enabled/. I created manually but no hope. I used customized port for nginx to avoid conflict with apache2

nano /etc/nginx/conf.d/librenms.conf

server {
listen 8080;
server_name librenms.grn.com;

[laf]

@QuocSi_Dao

Check your librenms.log”

Have you checked the log file?

[QuocSi_Dao]

Hi laf, thanks for your response. To be honest, nothing special from librenms.log. Moreover, log was not timestamp then it is uncomfortable to parse log. After two days, I did re-install after spending much time. Today, I get this error:
[FAIL] Scheduler is not running
[FIX]:
sudo cp /opt/librenms/dist/librenms-scheduler.service /opt/librenms/dist/librenms-scheduler.timer /etc/systemd/system/
sudo systemctl enable librenms-scheduler.timer
sudo systemctl start librenms-scheduler.timer.

I switch to root user and finish these commands. But .validation still goes on this error.

[QuocSi_Dao]

Solution : Re-installation. Sorry, I don’t have much time to figure out root cause. But this tool is super.

[ccc_c]

Component | Version
--------- | -------
LibreNMS  | 25.10.0-dev.39+db246ff2a (2025-10-01T02:25:15+02:00)
DB Schema | 2025_09_18_132019_add_basic_roles (355)
PHP       | 8.2.29
Python    | 3.11.2
Database  | MariaDB 10.11.14-MariaDB-0+deb12u2
RRDTool   | 1.7.2
SNMP      | 5.9.3
===========================================

[OK]    Composer Version: 2.8.12
[OK]    Dependencies up-to-date.
[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 not detected
[OK]    Locks are functional
[OK]    Python poller wrapper is polling
[OK]    Redis is unavailable
[OK]    rrd_dir is writable
[OK]    rrdtool version ok

Website /alert-rules

Hello everyone, I have a slightly different issue, but it also concerns alerts. Specifically, I’m having problems loading the /alert-rules and /alert-transports pages. This started happening after the last update. Can anyone help me? There’s nothing in the logs, and all other tabs are working.

Edit

The problem was resolved. I found in the log:
[CRITICAL] Exception: Error Class “LibreNMS\Alert\Transport\Weechatbot” not found @ /opt/librenms/LibreNMS/Alert/Transport.php:35

It turned out that the filename and the declared class WeechatBot were incorrect. Something must have changed after the update, because it was class WeechatBot.php — it should be Weechatbot.php and class Weechatbot