• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SetiQueue problem...OrangeKid?

Osmo --

Try using this IP for your proxy server in your queue server settings: 24.25.120.113. This is what I've used since his ISP changed his IP and I haven't had any problems.

Does somebody know if his DSN is still screwed up?
 
Ok, here is my guess...

I used the client merge utility of my SetiQueue to make the results from my work fleet and my home system appear as one client. Since OK's server has two clients listed there, I'm guessing that it is refusing them because it is expecting the results from the other user? So perhaps merges have to be cascaded upstream when nesting proxy connections? OrangeKid, what do you think? Regards,

Osmo.
 
It looks like it is a duplicate result and that one was waiting to be sent. I hve flushed the Q so now maybe yours will work ok.

My merging of clients doesn't seem to work or I don't know what I'm doing, probably the latter, I'll have to do some reading and then I'll try to merge your clients here also.

I did notice a new feature to name the clients and somewhat mask IP's so will do that for all as time allows.
 
I did notice a new feature to name the clients and somewhat mask IP's so will do that for all as time allows

I did that to mine a couple weeks ago when I accidently stumbled upon the feature. Kinda cool as it gets rid of the display of the inpersonal IPs/hostnames that are there by default. 🙂
 
Back
Top