Overview
This guide helps resolve OAuth authentication failures when connecting Google Ads integration, specifically when you encounter redirect errors to 'localhost2.dazoshealth.com' that result in "Safari can't find the server" or similar browser errors.
Symptom/Error
When attempting to activate the Google Ads workflow integration in your CRM settings, you may experience:
OAuth authentication fails during the connection process
Browser redirects to https://localhost2.dazoshealth.com/...
Error message displays: "Safari can't find the server" (or similar in other browsers)
Connection to Google Ads cannot be established
Cause
This error occurs due to an incorrect OAuth callback URL configuration that redirects to a development environment URL instead of the proper production URL. This is a backend authentication configuration issue.
Solution
Step 1: Try Standard Troubleshooting First
Log in to your Google Account settings
Navigate to Security > Third-party apps with account access
Find "Dazos" in the list and select Remove Access or Revoke
Log out of your Dazos CRM completely
Log back in to Dazos
Attempt to connect Google Ads integration again
Step 2: If the localhost2 error persists after Step 1
This indicates a backend authentication configuration issue that requires developer intervention. The standard troubleshooting steps will not resolve localhost2 callback URL errors.
When to Contact Support
Contact Dazos Support immediately if:
You see any "localhost2.dazoshealth.com" URL in the error
The standard troubleshooting steps in Step 1 do not resolve the issue
The error persists across different browsers (Chrome, Safari, etc.)
⚠️ Important: This error requires backend fixes and cannot be resolved through user-side changes alone. Our development team will need to schedule a direct session with you to resolve the authentication configuration.
What to Expect
When you contact support about this issue:
Our team will escalate to the development team
A developer will schedule a meeting with you
During the meeting, they will need access to the Google account with admin permissions
The issue will be resolved through backend authentication configuration changes
Related Resources
For general Google Ads integration setup, see our main Google Ads integration documentation in the Help Center.