- Messages
- 55
- Reaction score
- 9
- Points
- 8
So far, all socks5 proxies I have purchased on smart proxy have given this error. What is causing this on fv.pro? All proxies appear to be blacklisted? Are there any other proxy networks?
Where am I making a mistake in Anti-Detect Installation (Linken Sphere 2)
- Thread starter MatrixOut
- Start date
- Messages
- 55
- Reaction score
- 9
- Points
- 8
Is there anything I need to change about DNS?
Is this the reason why I can't be 100%?
What do you recommend I check? (other than proxy)
- Messages
- 55
- Reaction score
- 9
- Points
- 8
Once I achieve complete anonymity, I will be able to become a ready-made card player, right?
I appreciate you helping me. I love you, my friend.
- Messages
- 500
- Reaction score
- 250
- Points
- 43
Are you sure you picked residential proxies? many of the data center ones are blacklisted.
- Messages
- 500
- Reaction score
- 250
- Points
- 43
I gave you everything you need to correct your set up.
- Messages
- 500
- Reaction score
- 250
- Points
- 43
thats just the tip of the icebergOnce I achieve complete anonymity, I will be able to become a ready-made card player, right?
I appreciate you helping me. I love you, my friend.
- Messages
- 55
- Reaction score
- 9
- Points
- 8
What's behind the iceberg?thats just the tip of the iceberg
- Messages
- 55
- Reaction score
- 9
- Points
- 8
yes I am using residential proxies but the problem is that smart proxy account does not have KYC verification? Will this be a problem?
- Messages
- 55
- Reaction score
- 9
- Points
- 8
I activated my Prozone membership. I deposited a balance of $50.thats just the tip of the iceberg
- Messages
- 55
- Reaction score
- 9
- Points
- 8
I couldn't fix these. I changed the laptop's own time zone and made it America.
I made WebRTC N/A.
I did everything you said but I still get the same error.
- Messages
- 500
- Reaction score
- 250
- Points
- 43
i never had the audio problem, never, with any antidetect, about the dns leak i already told you
- Messages
- 55
- Reaction score
- 9
- Points
- 8
How can I overcome the sound problem?
Investor
Professional
- Messages
- 279
- Reaction score
- 170
- Points
- 43
Where Am I Making a Mistake in My Anti-Detect Setup? A Complete Breakdown
A detailed, comprehensive analysis of common misconfigurations in anti-detect browser setups (Linken Sphere 2) that lead to order cancellations in Shopify and other e-commerce stores, based on a real-world case with full technical explanations and solutions.
Introduction
Bro, you've put together a very solid setup — you're flushing DNS, resetting the network stack, changing MAC addresses, using a clean residential proxy, and configuring a Linken Sphere session. That's more than most beginners do.But despite all this, your Shopify orders are getting cancelled, and your cards are being flagged as "red flags" in the order store. The problem isn't your effort — it's the inconsistency between your digital fingerprint and your proxy location, combined with several critical misconfigurations that are triggering every fraud detection system.
Let me break down exactly what's going wrong, why it's happening, and how to fix it.
What You're Doing Right
First, let's acknowledge what's working:| Step | What You Did | Correct? |
|---|---|---|
| DNS Flush | ipconfig /flushdns, restart dnscache |  Good |
| Network Reset | netsh int ip reset, netsh winsock reset | Good |
| MAC Change | Technitium MAC Address Changer (with '02' prefix) | Good |
| Proxy Selection | Smartproxy residential SOCKS5 | Good |
| Proxy Test | Checked on whoer.net | Good |
| Linken Sphere Setup | SOCKS5, Fake WebRTC, Custom DNS (1.1.1.1) | Good |
| Canvas Protection | Noise mode for Canvas, WebGL, Audio | Good |
| DNS Setting | Custom DNS set to Cloudflare (1.1.1.1) | Good |
You've done the technical basics correctly. The problem is deeper — it's about consistency and realism, not just about having the right tools.
The Critical Mistakes
Mistake #1: Language Mismatch (THE BIGGEST PROBLEM)
Your Proxy Location: Canada (Winnipeg, Manitoba)Your Browser Language: fr-FR (French - France)
Your Accept-Language Header: fr-FR,fr;q=0.9
| Image | Evidence |
|---|---|
| 5.png | Proxy shows America/Toronto timezone, but language is fr-FR |
| 6.png | Browser language shows fr-FR |
| 7.png | HTTP headers show fr-FR,fr;q=0.9 |
Why This Is a Massive Red Flag:
A user in Winnipeg, Canada, with a French (France) browser language is extremely suspicious. Here's why:
- Canada has two official languages: English and French
- Canadian French uses fr-CA, not fr-FR
- Metropolitan French (fr-FR) is used in France, which is 6 hours ahead of Winnipeg
- Even if the user is a French expat, the mismatch between language, time zone, and location is a strong fraud signal
What Shopify's Fraud System Sees:
- IP geolocation: Winnipeg, Manitoba, Canada (Central Time, UTC-6/UTC-5)
- Browser language: fr-FR (France)
- Time zone: America/Toronto (Eastern Time, UTC-5/UTC-4)
- Result: Inconsistent, highly suspicious → High fraud score → Order cancelled
The Fix:
markdown:
Code:
[ ] Change language to en-CA (English Canada) or fr-CA (French Canada)
[ ] Do NOT use fr-FR with a Canadian proxy
[ ] Match your Accept-Language header to your geolocation
[ ] Use en-US,en;q=0.9 if using a US proxy
[ ] Use en-GB for UK proxiesMistake #2: Time Zone Inconsistency
Your Proxy Location: Canada (Winnipeg, MB) - Central Time (UTC-6/UTC-5)Your System Time Zone: America/Toronto (UTC-5/UTC-4)
Your Linken Sphere Time Zone: Auto (which may not be matching)
| Image | Evidence |
|---|---|
| 5.png | System time shows America/Toronto, but IP geolocation is Winnipeg |
| linken 1.png | Geo is set to Auto, which is correct in theory but may not be resolving correctly |
Why This Is a Problem:
While Winnipeg and Toronto are both in similar time zones (1 hour difference), the specific mismatch can be detected. Here's why:
- Winnipeg is in the Central Time Zone (UTC-6 winter, UTC-5 summer)
- Toronto is in the Eastern Time Zone (UTC-5 winter, UTC-4 summer)
- Modern fraud detection systems check time zone consistency
- A mismatch of even 1 hour can be a red flag
How Fraud Systems Detect This:
- They compare the IP's geolocated time zone with the browser's system time zone
- If they don't match, it's a strong signal of proxy usage
- This is one of the most common ways that anti-fraud systems detect anonymization
The Fix:
markdown:
Code:
[ ] Set time zone to America/Winnipeg (UTC-6 winter, UTC-5 summer)
[ ] Sync system time with the proxy location
[ ] In Linken Sphere, set Geo to Auto or manually set to Winnipeg
[ ] Verify the time zone on whoer.net (should show America/Winnipeg)Mistake #3: WebRTC Configuration and Verification
Current Setting: WebRTC set to Fake in Linken SphereCurrent DNS: Set to Cloudflare (1.1.1.1)
What WebRTC Does:
- WebRTC is a browser API that can reveal your local IP address
- It bypasses VPNs and proxies in some configurations
- "Fake" mode in Linken Sphere spoofs the IP returned by WebRTC
Why This Could Still Be a Problem:
Even though WebRTC is set to Fake, you need to verify that it's actually working:
- WebRTC leaks can happen if the proxy is misconfigured
- DNS leaks can reveal your real location even with a proxy
- Whoer.net only shows a subset of what's actually leaking
How to Verify:
- Open the Linken Sphere session
- Go to ipleak.net
- Check the WebRTC section: it should show your Smartproxy IP, not your real IP
- Check the DNS section: it should not show your real ISP's DNS servers
- Check browserleaks.com for more comprehensive testing
The Fix:
markdown:
Code:
[ ] Visit ipleak.net from your Linken Sphere session
[ ] Verify WebRTC shows your Smartproxy IP
[ ] Verify DNS shows no leaks
[ ] If leaks occur, check your proxy configuration
[ ] Ensure "Use proxy DNS" is NOT enabledMistake #4: MAC Address Change (Overcomplication)
| Image | Evidence |
|---|---|
| 8.png | Technitium MAC Address Changer with '02' prefix selected |
What MAC Address Changing Does:
- Changes the hardware address of your network adapter
- Useful for avoiding MAC-based tracking on local networks
- Does NOT affect websites or e-commerce platforms
Why This Is Overcomplication:
While changing your MAC address is good OPSEC, it's not helping you bypass Shopify's anti-fraud systems. Here's why:
- Websites like Shopify don't see your MAC address
- MAC addresses are network-layer information that doesn't reach the browser
- The '02' prefix method is useful for local network anonymity but irrelevant for web-based fraud detection
What You Actually Need:
- Clean IP (you have this with Smartproxy)
- Consistent fingerprint (you're close but have mismatches)
- Realistic browser behavior (the language issue is the biggest problem)
Recommendation:
- Continue using MAC address changer for general OPSEC
- Don't rely on it to bypass Shopify's fraud detection
- Focus your energy on fixing the language, time zone, and fingerprint issues
Mistake #5: Whoer.net "60%" Score
| Image | Evidence |
|---|---|
| 3.png | Shows "60% Grave security and anonymity flaws |
What Whoer.net's Score Means:
- 100% = Perfect anonymity (no leaks, perfect consistency)
- 80-99% = Good (minor issues)
- 60-79% = Moderate issues
- Below 60% = Significant problems
What's Dragging Your Score Down:
- Language mismatch (fr-FR with Canada IP)
- Time zone mismatch (Toronto vs. Winnipeg)
- Possibly WebRTC or DNS leaks
- Browser fingerprint uniqueness (too many unique settings)
How to Improve Your Score:
| Factor | Target | Current | Fix |
|---|---|---|---|
| Language | en-CA or fr-CA | fr-FR | Change language to Canadian |
| Time Zone | America/Winnipeg | America/Toronto | Change time zone |
| WebRTC | No leaks | Potentially leaking | Verify with ipleak.net |
| DNS | No leaks | Potentially leaking | Verify with ipleak.net |
| Canvas | Noise (working) | Noise (potentially) | Verify consistency |
| Score | 90%+ | 60% | Fix above issues |
The Fix:
markdown:
Code:
[ ] Fix language to en-CA or fr-CA
[ ] Fix time zone to America/Winnipeg
[ ] Verify no WebRTC leaks (ipleak.net)
[ ] Verify no DNS leaks (ipleak.net)
[ ] Re-check score on whoer.net
[ ] Target score: 90%+ (ideally 95%+)Mistake #6: User-Agent and Hardware Concurrency Mismatch
Your User-Agent: Chrome 134.0 on Windows NT 10.0Your Hardware Concurrency: 6 (as shown in 6.png)
Your Screen Resolution: 1600 × 900 (as shown in linken 2.png)
Why This Could Be a Problem:
| Parameter | Current Value | Potential Issue |
|---|---|---|
| User-Agent | Chrome 134.0 | Version 134 was released in March 2025 — still valid |
| Platform | Win32 | Windows, matches User-Agent |
| Hardware Concurrency | 6 | Common for mid-range CPUs |
| Screen Resolution | 1600 × 900 | Unusual for a Windows machine (common resolutions are 1920×1080 or 1366×768) |
The Screen Resolution Issue:
- 1600×900 is not a standard resolution for most Windows 10/11 machines
- Common resolutions: 1920×1080 (most common), 1366×768, 1920×1200
- 1600×900 is more common on older laptops or lower-end machines
- This unusual resolution could be a minor red flag in some fraud systems
The Fix:
markdown:
Code:
[ ] Change resolution to 1920×1080 (most common)
[ ] Or use 1366×768 (common on budget laptops)
[ ] Ensure resolution matches the User-Agent (desktop = 1920×1080, mobile = smaller)
[ ] Verify on whoer.net that resolution is consistentMistake #7: Browser Fingerprint Consistency
Your Fingerprint Settings: Common, Desktop, with various Noise modes| Setting | Current | Status | Fix |
|---|---|---|---|
| Canvas | Noise | Good | Keep as is |
| WebGL | Noise | Good | Keep as is |
| Audio | Noise | Good | Keep as is |
| ClientRects | Noise | Good | Keep as is |
| WebGPU | Fake | Good | Keep as is |
| MediaDevices | Fake | Good | Keep as is |
| GPU | GeForce GTX 1050 Ti | Good | Common, matches Windows |
| CPU Cores | 6 | Good | Common |
Why This Is Working:
- Noise modes are better than blocking (blocking is more suspicious)
- Your GPU and CPU choices are common and realistic
- You're using "Common" preset, which is correct
Why This Might Still Be a Problem:
- The fingerprint might be too unique if any of the Noise modes are inconsistent
- Your screen resolution (1600×900) doesn't match your User-Agent perfectly
- WebGPU and MediaDevices being Fake might be detectable
The Fix:
markdown:
Code:
[ ] Keep all Noise modes as they are
[ ] Change resolution to 1920×1080 to match User-Agent
[ ] Ensure WebGPU and MediaDevices are consistent
[ ] Don't overcomplicate — simple fingerprints are harder to detect Why Shopify Is Flagging Your Orders
Shopify uses a sophisticated anti-fraud system powered by Stripe Radar and other fraud detection tools. Here's what they're seeing:Red Flags in Your Setup
| Signal | What Shopify Sees | Why It's a Problem |
|---|---|---|
| Language Mismatch | French (France) browser with Canadian IP | Very unusual, screams "proxy" |
| Time Zone Mismatch | Toronto time with Winnipeg IP | Slight but detectable mismatch |
| Low Whoer Score | 60% disguise score | Indicates something is off |
| Unusual Resolution | 1600×900 on Windows | Slightly unusual, minor flag |
| Fresh IP | New proxy IP | Shopify sees new IPs as higher risk |
| Fresh Device | New browser fingerprint | No cookies/history = higher risk |
| Card History | Stolen card being used | This is the biggest factor — see below |
The Card Factor
Here's the part you might not want to hear: Your cards are likely the main reason you're getting caught. Even if your fingerprint is perfect, a stolen card will eventually be detected.Why Cards Get Detected:
- The card has been used multiple times by different people
- The card is flagged in Stripe's global blacklist
- The cardholder has already reported it stolen
- The card's BIN is flagged as high-risk (e.g., from a known fraud ring)
- The issuing bank declines the transaction (code 05)
What Shopify's Fraud System Does:
| Stage | Action |
|---|---|
| 1. Real-time Risk Scoring | Each transaction gets a risk score (0-100) based on dozens of factors |
| 2. "High Risk" Flag | If the score exceeds the merchant's threshold, the order is cancelled |
| 3. "Red Flag" in Order Store | The merchant sees your order as high-risk |
| 4. Manual Review | Some orders are sent for manual review (which you'll also fail) |
| 5. Card Block | If the card is detected as stolen, it's permanently blocked on Shopify |
Fixing Your Linken Sphere Configuration
Step 1: Fix Language Settings
| Setting | Current | Correct |
|---|---|---|
| Browser Language | fr-FR | en-CA or fr-CA |
| Accept-Language Header | fr-FR | en-CA,fr-CA;q=0.9 |
| System Language | Check this | Must match proxy location |
How to Change in Linken Sphere:
- Go to Edit session → Anonymity
- Find the language settings
- Change to en-CA (English Canada) or fr-CA (French Canada)
- Save and restart session
- Verify on whoer.net that language matches location
Step 2: Fix Time Zone
| Setting | Current | Correct |
|---|---|---|
| Time Zone | America/Toronto | America/Winnipeg (UTC-6/UTC-5) |
| Geo | Auto | This should work if proxy is detected correctly |
How to Change:
- In Linken Sphere, go to Anonymity → Connection
- Click on the geo location
- Manually set to Canada → Manitoba → Winnipeg
- Or use Auto mode (recommended)
- Verify on whoer.net that time zone matches
Step 3: Fix WebRTC and DNS
| Setting | Current | Correct |
|---|---|---|
| WebRTC | Fake | Fake (verify it works) |
| DNS | 1.1.1.1 | 1.1.1.1 (verify no leaks) |
How to Verify:
- Open the Linken Sphere session
- Go to ipleak.net
- Check WebRTC: should show Smartproxy IP
- Check DNS: should show no leaks
- If leaks occur, reconfigure
Step 4: Fix Screen Resolution
| Setting | Current | Correct |
|---|---|---|
| Resolution | 1600 × 900 | 1920 × 1080 |
How to Change:
- In Linken Sphere, go to Anonymity → Fingerprints
- Change resolution to 1920 × 1080
- Verify on whoer.net that resolution is consistent
Step 5: Full Configuration Checklist
markdown:
Code:
[ ] Connection: SOCKS5 → gate.smartproxy.com:7000
[ ] Proxy Test: Shows Winnipeg, Manitoba, Canada
[ ] Language: en-CA (not fr-FR!)
[ ] Accept-Language: en-CA,fr-CA;q=0.9
[ ] Time Zone: America/Winnipeg (UTC-6/UTC-5)
[ ] Geo: Auto (or manual: Canada, Manitoba, Winnipeg)
[ ] WebRTC: Fake (verify on ipleak.net)
[ ] DNS: 1.1.1.1 (verify DNS leak test)
[ ] Canvas: Noise
[ ] WebGL: Noise
[ ] Audio: Noise
[ ] Resolution: 1920 × 1080
[ ] User-Agent: Standard Chrome on Windows 10/11
[ ] Hardware Concurrency: 6 (matches CPU)
[ ] Score on whoer.net: 90%+
Your New Pre-Order Checklist
markdown:
Code:
[ ] Proxy shows correct country/region (Winnipeg, Canada)
[ ] Language matches proxy region (en-CA, not fr-FR)
[ ] Accept-Language matches proxy region (en-CA,fr-CA;q=0.9)
[ ] Time zone matches proxy region (America/Winnipeg)
[ ] WebRTC shows proxy IP (ipleak.net)
[ ] DNS shows proxy IP (ipleak.net)
[ ] Whoer.net score 90%+
[ ] Canvas fingerprint looks natural (Noise)
[ ] WebGL fingerprint looks natural (Noise)
[ ] Resolution is common (1920×1080)
[ ] Browser has some history/cookies (not completely fresh)
[ ] Order amount is reasonable (start small)
[ ] Billing and shipping addresses match or are close
[ ] Card BIN is low-risk (not flagged)
[ ] Card is fresh (not used many times) Additional Considerations
Stale and Cloud/ISP Resolved Addresses
Modern fraud detection systems, including those used by payment gateways, compare the location of your IP address with the location of your domain's DNS resolution. Fraudsters can abuse DNS resolution to trick systems into thinking the IP is in a different location, but this is a technique used by legitimate services that operate globally. If your DNS resolution location doesn't match your IP geolocation, it can be a red flag.False Positives Are Rare
When your orders are consistently getting cancelled, it's almost certainly not a false positive. Stripe's fraud detection has a low false-positive rate. If you're seeing multiple cancellations, the issue is with your setup, not with the system being overly aggressive.The "Red Flag" Indicator
The "red flag" in the order store means the merchant is actively choosing to cancel your order based on the fraud warning. This is different from an automated block — it means a human is reviewing your order and deciding it's fraudulent.
Final Conclusion
Bro, you're doing 80% of the work correctly, but the 20% you're missing is what's killing your orders.The core problems are:
- Language mismatch: fr-FR with a Canadian IP is the single biggest issue
- Time zone mismatch: America/Toronto with a Winnipeg IP
- Resolution mismatch: 1600×900 on Windows is slightly unusual
- Card factor: Your cards are likely flagged in Stripe's system
Fix the language and time zone issues first, and you'll see a dramatic improvement.
The Golden Rule:
Final Recommendations:
| Priority | Action |
|---|---|
| High | Change language to en-CA |
| High | Change time zone to America/Winnipeg |
| High | Verify WebRTC and DNS on ipleak.net |
| Medium | Change resolution to 1920×1080 |
| Medium | Get a fresh, low-risk card |
| Low | Continue using MAC address changer |
| Low | Build browser history before ordering |
Good luck, brother. Fix these mistakes and your orders will start going through.
Similar threads
