account credentials entail not storing or failing to connect

[Camo67]

Bug Description

Subject: API and Credential Connection Issues in n8n

Description of the Issue:
I am experiencing persistent issues with API and credential connections in n8n. Despite ensuring that all settings are configured correctly, the following problems occur:

1. API and Credential Failures:

   • API credentials and other integrations intermittently fail to connect or authenticate.
   • Credentials that have been successfully tested occasionally stop working without changes being made.

2. Connection Instability:

   • Even after verifying and reconfiguring, connections sometimes drop randomly during workflows.
   • The issue persists across various nodes, regardless of the API being used.

3. Deletion and Recreation Did Not Resolve the Issue:

   • I have deleted and recreated affected credentials and workflows multiple times, but the problem remains.

Steps Taken to Troubleshoot:

• Verified all API keys, tokens, and credentials for correctness.
• Double-checked endpoint URLs and authentication settings for each node.
• Deleted and re-added credentials and workflows as a last resort.
• Ensured that n8n is running on the latest version.

Expected Behavior:
API credentials and connections should remain stable once configured correctly. Credentials that pass validation should not fail intermittently during normal operation.

Environment Details:

• n8n Version: [Insert version here]
• Hosting Environment: [e.g., self-hosted, cloud-hosted, Docker, etc.]
• APIs Affected: [List specific APIs, if relevant]

I would appreciate any guidance or support in resolving this issue, as it significantly impacts my workflows. Please let me know if additional information or logs are required.

Thank you.

Best regards,
Cameron De Vries
Founder of Our Community in Unity
Email: [email protected]
Phone: +27 81 569 3926

To Reproduce

entered credentials and tested it worked then it didnt gpt fails

Expected behavior

i expect it to work

Operating System

ubuntu 2.0

n8n Version

Running version [email protected]

Node.js Version

18

Database

MySQL

Execution mode

main (default)

[Joffcom]

Hey @Camo67,

We have created an internal ticket to look into this which we will be tracking as "N8N-8052"

[Camo67]

Hi Jon, Thank you for the update regarding the internal ticket "N8N-8052". I appreciate the effort being put into addressing this matter and am looking forward to any updates or resolutions that come from it. Please let me know if there's anything further I can provide to assist. Best regards, Cameron De Vries

…

On Mon, Jan 6, 2025 at 7:36 PM Jon ***@***.***> wrote: Hey @Camo67 <https://github.com/Camo67>, We have created an internal ticket to look into this which we will be tracking as "N8N-8052 <https://linear.app/n8n/issue/N8N-8052>" — Reply to this email directly, view it on GitHub <#12475 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBYVD2DA3DOD2BZCXRLJYSD2JK5JTAVCNFSM6AAAAABUWBTEK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGU4DQNBUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

Hey @Camo67

Can you be more specific here, which credentials are not working / storing / connecting?

When credentials fail to connect what error are you seeing?

It sounds like this could be an environmental issue or something out of our control like a networking issue but without more details it is hard to say.

[Camo67]

All my credentials it did work but suddenly it doesn't mostly GPT

…

On Mon, 6 Jan 2025, 20:14 Jon, ***@***.***> wrote: Hey @Camo67 <https://github.com/Camo67> Can you be more specific here, which credentials are not working / storing / connecting? When credentials fail to connect what error are you seeing? It sounds like this could be an environmental issue or something out of our control like a networking issue but without more details it is hard to say. — Reply to this email directly, view it on GitHub <#12475 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BBYVD2DTDLDUDLLND7TKCD32JLBXRAVCNFSM6AAAAABUWBTEK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGY2TEMJUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Joffcom]

Hey @Camo67,

In that case I am not able to reproduce this on our internal instance of n8n, my own self hosted instance or my cloud instance. Can you share more details and possibly screenshots or a video showing how to reproduce this?