Can’t connect to my n8n Server with API key. Says HTML is being returned, but clearly JSON coming back on the Apps diagnostics page.
Thank you so much for the detailed technical analysis and for taking the time to report this issue. You’ve identified a real bug in the app’s error handling logic.What’s happening:After reviewing your case and the app code, I can confirm that this is indeed a bug in neightn_remote. The app is receiving valid JSON from your n8n server (as your packet capture and diagnostics show), but the error handling logic incorrectly reports “HTML instead of JSON” when it should be saying “JSON structure incompatibility.”The app’s diagnostic tool uses proper response type detection, but the main connection logic uses outdated error handling that gives misleading error messages.The fix:I’m implementing improved error handling logic that will:•Properly detect response types (HTML vs JSON vs plain text)•Give accurate error messages based on the actual problem•Better handle different n8n versions and API structures•Match the logic used in the diagnostic toolTimeline:I’ll be releasing an updated version of the app this week with these improvements. The update will properly identify whether you’re getting HTML (proxy/Cloudflare issues), valid JSON with wrong structure (n8n version differences), or other response types.Apology:I sincerely apologize for the confusion this bug has caused. Your detailed technical investigation was incredibly helpful in identifying the root cause, and I really appreciate your patience.I’ll send you a follow-up email once the update is live on the App Store. Thank you again for helping make neightn_remote better for everyone!Best regards,