Solved Ackee - How to: CORS headers, reverse proxy?
I am out of my depth here. Would someone be able to help me figure this out?
As per this:
https://docs.ackee.electerious.com/#/docs/SSL and HTTPS#recommended-configuration
how can I set this up so that Ackee is actually tracking?
@andxclfor I'd follow this: https://docs.cloudron.io/apps/ackee/#adding-a-domain
For CORS you edit the env file and put your domain in the variable "ACKEE_ALLOW_ORIGIN". Then in ackee you add your domain, then it will give you JS to put in the website html for tracking.
robi last edited by robi
I'm having an issue with this as well, no tracking is actually happening, mainly because of issues with documentation.
The examples on the github site are flat out wrong, and the Cloudron docs need improvement too.
@staff Here's a short list:
- the example domain is not of your site, but of your ackee install
- the example ackee-tracker.min.js does not exist
- the example path to the tracker does not exist
- CORS preventing self-hosted tracking
- CORS docs not specifying which domain(s) to add (tracker or tracked)
After adding CORS domains to Ackee env file and restarting, FF still won't connect to the ackee API and blocks because of CORS
@robi I put some screenshots and improved it - https://docs.cloudron.io/apps/ackee/#adding-a-domain . Better?
robi last edited by
@girish Yes, it is much better! Thank you.
This also helped me find my issue.
Next question is can a CORS wildcard be added for subdomains.
If not, we'll need a feature request to add to Ackee for a checkbox to add new monitored domains to the env file origins list automatically from the UI.
Not sure, https://github.com/electerious/Ackee/blob/master/docs/Options.md#cors-headers says you can set
ACKEE_ALLOW_ORIGIN="*"which is of course insecure.