res://ieframe.dll/dnserrordiagoff_webOC.htm

[riken]

I'm having this on the browser when working with must of the templates.

res://ieframe.dll/dnserrordiagoff_webOC.htm#httpthe site).com

anybody knows how to fix this?

I'm getting this with and without proxys, when not using proxys I have a 60 mbs conection

 

[Hungry Bulldozer]

How many threads do you run it?

 

[rostonix]

This error occur even when you run 3-4 threads. And occur all the time with all templates even with private proxies.

12 Gb RAM, 60 mbit/sec

Will it be fixed?

 

[riken]

I was running 1 in project maker, after that 10 in zennoposter, got same error in both.

@Rostonix, you mean I have to run a max of 2?

thanks!

 

[rostonix]

I meant that this error happens to everybody on every template in my experience.
And it was mentioned million of times.

I'm just curious if it will be fixed.

 

[riken]

I meant that this error happens to everybody on every template in my experience.
And it was mentioned million of times.

I'm just curious if it will be fixed.

Really? so it's an old one withouth an update... I bought zennoposter 1 week ago, When was the last update? cause I'm finding that there are many errors like this

 

[reislet]

Hmm interesting I got this error while doing debugging on a twitter bot. Any ideas how to fix? Or was it because i clicked the next button too frequently?

 

[reislet]

Ok fixed it, its seems that I added the URL incorrectly or something, is there an issue with https://twitter.com and http://twitter.com?

 

[psyvisions]

Ok fixed it, its seems that I added the URL incorrectly or something, is there an issue with https://twitter.com and http://twitter.com?

What was the problem exactly? I get that same error all the time I work with proxies(private) on twitter! It's driving me crazy!

 

[riken]

I don't know what is this but 80, 90% of my threads get stuck with this error. I hope they get an update on this soon, somewhere I read this guys don't want to publish any update till zennoposter 4, which is a veeeeery bad idea and a good way to lose new clients.
I understand they want to give a big surprise with zenno 4 but don't publishing updates for this kind of error is really bad idea

 

[googlemonster]

I don't know what is this but 80, 90% of my threads get stuck with this error. I hope they get an update on this soon, somewhere I read this guys don't want to publish any update till zennoposter 4, which is a veeeeery bad idea and a good way to lose new clients.
I understand they want to give a big surprise with zenno 4 but don't publishing updates for this kind of error is really bad idea

Does it for me when the site is down