Hmm - looks like it is talking to the agent fine but it never gets to the point where it requests work. Could be a race condition in the firefox extension (believe it attaches to a startup event). I’ll take a look and see if I can make that code more robust and send an updated agent over for testing.
Looks like I managed to reproduce it on my dev system when I went to try to put in some extra hardening. For some reason Firefox isn’t loading the extension at all and it’s not immediately clear why.
It’s my top priority and I’m holding up the next agent release which has a few other goodies in it until I get it fixed so hopefully I’ll have a good handle on it tomorrow.
ok, in my case it was because the files under “templates/firefox” were marked as read only. You can try manually clearing the flag on the files or grab the agent update that I just released which automatically clears the read only bit if it is set as it sets up the firefox profile.
I also added some extra logic to the extension to make it more resilient in case your issue was different but the behavior was identical so I’m cautiously optimistic that it should work now.