-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cachet Auth Issues #33
Comments
Hi,
Why you use Cachet token in base64 encoding?
Did you get it from web interface?
On Wed, Mar 28, 2018, 6:34 PM Don Richards ***@***.***> wrote:
Possible auth issues?
Trying to set up for the first time. Ran the zabbix-cachet.py with the
following error(s). Not sure what I'm doing wrong or what I've missed.
$ ./zabbix-cachet.py
2018-03-28 11:26:10 EDT INFO: (MainThread) Zabbix Cachet v.1.3.4 started
2018-03-28 11:26:10 EDT INFO: (MainThread) JSON-RPC Server Endpoint: https://zmonitor.lib.utk.edu/api_jsonrpc.php
2018-03-28 11:26:10 EDT INFO: (MainThread) Zabbix ver: 3.2.11. Cachet ver: 2.3.9
2018-03-28 11:26:10 EDT ERROR: (MainThread) ClientHttpError[https://cachet.example.com/api/v1/components, 401: {"errors":[{"id":"00452337-0803-45ef-8d6b-26324ff860ec","status":401,"title":"Unauthorized","detail":"Authentication is required and has failed or has not yet been provided."}]}]
2018-03-28 11:26:10 EDT ERROR: (MainThread) 'NoneType' object is not subscriptable
File: config.yml
Not my actual values (obviously) but wasn't sure what needs to be wrapped
(if anything) in quotes. And I removed comment fields for this issue post.
The service name is the URL of the service (something.example.com). I did
try to just aim it at the root ('/') with no luck. Root would be preferred.
zabbix:
user: read_access_only_user
pass: this_is_my_password
server: https://zabbix.example.com
https-verify: true
cachet:
token: base64:Not_REAL-HNvyVLGYaUyhOfEsMcKIhTHhZDmZl4wtnbOS3kyD-Not_REAL=
server: https://cachet.example.com
https-verify: true
settings:
root_service: 'something.example.com'
update_inc_interval: 120
update_comp_interval: 3600
log_level: INFO
log_level_requests: WARNING
templates:
acknowledgement: "{message}\n\n###### {ack_time} by {author}\n\n______\n"
investigating: "{group} | {component} check **failed** - {time}\n\n```{trigger_name}```"
resolving: "__Resolved__ - {time}\n\n______\n"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIAVS6uX0mRox9QBMA6oky_VjrrSv5ayks5ti62IgaJpZM4S-4EB>
.
--
Best regards, Artyom
|
Yes. That is what was auto generated. |
And I see the issue. Cachet generates a key during setup. For some reason I thought this was the key to be used. Made the change and we're up and running. Thanks for getting back quickly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Possible auth issues?
Trying to set up for the first time. Ran the zabbix-cachet.py with the following error(s). Not sure what I'm doing wrong or what I've missed.
File: config.yml
Not my actual values (obviously) but wasn't sure what needs to be wrapped (if anything) in quotes. And I removed comment fields for this issue post. The service name is the URL of the service (something.example.com). I did try to just aim it at the root ('/') with no luck. Root would be preferred.
The text was updated successfully, but these errors were encountered: