TriggerCMD down?
-
Consistently getting login errors today. Can’t get to any of my triggers on any of my multiple computers, and my automation tasks can’t access them either. Anybody else dealing with this?
-
@Avik-Basu I have major issues today
-
@Avik-Basu I Can get my triggers to work sometimes, but most often the trigger is very delayed or not triggered at all.
-
@OPTIMUS-PЯIMΞ I’m seeing the same thing as you now - periodically able to access and trigger commands, but then get an access error for several minutes. Issues started about 4 or 5 hours ago. Appears to be improving but would love to hear an update from anyone that knows why this is happening. I’ve been using TriggerCMD for about 4 months and never had an issue. Really like this program and find the support and discussion resources to be very helpful.
-
@Avik-Basu I have used this for years, this is a temporary issue, probably with a datacenter or such. Hopefully someone can fix it soon.
-
@Avik-Basu I updated the client, could be worth a try and see if it helps, it seems to have helped me. Rightclick on the icon and choose "Update agent".
-
@OPTIMUS-PЯIMΞ , sorry guys. There was an outage this morning but it's fixed now.
I'm not sure, but it was likely a denial of service attack.
I figured out what was happening and patched the code so it can't happen again.
-
@Russ Thanks for the fix! Do I need to update the agent or am I good to keep running as is? I’m a few hours away from the remote computers so just wondering.
-
@Avik-Basu the agent is fine, no need to update. I patched it on the server side.
BTW this is where I keep track of agent version releases:
https://www.triggercmd.com/forum/topic/14/triggercmd-agent-versions -
it is down now, don't know if is related to alexa skill or to triggercmd
-
@Mark-Hollis, it's not down and it looks like it wasn't down at all today. What problem are you seeing?
-
@Russ yes it was down for about 2 hours yesterday, now work correctly
