TABLE OF CONTENTS

✅ Step-by-Step Fix

1. Create and Assign the Subnet Group

2.  Flush Reset IP

3. Launcher Login & Chrome Config Push

4. Open All Profiles

6. Log In to Ticketmaster on Each Profile

• Why This Works
• Common Mistakes to Avoid

If a customer reports issues like:

• Getting stuck in a Browser Activity Paused Error

• Being randomly kicked from the queue

• Unable to log in to Ticketmaster errors

⚠️ These problems are often caused by out-of-sync local cache or missing reset steps during subnet setup.

✅ Step-by-Step Fix

1. Create and Assign the Subnet Group

• Follow the Process Street Workflow to create and assign the subnet group to the customer.

• Search for the customer's account in the Admin Panel. 

2.  Flush Reset IP

• From the Admin view, Flush / Reset IP for that customer by clicking "Reset All Proxies".

3. Launcher Login & Chrome Config Push

• Ask the customer to log in via the PrivateTabs Launcher app.

• Reset the Chrome Engine Confi.

    •  Click "Reset App."

• Click "Delete App Data."

• Once you see the blue "App Data Clear Successfully" text, you can now advise the customer to click the "Go Back" button to sign in to their account.

4. Open All Profiles

• Open each profile in their system one by one to sync IPs.

• Load each profile in the customer’s system one by one.

  • On each profile:

    • Click the PT Extension (green icon).

• Click the left pink button that says "Clear This Tabs Cookies".

•  ⚠️ Make sure to UNCHECK the rotate Profile Proxy checkbox then click “Clear Browsing Data”.

6. Log In to Ticketmaster on Each Profile

• Once steps above are completed, log in to TM from each profile.

Why This Works

When subnet groups are changed or reassigned, browser-level data may still retain cached elements from old configurations. This can lead to:

• Misaligned IP assignments

• Session mismatches

• Failed Ticketmaster authentication

By clearing all settings without rotating the IP, we ensure the session stays aligned with the newly assigned subnet.

Common Mistakes to Avoid

❌ Skipping profile sync step (Step 4)

❌ Rotating IP during reset (this breaks session sync)

❌ Only resetting data via launcher without loading actual profiles