-
Notifications
You must be signed in to change notification settings - Fork 51
FAQ & Troubleshooting
Kris Anderson edited this page Apr 16, 2020
·
1 revision
There is can be a large list of reasons for this: -
- If you're using HTTPS, is the certificate valid?
- Are you listeners created and running?
- Is the callback domain DNS record configured correctly?
- Are proxies/reverse proxies in the way?
- Is the domain blacklisted by any TI vendors, or spam engines?
- Is your domain uncategorised?
Often your test environments will differ from the target, but ensuring you've tested as many of the above possibilities should help to avoid common pitfalls.
When configuring the operating hours (and kill date) functionality it uses the system time and date. If a users system is set to another timezone, or the time/date is incorrect the beacons operating hours maybe out.