[SOLVED] cannot login in right after installation

  • Hi,

    I installed Bloonix on my Debian Server (Debian 12.8 bookworm) according to the official documentation [1] and all three components (agent, server, webgui) work seemingly without problems, but I cannot login with the admin user after the installation. The credentials are correct (admin / bloonix) and I do not get the error "Bad login!", but all that happens is the login form refreshing, resetting and not logging me in.


    This is what a login currently looks like in bloonix-webgui.log

    Jan 10 2025 10:23:35 DEBUG 7225 0.016492 found route: login - 
    Jan 10 2025 10:23:35 DEBUG 7225 0.000188 got route bloonix_webgui.controller.login -> login - 
    Jan 10 2025 10:23:35 DEBUG 7225 0.000108 route options {} - 
    Jan 10 2025 10:23:35 NOTICE 7225 0.000121 exec module bloonix_webgui.controller.login action login opts {} - 
    Jan 10 2025 10:23:35 DEBUG 7225 0.000111 call bloonix_webgui.controller.root -> auto - 
    Jan 10 2025 10:23:35 INFO 7225 0.000225 connect to database - 
    Jan 10 2025 10:23:35 INFO 7225 0.039816 sql exec: select "sys_options".* from "sys_options" where "key" = %s ['has_maintenance'] - 
    Jan 10 2025 10:23:35 DEBUG 7225 0.003801 call bloonix_webgui.controller.login -> login - 
    Jan 10 2025 10:23:35 DEBUG 7225 0.000372 call bloonix_webgui.controller.root -> end - 
    Jan 10 2025 10:23:35 NOTICE 7225 0.000448 finished request /login (took 0.5006961822509766s) - 
    Jan 10 2025 10:23:35 INFO 7225 0.000413 disconnect from database - 
    Jan 10 2025 10:23:35 INFO 7225 0.000665 process view jinja - 
    Jan 10 2025 10:23:35 NOTICE 7225 0.003133 start processing template login.html - 
    Jan 10 2025 10:23:35 INFO 7225 0.000579 res: Content-Type: text/html; charset=utf-8 - 
    Jan 10 2025 10:23:35 INFO 7225 0.000348 res: Content-Length: 2103 bytes - 
    Jan 10 2025 10:23:35 INFO 7225 0.000400 res: http status 200 OK -

    Anybody out there with a solution for this?


    Thanks in advance!


    [1] https://docs.bloonix.org/en/installation/debian

  • Jonny 10. Januar 2025 um 09:33

    Hat das Thema freigeschaltet.
    • Offizieller Beitrag

    Ok, the problem is that the connection is not "secure". The cookie is set with the tag "secure", which requires an HTTPS connection.

    To solve the problem, open the configuration file /etc/bloonix/webgui/main.conf, set the parameter "cookie_secure False" and restart the webgui. After that it should work.

    I will update the documentation accordingly.

  • Eisheexein8Ze9Ab 10. Januar 2025 um 11:42

    Hat den Titel des Themas von „cannot login in right after installation“ zu „[SOLVED] cannot login in right after installation“ geändert.
  • I have installed bloonix NMS on a debian12 server (without gui). Installed as per the instructions given, without any hiccups. Wanted to test without ssl, and also changed the flag "cookie_secure" to False. I am trying to access the server from another machine using the following

    http://192.168.0.197:5432

    192.168.0.197 is the server IP address

    Unable to connect, says "Connection Refused"

    Please suggest , how to proceed further

  • Yes, I did restart the nginx server. I am including some output

    partial output of bloonix-webgui.log

    Mar 06 2025 06:08:28 NOTICE 452 0.000070 load model bloonix_webgui.model.db -
    Mar 06 2025 06:08:28 WARNING 452 0.095137 Exception occurred:
    Traceback (most recent call last):
    File "/srv/bloonix/webgui/lib/bloonix_webgui/model/db/__init__.py", line 54, in __init__
    db_lock.connect()
    File "/usr/lib/python3/dist-packages/bloonix/dbi/base.py", line 99, in connect
    self._connect()
    File "/usr/lib/python3/dist-packages/bloonix/dbi/pg.py", line 15, in _connect
    self.dbh = psycopg2.connect(
    ^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/psycopg2/__init__.py", line 122, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    psycopg2.OperationalError: connection to server at "127.0.0.1", port 5432 failed: Connection refused
    Is the server running on that host and accepting TCP/IP connections?

    curl output:

    bloom@bloonixNMS:/$ curl http://192.168.0.197:8080
    curl: (7) Failed to connect to 192.168.0.197 port 8080 after 0 ms: Couldn't connect to server
    bloom@bloonixNMS:/$

    Einmal editiert, zuletzt von kamal3965 (6. März 2025 um 12:10) aus folgendem Grund: In nginx.conf, i have changed the server name to: server { listen 8080 default_server; # listen [::]:8080 default_server; server_name bloonixNMS;

    • Offizieller Beitrag

    Okay, then please check why a connection to the database is not possible. Is the database actually running on 127.0.0.1:5432? Were you able to install the plugins via bloonix-import-plugins-into-db? Is it possible to connect to the database using "psql -U blxdb -h localhost"? The connection data is in /etc/bloonix/database/main.conf. Is the connection perhaps being prevented by apparmor, selinux or firewall?

    The same applies to Nginx. Is Nginx listening on 192.168.0.197:8080? Does the hostname bloonixnms.csiriict.in (case-insensitive!) resolve to the IP? Does "curl bloonixnms.csiriict.in:8080" work? Is there a firewall active that is rejecting the connection?

    BTW you can remove default_server.

    If you follow the steps correctly according to the HowTo on Debian 12, everything will work perfectly.

    • Offizieller Beitrag

    No sorry :(

    At this point, it would be beneficial for you to familiarize yourself with the basics of Linux/Nginx/PostgreSQL and system diagnostics (e.g., checking logs, verifying process status). I can't walk you through every single step, but there are plenty of good guides available. Try reading up on these topics and experimenting a bit on your own.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!