-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser Automation Detected on Linux Machines #13
Comments
I have a Linux machine where Kasada appears to function smoothly. Transferring certain const context = await browser.newContext({
userAgent: 'Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0'
});
await context.addInitScript(() => {
Object.entries({
appCodeName: 'Mozilla',
appName: 'Netscape',
appVersion: '5.0 (X11)',
buildID: '20181001000000',
doNotTrack: "1",
oscpu: 'Linux x86_64',
platform: 'Linux x86_64',
product: 'Gecko',
productSub: '20100101'
}).map(([key, value]) => Object.defineProperty(navigator, key, {
get: () => value
}));
}); Removing the This is not a foolproof solution. |
Hi, is there a Docker image that will work stably on Linux? |
No, not exactly. 😅 |
Just FYI these values are working for me inside docker with TTV, despite the image being based on Ubuntu:
|
hi, I requested the api through the headers I got and got a 500 error response, is this because of linux? |
It's not entirely clear whether Linux plays a major role in causing the 500 error response. Could you specify which service you're using kpsdk-solver against? |
I try to against vercel on debian12, code:
|
I've been notified about a persistent problem affecting several users, and I'd like to address it myself since there haven't been any related issues submitted to this repository. Correct me if I'm mistaken, but it appears that kpsdk-solver is easily being detected for browser automation on Linux-based systems.
At the moment, the easiest workaround is to run the solver on a Windows-based machine. However, despite this, I still plan on putting efforts into patching this issue in an attempt to maintain some cross-platform functionality.
The text was updated successfully, but these errors were encountered: