Unable to create FB accounts even with anti detect + proxy

Joined
Sep 20, 2025
Messages
13
Reaction score
1
Hi all, would like to ask for some advice regarding my set up for running FB ads:

1. create multilogin with default/basic profile settings
2. nodemaven proxy with these settings: residential, mixed ipv4&6, and specific location settings like usa, nyc, brooklyn and a specific isp with sticky session, keep ip as long as possible, quality default filter mode
4. I use one proxy per multilogin profile and use the same proxy to farm cookies
3. Use multilogin's cookie robot script to cookie farm for 30 mins/day for 2 days - using websites from https://whotracks.me/trackers/facebook.html
4. Let profiles rest for 2 days
5. using the same proxy for each profile, i go to facebook.com and attempt to create a new profile using new gmail accounts verified using paid online SMS services

I either get the unable to complete registration error, or if it does get through after I try again, it asks me for a video verification immediately which I always fail. And the FB profile gets disabled for good. Tried this setup 5 times and they all have failed.

Is there something wrong with my setup? Would appreciate some advice and feedback :)
 
I'm not an account farmer, but I think the process you laid out looks pretty solid. I believe the main issue is with the cookie robot. Also, you should try switching to a different proxy provider or ask them for a private proxy just for you to test. Even though you use one proxy per profile, it's possible the provider has already shared that proxy with others
 
for cookie farming, how long do you think is a good duration? before creating fb acc
 
Hi all, would like to ask for some advice regarding my set up for running FB ads:

1. create multilogin with default/basic profile settings
2. nodemaven proxy with these settings: residential, mixed ipv4&6, and specific location settings like usa, nyc, brooklyn and a specific isp with sticky session, keep ip as long as possible, quality default filter mode
4. I use one proxy per multilogin profile and use the same proxy to farm cookies
3. Use multilogin's cookie robot script to cookie farm for 30 mins/day for 2 days - using websites from https://whotracks.me/trackers/facebook.html
4. Let profiles rest for 2 days
5. using the same proxy for each profile, i go to facebook.com and attempt to create a new profile using new gmail accounts verified using paid online SMS services

I either get the unable to complete registration error, or if it does get through after I try again, it asks me for a video verification immediately which I always fail. And the FB profile gets disabled for good. Tried this setup 5 times and they all have failed.

Is there something wrong with my setup? Would appreciate some advice and feedback :)

If you’re getting blocked even with proxies, check emails/phones and device/browser fingerprints. Often it’s the combo (IP + bad fingerprints) and Facebook will still catch obvious automation.
 
If you’re getting blocked even with proxies, check emails/phones and device/browser fingerprints. Often it’s the combo (IP + bad fingerprints) and Facebook will still catch obvious automation.
but im using new gmail email addresses verified by paid SMS services. for anti detect im using multilogin. they did not ask me for phone during the sign up process
 
but im using new gmail email addresses verified by paid SMS services. for anti detect im using multilogin. they did not ask me for phone during the sign up process

Yeah, but FB’s filters go way beyond just email/phone. They look at browser fingerprints, cookies, time-zones, device consistency, even behavior patterns. If anything feels off or automated, they’ll flag it instantly. That’s why you keep hitting verification walls.
 
Yeah, but FB’s filters go way beyond just email/phone. They look at browser fingerprints, cookies, time-zones, device consistency, even behavior patterns. If anything feels off or automated, they’ll flag it instantly. That’s why you keep hitting verification walls.
As mentioned in the original post I’m also using multilogin with default settings which masks fingerprints and time zone. For cookies I browse websites with fb trackers for 2 days 30min/day and then let profiles rest for two days before I attempt registration.
 
As mentioned in the original post I’m also using multilogin with default settings which masks fingerprints and time zone. For cookies I browse websites with fb trackers for 2 days 30min/day and then let profiles rest for two days before I attempt registration.

I won’t advise on cookie-farming or fingerprint evasion it risks bans and policy violations. For scaling legitimately, set up Meta Business Manager, verify pages/accounts, use real phone/email verification or trusted staff, and use Meta’s developer/test users for safe testing.
 
I’ve seen this issue come up quite a lot. Facebook has definitely tightened account creation and verification — especially when using proxies, SMS services, or multi-login setups.
 
The issue isn’t just the proxy or email/SMS — Facebook also checks browser fingerprint, time zone, device consistency, and behavior patterns; any unusual or automated signal gets flagged instantly.
 
I find your process pretty good, I haven't noticed anything wrong that would cause you to have an error when registering an account. Have you tried contacting Meta support?
 
just an update: unfortunately i have tried every combination and fb still asks for verification.
 
I understand the frustration — you’ve taken all the steps, but Facebook still sees it as a risk. Possible reasons: SMS/Gmail/proxy/cookie farming sources look “unnatural” and trigger video verification; creating multiple profiles on the same infrastructure can also be linked.

Safety tips:
Use real SIMs and clean devices/apps instead of cheap SMS services.
Reduce automation: slow down, warm-up each profile with real behavior.
If the target is legitimate, consider an official solution (Meta partner/agency) or hire a compliance expert.
 
Facebook doesn’t just check email or phone — it scans fingerprints, cookies, time zones, devices, and behavior, so anything suspicious gets flagged quickly. Instead of risky tricks like cookie farming, the safe way to scale is through a verified Business Manager, real pages/accounts, trusted phone or email verification, and using Meta’s developer/test users for testing.
 
From what you described, it seems the issue may be linked to how Facebook is flagging patterns during the account creation process.
 
Honestly I’d look less at the proxy/browser combo and more at the fact that new Facebook accounts are heavily reviewed now. Tools like Gologin, Multilogin, Adspower or proxies can help with legit account management, but they won’t guarantee trust on freshly created profiles, especially when verification signals don’t match normal user behavior.
 
Back
Top