Jump to content
UBot Underground

stever

Fellow UBotter
  • Content Count

    115
  • Joined

  • Last visited

  • Days Won

    4

stever last won the day on February 9 2023

stever had the most liked content!

Community Reputation

10 Good

About stever

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

System Specs

  • OS
    Windows 10
  • Total Memory
    4Gb
  • Framework
    unsure
  • License
    Standard Edition

Recent Profile Visitors

2630 profile views
  1. I suspect it's because (a) there are other fires burning, or (b) they don't know how to - maybe they can't replicate it, so go to (a). Super frustrating especially since the inbuilt browser is now so old it gets bounced on so many sites - the whole package is mainly unusable.
  2. @Seth Turin Hi Seth - as you can see from this thread, this is a growing problem. I'm sure we're all willing to help you troubleshoot the issue, but at the moment, for us, and maybe others, Ubot is unusable. I've had the problem for nearly three weeks and it's affecting my business (I use Ubot to create products on Fiverr) - having to suspend my gigs. Hope you can sort it out.
  3. Also getting this error after the Uh-oh splash screen error pointing to the WeServer: Obvs, I don't have internet connection issues. The uh-oh screen appears most times after starting Ubot, but sometimes it starts as normal and then exhibits the behavior described by @UPPER Not easily repeatable but I noticed yesterday that when you load a script to just navigate to different URLs, while the script stops after the first navigate element, it seems you can still run individual elements manually and they operate as expected. Also - another point that may be relevant:
  4. That seems to work - great stuff - thanks
  5. Thanks mate - have done - great work - thank you!
  6. Same here - I get similar error messages. The splash screen error doesn't happen every time, but the navigate error occurs from the start for me: I think the Chrome browser update may have something to do with it. Only happens when the Chrome browser is enabled - not the internal browser.
  7. Thanks - that's great - any chance you could tweak it for 6.7.23 - or explain how that can be done? 6.7.23 is such a useful version of Ubot when it works - but not doing at the moment for at least two of us.
  8. Thanks Seth - I am doing clean installs - things have deteriorated now so I can't download the support files to even start Ubot (this is new behavior - it was installing fine until yesterday. Now nothing is working : 2023-10-26 20:34:42: UBot Studio Starting Up 2023-10-26 20:34:42: Start Core UI... 2023-10-26 20:34:43: Loading Main Window... 2023-10-26 20:34:43: Download Core Files... 2023-10-26 20:34:43: Downloading base files 2023-10-26 20:34:44: Error downloading file C:\Users\Steve\AppData\Roaming\UBot Studio\Browser\6.7.23\6.7.23.zip: System.Net.WebException: The remote ser
  9. Me too - looks like another central server issue - don't understand why they can't fix this...
  10. That fixed nothing - still getting the same error message
  11. Am trying a complete reinstallation (being careful not to lose plugins) - let's see if this works
  12. "The HTTP request to the remote WebDriver server for URL http://localhost blah blah timed out after 60 seconds" The external Chrome browser is unusable with this error so everything has stopped. Any suggestions? (This is Ubot 6.7.23 standard version)
  13. Indeed - that's what I was told as well. Sometimes Seth gets involved and things happen. Other times very basic bugs and errors continue for months and months. The best thing they did recently was introduce the Chrome browser, but inow Ubot is such a fragile piece of software - easily crashes when scraping attributes for example - I only use it when I can't find a way of using Python.
  14. I'm using the standard edition, Chrome browser and get this error when compiling:
×
×
  • Create New...