Notifications via docker compose question #318
Replies: 1 comment
-
|
Problem solved. Or rather, the testing was flawed. If I send the test from the parent directory, it succeeds. Clearly the ability to connect to localhost:8080 is something I need to understand better but this query can be closed for now. Thanks for reading. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. I wonder if someone is willing to assist with this query.
I have just moved from the AnalogJ repo in the last 24-36 hours by replacing all the binaries on the endpoints and changing the image in the docker compose file. I use binaries with scheduled tasks on them to send and a hub with docker compose. I do not use config.yaml files on any of them. All using defaults except the hub which is using a docker compose file.
This is the setup that has worked before for notifications. I am using mattermost, hosted as another container on the same host i.e. sits alongside scrutiny.
However this is my problem, the notifications aren't working. Testing with
curl -X POST http://localhost:8080/api/health/notifyon the docker container of the hub errors with{"errors":["failed to send using mattermost: timed out"],"success":false}.Frustratingly there are no errors on the mattermost server that I can spot.
I am hoping that my problem is that I need to change something on the compose for this repo.
This is the setting in my docker compose:
As mentioned earlier. This worked fine when the image was analogj. That was the only change on the compose file above.
Additional info:
A test succeeds from outside scrutiny, still inside the host:
$ curl -i -X POST -H 'Content-Type: application/json' -d '{"text": "Hello, this is some text\nThis is more text. :tada:"}' https://mydomain/hooks/x3zfc96h7brizyk9d1xy7hbgrcthis confirms the webhook is working, can receive messages. I have tested with and without the "hooks" element in the url, which when getting it to work with analogj proved to need to be dropped from the scrutiny configuration in the compose.
Logs for this successful test in mattermost:
{"timestamp":"2026-03-03 12:54:51.973 Z","level":"debug","msg":"Received HTTP request","caller":"web/handlers.go:175","method":"POST","url":"/hooks/x3zfc96h7brizyk9d1xy7hbgrc","request_id":"u1mcu3atetdimrjrk47nffqydc","status_code":"200"}This now is a test with the health/notify endpoint and logs from the time window. In case it helps. We can ignore the "your license does not support..." as is I believe an outstanding mattermost issue.
Sending:
Receiving end:
Beta Was this translation helpful? Give feedback.
All reactions