Replies: 3 comments
-
The following two sections of code in the docker-compose-v3.yml file do not work for me:
I tried changing the paths but nothing worked. I ended up replacing each section of code with an
I was able to get things running by making sure all of the following exist in BOTH the frontend and switchboard environments (.env files):
This should be documented somewhere that ALL of the above need to be included in both environments. However, I'm still not getting alerts. I opened #159 to report this issue. As of this post, I switched back to v2 and everything is working but I would like to use v3. |
Beta Was this translation helpful? Give feedback.
-
Hi @jeffshead, Sorry for the delay here. We haven't been keeping a sharp eye on the discussions (but we've made notes that we should so hopefully better going forward). I just want to check if you still hitting this issue? We did a bit of an overhaul end of last year to get everything running smoothly. |
Beta Was this translation helpful? Give feedback.
-
I resolved this issue and posted what I did in #159. |
Beta Was this translation helpful? Give feedback.
-
I had CanaryTokens up and running 7-10 months ago but I recently lost my entire server. I kept detailed notes so I rebuilt everything but I can't get things to work with the new v3 docker image of canarytokens-docker.
I am using a AlmaLinux 9.3 server with Portainer and everything is behind the Nginx Proxy Manager (NPM) reverse-proxy Docker container which is hosted on the same server.
If I pull
thinkst/canarytokens:v2_latest
, everything works.However, when I try the latest v3 image, I'm getting a 502 gateway error (nginx).
In Portainer, these are the internal IP's assigned to the containers:
In NPM, I have the following for the destination in my proxy host for canarytokens-docker:
http://nginx:80
This works with canary-tokens v2.
Canarytokens-docker nginx container log:
Canarytokens-docker frontend container log:
Canarytokens-docker redis container log:
Canarytokens-docker switchboard container log:
Can v3 be made to work with my server setup? If so, what needs to be changed?
Beta Was this translation helpful? Give feedback.
All reactions