Yesterday I decided to give the CLI a go. I downloaded it to it's own directory and then downloaded a packet. I then made a shortcut to it in my startup bar with the options -proxy 192.168.0.1:5517 -verbose so that it would access Seti Queue. When I woke up this morning I noticed that it completed a packet and sent it to SetiQueue for cache, but it's not getting a cached packet from SetiQueue. I also tried the option -proxy 127.0.0.1:5517 but it doesn't work either. How do I get the CLI to get a packet from SetiQueue?