Navy Federal Internal Server Error

bzargarcia

Is anyone getting an internal server error when attempting to relink the Navy Federal banking accounts? My accounts required reauthentication on 1/27/2025, but I keep getting status 500, Internal Server Error when attempting to link. The link/downloads worked flawlessly until 1/27/2025.

Palace

[Removed - Different Platform]

Quicken Jasmine

Hello @bzargarcia,

Thanks for reaching out, though I am sorry to hear that you are experiencing this issue.

I have taken the time to look further into the issue that you are experiencing and can see that you are internally receiving an FDP-350 with your Navy Federal Credit Union account(s). This message occurs when your security token has expired, and you need to reenter your account credentials. You can access this FAQ for more information. It is recommended to save a backup before proceeding (just in case).

To resolve this issue: You will simply need to click Reauthorize, then follow the on-screen prompts to sign in and reauthorize your accounts.

I hope this helps!

bzargarcia

I've deleted my Navy Federal token several times today, refreshed, and confirmed it was removed. Every time I add the token back, the token is dated 3/28/24 on Navy Federal's website and the process does not change. I'll try again tomorrow.

bzargarcia

I attempted to link again this morning. the same thing. 1) Ensured my token was deleted on Navy Federal 2) ensure Navy Federal accounts in Quicken are not linked 3) + on Quicken and attempt to link account. 4) Log into Navy Federal 5) Navy Federal shows me accounts to be linked 6) Get status 500, Internal Server Error 7) receive text and email from Navy Federal saying accounts have been linked 8) Navy Federal token is dated 3/28/24 on Navy Federal's website. 9) Accounts are not linked in Quicken

bzargarcia

Solved my problem. I cleared my cache and cookies on my Safari browser and the problem went away. I got the idea from Navy Federal.

Quicken Jasmine

Hello @bzargarcia,

Thank you for coming back to update us, I am happy to hear that you were able to resolve the issue!