Bablosoft

@DezeJK i think fingerprint had issue last night as just getting normal print cause me issues aswell but better now

@Fox "Pretty sure a filter that checks the authenticity of the user is applied before obtaining the fingerprint (if some mod can confirm)."

Maybe you can give us some information about the filtering and selection that is applied to fingerprints from the FPS-API? Thank you.

@Fox I asked in the Russian-speaking segment. And dubbed it into the English-speaking segment. Or is it forbidden?

Well, at the moment I have not received a response that would close the topic

Not entirely sure if I understood you correctly, but I think there's a misconception on your part. The color and number on the left simply indicates how likely it is that the specific method is used for fingerprinting. If you hover over the colored field, the tooltip will tell you this.

@FastSpace thanks for the information I will definitely take a look at the proxies pretty sure these sites will come in handy when picking the next proxies

@robertbaldwin Strange behaviour. Maybe the developers of the fingerprint.js changed something in their code. In general it should work. You can try a different version from their github or the npm module.
Maybe their is some relevant information in the documentation. It's a while ago I used it.

@Mario-Rossi said in How to run it on docker?:

Unfortunatly it not the same as puppeteer, in order to preserve the current codebase i should stick to node + puppeteer. Im switching to azure actually wich supports windows containers.

You can work with Selenium via CDP, similar to how Puppeteer works.
https://www.selenium.dev/documentation/webdriver/bidirectional/chrome_devtools/

Start browser with Selenium -> Get CDP connection -> Working with Puppeteer via CDP connection

Best is to ask support for the error.

Where exactly are you getting the 503? Are you making a post request?

Hello we found a way to fix this issue by adding error handling code

file: node_modules\browser-with-fingerprints\src\plugin\index.js

`
async #run(spawn, options = {}) {
const { proxy, fingerprint } = this.setProxyFromArguments(options.args);

const { id, pid, pwd, path, bounds } = await setup(proxy, fingerprint);

await cleaner.run(path).ignore(pid, id);

mutex.create(BASProcess${pid});

const browser = await (spawn ? launcher : options.launcher ?? this.launcher).launch({
...options,
headless: false,
defaultViewport: null,
executablePath: ${path}/worker.exe,
args: [--parent-process-id=${pid}, --unique-process-id=${id}, ...defaultArgs(options)],
});

try{
await (spawn ? configure : this.configure.bind(this))(
(target) => target === browser && cleaner.include(pid, id),
browser,
bounds,
synchronize.bind(null, id, pwd, bounds)
);
} catch (error){
await browser.close();
throw new Error(BASProcess${pid} ${error});
}

return browser;
}
`
this will stop the error from leaving the browser open

Thank you for this wonderful project