Ad Widget

Collapse

No auth token found, please login before making Zabbix requests

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • armbl
    Junior Member
    • Jun 2026
    • 2

    #1

    No auth token found, please login before making Zabbix requests

    Hello;

    I am currently having an issue with hosts that are using Zabbix sender embedded inside a Kubernetes pod to send data to the server, which is running on Zabbix version 7.4. Despite apparently succeeding in logging into the server, there is an authorization error after the login succeeds mentioning a missing auth token - note that as of currently, I have not set any requirement for an auth token in the system, and the hosts running on Zabbix Agent are connecting properly and functioning as intended despite having no auth token set up. It may be worth mentioning that these hosts were originally directed towards a separate Zabbix server running on version 4.4, and that I am in the process of redirecting them to the new server rather than making them as part of a fresh installation.

    The following is a condensed version of the error that occurs every 5 minutes, with all potentially sensitive information for names of pods and templates removed:
    Code:
    2026-08-20T18:55:34.620+00:00 INF [pod]:  Logging into Zabbix
    2026-08-20T18:55:34.701+00:00 INF [pod]:  Zabbix login successful
    2026-08-20T18:55:34.701+00:00 INF [pod]:  Getting Zabbix template ID for "x"
    2026-08-20T18:55:34.701+00:00 ERR [pod]:  Failed Zabbix upload/host creation with error: No auth token found, please login before making Zabbix requests
    Note that despite claiming that logging in was successful, there are no records on the side of the Zabbix server showing that there was a connection from this IP address.

    Any help would be appreciated, and I thank you for your time.
  • mariusl
    Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Aug 2024
    • 32

    #2
    Hi!

    Note that there are quite some changed from 4.4 to 7.4. In particular, be aware that using a Bearer token in the HTTP header is required since 6.4 when you are not using persistent API tokens. You will get a bearer token in the response after authenticating with username and password, which then must be used for further requests with other methods.

    Related:
    > ZBXNEXT-8051 Authorization method changed from auth parameter to Authorization header.
    > ZBXNEXT-8051 Deprecated parameter auth.


    Apart from that, have you verified that the user account that you are authenticating as has permissions to access the objects you are trying to get, like the template?
    Last edited by mariusl; Today, 11:46.

    Comment

    Working...