You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had used the GUI a while back to run some crawls on a few sites and it worked brilliantly. I've tried to fire it up again, but when I run the crawl, the output shows no movement at all, where as if I install and use the command line it starts instantly. I'm happy to use the command-line but would rather use the GUI. Is there any reason for this? I'm using an M4 Mac Mini if that's any help in diagnosing the issue.
The text was updated successfully, but these errors were encountered:
unfortunately I can't think of any reason. So at first it worked fine for you with the GUI and on M4 and after a few days it stopped? You start crawling, but you only see a black screen of the virtual console?
Have you tried uninstalling and reinstalling SiteOne Crawler?
By the way, in the next few days I will be releasing a new version of the CLI and GUI tool, with new features and various fixes.
I recently switched from an older m1 MacBook to an M4 Mac Mini and this issue happened on the first crawl on the M4 Mac Mini. The virtual console just says:
"Hello from SiteOne Crawler! Enter the URL above and let me do my work"
The button has a spinning wheel which would insinuate progress next to the word "stop". Unfortunately, nothing happens, no matter how long I leave it. If I run the commands manually in a terminal however, it runs strait away blazing fast.
And yes, I've also tried uninstalling and reinstalling which didn't work either unfortunately.
I'll wait for the update, remove and start fresh, and see if that resolves my issue.
I had used the GUI a while back to run some crawls on a few sites and it worked brilliantly. I've tried to fire it up again, but when I run the crawl, the output shows no movement at all, where as if I install and use the command line it starts instantly. I'm happy to use the command-line but would rather use the GUI. Is there any reason for this? I'm using an M4 Mac Mini if that's any help in diagnosing the issue.
The text was updated successfully, but these errors were encountered: