QuickBooks Error 179
Let’s Dive in to see…

How to Fix QuickBooks Error=179

Get ProAdvisor Help Now!
QuickBooks Online

QuickBooks Banking Error Guide

How to Fix QuickBooks Error 179

QuickBooks displays Error 179 when attempting to connect to or update a bank account feed — the bank rejected the login attempt.

Error 179 is a bank-side login rejection. The problem originates at your bank's security system, not QB's software. At QuickFix Bookkeeping, the first step is always logging out of your bank from all other devices and waiting 15-20 minutes before reconnecting through QB.

The QuickFix Bookkeeping Distinction

Error 179 is a bank-side login rejection — not a QuickBooks internal error. The fix is almost always on the bank/session side, not in QB's program files.

Concurrent session (most common)

Logged into the bank on phone, tablet, or another browser while QB is trying to connect. Log out of all devices, wait 15 minutes, then reconnect.

Stale credentials in QB

Bank password changed but not updated in QuickBooks. Update via Banking > Edit icon > Edit Sign-in Info.

Bank website or MFA changed

Bank updated its login page or added multi-factor authentication, breaking QB's automated connection. Disconnect and reconnect fresh.

Wait 15-20 minutes after logout before reconnecting: Bank sessions take time to fully clear server-side. Immediate reconnect after logout often fails because the old session still appears active. This explains why the "fix" works when you try again later but not immediately.

What Causes QuickBooks Error 179?

Bank Password Changed — QB Not Updated

Most common — password changed at the bank but QB still holds the old one. Update credentials via Banking panel > Edit icon > Edit Sign-in Info.

Simultaneous Login from Another Device

You or another user is logged into the same bank account from a phone or browser while QB attempts to connect. Most banks allow only one automated session at a time.

Bank Website or Login Process Changed

Bank updated its website login, added MFA, or changed security protocols. QB's saved connection method no longer matches. A fresh disconnection and reconnection is required.

Bank Account Temporarily Locked

Multiple failed QB login attempts caused the bank to temporarily lock the account for security. Wait 30-60 minutes, verify credentials at the bank's website directly, then retry.

Corrupted Browser Cache (QB Online)

In QBO, a corrupted browser cache loads stale session data. Clearing browser cache and cookies then reloading resolves this variant quickly.

Bank Server Maintenance

The bank's online banking servers are undergoing maintenance or experiencing downtime. QB cannot reach the login endpoint. Wait and retry after a few hours.

How to Fix QuickBooks Error 179

Start with Method 1 — log out of bank on all devices and wait. This resolves the majority of Error 179 cases.

METHOD 1 Log Out of Bank on All Devices — Wait 15-20 Minutes Do this first
1

Log out of your bank account on every device — phone banking app, all browser tabs, tablet. Confirm no one else with account access is currently logged in.

2

Wait 15-20 minutes for the bank's session to fully clear server-side. Reconnecting immediately often fails even after a correct logout.

3

In QB: Banking panel > select the affected account > Edit icon > Edit Sign-in Info. Re-enter current credentials > Update. If the connection restores — concurrent session was the cause.

METHOD 2 Verify Credentials at Bank Website Then Update in QB
1

Open your bank's website in a browser and log in manually. If login fails — reset password at the bank, then update QB. If login succeeds — log out, then update credentials in QB as below.

2

In QB Banking: select the affected account > Edit icon > Edit Sign-in Info > enter the current credentials > Update. Wait for the sync to complete.

METHOD 3 Clear Browser Cache (QBO) or Disconnect and Reconnect Bank
1

QBO: Chrome Settings > Privacy > Clear browsing data > Cached images and files + Cookies > Clear. Log back into QB Online and retry the bank update.

2

If bank website changed: Banking panel > select account > Edit icon > Disconnect. Then Banking > Add account > search for your bank > reconnect fresh. Missing transactions from the gap can be imported via CSV download from your bank's statement page.

METHOD 4 Manual CSV Import — Keep Books Current While Feed is Being Fixed
1

Log into bank website > download transactions as CSV for the relevant period. In QB: Banking > File Upload > select CSV > map columns > import. This keeps reconciliation current while the live feed is restored.

Frequently Asked Questions

Does Error 179 mean my bank account data is at risk?
No. Error 179 is a connection failure — QB could not log into the bank to retrieve transactions. No data was transmitted. Your QB books and bank account are both unaffected. The only consequence is that recent bank transactions have not synced into QB. Import these via CSV manually until the connection is restored.
Why does Error 179 keep recurring every week?
Recurring weekly 179 errors almost always mean someone is logged into the bank account on another device (often a phone with the banking app kept open in the background) at the same time QB's automatic bank feed sync runs. The fix is to either use a dedicated QB-only login at your bank, or ensure the banking app is fully closed before QB's scheduled sync time. Banks with strict single-session policies are the most common scenario for this pattern.

Related QuickBooks Banking Errors

Bank Feed Still Not Connecting After All Methods?

Let QuickFix Bookkeeping Restore Your Bank Connection.

Recurring Error 179 or a bank that changed its login structure often requires a full reconnection and CSV catch-up import. Our advisors restore your bank feed and keep reconciliation accurate throughout.

Book a Free 30-Minute Consultation

No obligation. Same-day response. Bank feed restored fast.