robchroma

Figured it out after reading some more threads on this forum. Heavy botting caused a corrupt temp file. Running "Disk Cleanup" fixed everything.

Yes rebooting the PC did not resolve the issue.

The last several support issues I've placed with support have happened to be issues not with Ubot but the specific pc I was trying to run uBot with. In an effort to hopefully solve this without pulling my hair out or badgering support I'm posting here to hopefully find out if anyone else has had similar issues. The issue: All of a sudden a PC that normally ran 5-8 bots can not run more than three. When trying to run more than three bots any subsequent bot pops up with the script tab bar present but without any script tabs present. Sometimes I am able to load 3 bots of one type and a single b

When I originally started using ubot I tried using socks proxies as well. Short story, uBot does not support SOCKS proxies, only HTTP/HTTPS proxies.

make sure you have .net framework 4.5 It's a newer version than is required by ubot 4.

Look for special characters in the body of the emails, make sure you are sanitizing your database input before insersion. characters that can cause problems: ' " &

So flash was the key blah. I had javascript disabled already. I did not realize flash gave them another window.

A site I am automating is using various information given by the browser to profile users on a meta level. This information includes browser version, plugin versions, browser timezone, as well as screen resolution, browser size, and content area size. They are using this and other bits of information to profile users at a level above accounts. Is there any way to deny them this information? short of using IE 6 and another scripting language(which I hear works). At this point I am just trying to spoof as many pieces of the puzzel as I can, Having each ubot window a different size, cycling use

Check for javascript. I know crigslist is comparing screen size vs window size vs viewport size. If you have a large UI they may be picking up on the small displayport.

Update for anyone interested. If you want to post to craigslist: Disable javascript. Cl has implemented some intensive javascript/ajax scripting that if allowed, gives them a very detailed profile of your window size, document size, screen size, and a slough of browser information. This information is added as a hidden input as you click the submit button on the Posting details form.

Were those just examples? I am pretty sure those are not the proper long-form user agents browsers normally send. The issue persists. Looks like I'm going to have to delve into javascript and make a firefox extension to post the ads. Unless there was a change to the browser behavior the past two months that can be reverted, it appears that at least some websites can detect ubot activity as abnormal.

Yes, most of the above was added when it started not to work. One think I have noticed that may be tripping it up is that it seems once you set referrer, it is permanently set until you change it again, is there anyway to make it change referrer as it goes?

My company posts to CL automotive sections using ubot bots. As of recently(past two months) our success rate has plumetted from 75-80%, down to 11-14%. We have determined it is not a proxy or post content issue. When we manual post through firefox, using the same proxies, same content, and even posting faster than our bots do, we achieve 95% or so. The only conclusion to come to is that C raigs L ist is able to determine something wrong with our browser.Here is our startupSteps command that gets ran at the beginning of each post. define StartupSteps { set(#botstatus, "Starting Up"

Most of my bots are internal and consist on one person monitoring a PC running 13-15 bots(8 of one, 3 of a second, and 2 of a third, these constanly go up). To get around cookie/cache issues we do not run more than 1 of a single bot type on a user. Thus all the bot installs are spead across 8 different user profiles making even minor updates a less than straigforward process. All bot input is driven by php controller script feeds however, maybe I can work out something.

What are the chances of getting a feature where our bots auto-update themselves? My thinking is that the bots would be compiled with a location(in which the bot writer would be resposible for maintaining/hosting) to tell the bot what the latest version of that particular script is, and where to download the latest version. If that script is out of date, the bot should download a downloader, run the downloader, and close itself. The downloader would then overwrite the bot's compile exe and launch the new exe.