Seth Turin

Hey, sorry, Johhny and I had some miscommunication about the location of the log file. The file I need is in your documents folder, like if you hit the documents shortcut on the left side menu in windows explorer. Please see the attached image. Thanks for your patience, and we'll get this fixed ASAP once we find the issue.

Sorry, Johnny is referencing this tool: https://ubotstudio.com/files/ubot_chromedriver_fix.zip To explain: Chrome changed something and made it so that we have to download a new version of chromedriver (which is what runs the chrome automation) for every new version of chrome. The latest version of UBot Studio should automatically do this on startup. But if it's error, there could be a few reasons why. The tool I linked to will try to manually update chromedriver to the correct version. If it fails. it will give us information on why it failed, so that we can fix it in UBot. Like Joh

Hi Chrome made a recent update that broke UBot's connection to Chrome. I'm working on a fix for it that will be released in an upcoming version, but for now, run this script and it will patch the necessary files and get things running again. Download at: https://ubotstudio.com/files/ubot_chromedriver_fix.zip

Alright, everything is back up and running. We're going to continue to monitor the situation and we'll be looking for a more permanent solution to make sure this never happens again

If we can't get it up in the next day or two, I'll be looking into this. It's not super easy, because the server does a lot more than just check licenses, but I understand the urgency, so my priority is just getting something working for you guys. I know this sucks. I'm doing everything I can to get it working again.

Sorry for the long outage. We're basically rebuilding the server from the ground up. Please know we're doing everything we can to get things back up and running ASAP. Thanks for your patience.

I see, well that error is definitely on our end (or rather, amazon's end). I've resolved it and it should be working now.

This isn't actually a server issue, and I'm not sure how to reproduce the error on my end, but I can provide some information that might help determine the cause of the error. UBot Studio controls the external browser using selenium. Selenium uses a locally hosted http server to communicate with the controlled chrome window. For some reason or another, selenium is timing out when it tries to communicate with chrome via its locally hosted http server. One thing you can try is turning off all your plugins, and seeing if the error goes away. If it does, you can try to narrow it do

Hi If there are errors occurring when you run UBot Studio without plugins, it's our top priority to get on top of it and get it working again. We don't have access to the source code of the plugins and we can't debug them. It's possible that plugins will contain errors, and this is what it sounds like is happening in your case. When this happens, the best thing to do is contact the developer of the plugin. We want to help, but we didn't create the plugins, so there's no way for us to fix the errors that they raise.

Hi Can you tell us how to reproduce the behavior you're seeing without installing the Automax plugin?

Hi These features are part of the new Enterprise subscription. If you'd like a discount, PM me and I'll get you set up.

Sorry to hear that! Please open a ticket with support.ubotstudio.com and they'll help get it working for you.

Can you tell me what page this is on?

In the next version, you'll be able to navigate from the on load command