Skip to main content

Reconnecting your account (and changing your Upwork password)

Why a connection drops and how to reconnect — including after changing your Upwork password.

Written by Ivan Nedelkovski

When you'll need to reconnect

Lancer stays signed in to your Upwork account in the background. A few things end that session and require a reconnect:

  • You changed your Upwork password (the most common cause).

  • You changed your 2FA method, or switched on SMS 2FA or "Sign in with Google".

  • Upwork logged the session out for a security check.

If Upwork rejects the saved password during Lancer's daily proposal sync, Lancer stops retrying the login, marks the account as failed to connect and shows a reconnect message ("Upwork rejected the saved password. Reconnect the account with its current password."). The account is skipped by the sync until you reconnect it.

You will also see an amber banner at the top of every Lancer page: "Lancer can’t sign in to <account>. Upwork says the saved password or security answer is wrong." Click Reconnect it with the current details to open that account. The banner shows once per affected account, you can dismiss it (it only hides in that browser, and comes back if Upwork refuses again), and it goes away once you reconnect the account.


How to reconnect

  1. Open Connected Accounts.

  2. Open the menu on the account's row and choose to update / reconnect it.

  3. Enter your current Upwork password (and your Authenticator setup key if you use one). You can leave a field empty to keep its current value.

  4. Submit — the account re-syncs in a few minutes and your campaigns can resume.

Don't use Connect for this. If you add the same Upwork email again with Connect, Lancer refuses it ("This Upwork account is already in your Connected accounts") — use Reconnect on the existing account.


Tip

If you change your Upwork password, reconnect in Lancer right after so your campaigns don't sit paused. And don't disconnect the account to fix a login issue — disconnecting deletes its data. Update/reconnect instead, or message us.

Did this answer your question?