first of all I wanted to congratulate you on this project, I really like the idea and the fact that you share it with us is great
Not having a computer at hand at the moment, I chose to host your project on a VPS under debian 12 but I find myself facing some difficulties
Indeed, when I launch the project, i can see in the server-side console that it encounters a 429 error, which does not surprise me because the IP must not be clean. So I removed the comments in the utils.js file so that puppeteer launches with a proxy (I put a static residential proxy from IPRoyal) but I get the following result at launch:
[6:11:59 AM] User is not logged in. Redirecting to the login page...
Declining optional cookies...
[6:12:09 AM] Still got a 429, trying again in 12 hours.
[6:12:11 AM] Received 400 error for `https://www.instagram.com/api/v1/challenge/web/xxxxxxx/ (challenge link)
Then the server crash:
/home/debian/instagram_commenter_ui/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WaitTask.js:50
this.#timeoutError = new Errors_js_1.TimeoutError(`Waiting failed: ${options.timeout}ms exceeded`);
TimeoutError: Waiting for selector 'img[alt*="'s profile picture"]' failed: Waiting failed: 30000ms exceeded
at new WaitTask (/home/debian/instagram_commenter_ui/node_modules/puppeteer-core/lib/cjs/puppeteer/common/WaitTask.js:50:34)
at IsolatedWorld.waitForFunction (/home/debian/instagram_commenter_ui/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Realm.js:25:26)
at CSSQueryHandler.waitFor (/home/debian/instagram_commenter_ui/node_modules/puppeteer-core/lib/cjs/puppeteer/common/QueryHandler.js:172:95)
at async CdpFrame.waitForSelector (/home/debian/instagram_commenter_ui/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Frame.js:522:21)
at async CdpPage.waitForSelector (/home/debian/instagram_commenter_ui/node_modules/puppeteer-core/lib/cjs/puppeteer/api/Page.js:1312:20)
at async login (/home/debian/instagram_commenter_ui/utils.js:366:5)
at async init_browser (/home/debian/instagram_commenter_ui/utils.js:323:3)
at async Socket.<anonymous> (/home/debian/instagram_commenter_ui/utils.js:445:9)
If there is no fix for this problem, could you implement a captcha solving system?
I can’t do it myself because I don't have a PC right now but i would be happy to give you my own Capmonster or Cap.guru key loaded with money if you need one to work on the project.
By the way i saw that even after setup the endpoint /register is still accessible, I assume it's not done on purpose but it could be dangerous if deployed on a server like i did i guess
In any case thank you for this work, I will try to make a pull request with additions and improvements when I have a computer
Hello!
first of all I wanted to congratulate you on this project, I really like the idea and the fact that you share it with us is great
Not having a computer at hand at the moment, I chose to host your project on a VPS under debian 12 but I find myself facing some difficulties
Indeed, when I launch the project, i can see in the server-side console that it encounters a 429 error, which does not surprise me because the IP must not be clean. So I removed the comments in the utils.js file so that puppeteer launches with a proxy (I put a static residential proxy from IPRoyal) but I get the following result at launch:
Then the server crash:
If there is no fix for this problem, could you implement a captcha solving system? I can’t do it myself because I don't have a PC right now but i would be happy to give you my own Capmonster or Cap.guru key loaded with money if you need one to work on the project.
By the way i saw that even after setup the endpoint
/registeris still accessible, I assume it's not done on purpose but it could be dangerous if deployed on a server like i did i guessIn any case thank you for this work, I will try to make a pull request with additions and improvements when I have a computer