How to Fix Google Ads “You Need to Create aPasskey” Error on VPS / RDP
If you run Google Ads inside a Remote Desktop (RDP) VPS, you may suddenly encounter a popup saying: ‘You need to create a passkey to perform this action'...
If you run Google Ads inside a Remote Desktop (RDP) VPS, you may suddenly encounter a popup saying: ‘You need to create a passkey to perform this action’ when creating campaigns, adding
billing, or changing ad groups.
When you click Create a Passkey, Chrome opens a Windows Hello dialog asking to ‘Insert your security key and touch it’. Because a remote VPS server has no physical USB Yubi Key or fingerprint scanner attached, users get stuck in an infinite security key loop.
The Problem: Why Google Ads Loops on Remote Desktop
- Google Ads blocks your action with a security requirement popup

- Clicking ‘Create a Passkey’ on the VPS triggers the stuck Windows Security key prompt because there is no physical USB key inserted in the cloud server:

Step-by-Step Solution: Create & Approve Passkey on Mobile Phone
Follow these clear steps on your personal mobile phone to create and register your passkey without needing hardware keys on your VPS:
Step 1: Open Google Account Security on Your Mobile Phone
Do NOT create the passkey through the Google Ads popup. Instead, open a web browser on your mobile phone and navigate directly to:
Direct Link: myaccount.google.com/sign in options/passkeys, On the page, tap the button: ‘+ Create a passkey’.

Step 2: Tap ‘Create a passkey’ on the Mobile Popup
When the dialog appears stating ‘Create a passkey for your Google Account – Create a passkey to start signing in with just your fingerprint, face, or screen lock’, tap the blue ‘Create a passkey’
button.

Step 3: Tap ‘Continue’ and Verify Phone Biometrics
On the Android system sheet, tap the cyan ‘Continue’ button. Scan your phone’s Fingerprint, Face ID, or enter your Screen Lock PIN. Your passkey is now created.

Step 4: Tap ‘Approve’ to Authorize the New Passkey
Under Google Password Manager, find the newly created passkey and tap the blue ‘Approve’ button. This authorizes your passkey and initiates the security synchronization.

Step 5: Observe the 24 to 48-Hour Pairing Cooldown
As explicitly noted in the Google Ads popup: ‘New passkeys take 1 to 2 days to pair with Ads. Try attempting this action again after this period.
Google Ads enforces a mandatory 24 to 48-hour security waiting period after a new passkey is registered. Simply wait 1 to 2 days for Google’s servers to sync your passkey, then log back into
Google Ads on your VPS to complete your campaign edits!
Step 6: Observe the 24 to 48-Hour Pairing Cooldown
As explicitly noted in the Google Ads popup: ‘New passkeys take 1 to 2 days to pair with Ads. Try attempting this action again after this period. ‘Google Ads enforces a mandatory 24 to 48-hour security waiting period after a new passkey is registered. Simply wait 1 to 2 days for Google’s servers to sync your passkey, then log back into
Google Ads on your VPS to complete your campaign edits!
Frequently Asked Questions (FAQ)
Google updated its security policy for Google Ads to protect accounts against hijacking. Sensitive actions (like budget changes or adding billing) require biometric or passkey verification.
Standard RDP does not redirect USB security key hardware automatically. Creating the passkey on your mobile phone via Google Account is the easiest workaround.
Google Ads takes up to 48 hours to recognize new passkeys across its ad infrastructure. You must wait 1 to 2 days after creation before Google Ads unlocks sensitive campaign edits.
Keep Reading
More from the blog
Guides, tutorials, and insights on RDP hosting and cloud infrastructure.



