Großartige App! Perfekt für den Alltag
Man merkt, dass hier jemand Ahnung von n8n hat. Gerade für kleinere Anpassungen oder zum schnellen Überprüfen von Flows mit der Monitor Funktion ist sie echt praktisch. Tut genau das was sie soll. Dafür gibt es verdiente 5 Sterne von mir!
Be careful(update)
Response from developer
Thank you so much for updating your review. I am happy to hear that the app now works for you. All the different setups makes it tricky to solve all possible issues preventive. So if you have more issues, please let me know so I will try to fix that so neightn_remote becomes useful for more users an more setups. Thank you!!!! Best regards, Enrico
Not Working
Response from developer
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 tool Timeline: 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,
Be careful
Response from developer
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 tool Timeline: 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,
Error: Unsupported URL
Response from developer
Hi! Vielen Dank für dein Feedback zu deinem lokalen Server Setup. Das "Unsupported URL" Problem kann verschiedene Ursachen haben. Um dir besser helfen zu können, wären ein paar Details hilfreich: **Quick Check:** • Verwendest du HTTP oder HTTPS in der Server URL? • Funktioniert die URL im Browser auf dem iPhone? • Wie ist dein Reverse Proxy konfiguriert? **Mögliche Lösungsansätze:** Bei **lokalen HTTP-Servern** können Custom Headers oft helfen: - Gehe zu Server-Einstellungen → Custom Headers aktivieren - Füge Headers wie Host: `localhost` oder X-Forwarded-Proto: `http` hinzu **Teste das Header Diagnostics Tool:** - Findest du in den Server-Einstellungen - Analysiert automatisch deine Server-Response - Schlägt passende Headers vor Bei **selbst-signierten HTTPS-Zertifikaten:** - Die App unterstützt Custom SSL Handling für Development-Server **Weitere Optionen:** - Anderen Port testen (8080 statt 443) - Direktverbindung ohne Reverse Proxy prüfen Falls du mehr Details zu deinem Setup teilen möchtest, kann ich gezielteren Support anbieten! Mail bitte an: info@neightn-remote.org Update: Ich würde dir wirklich gerne helfen, aber wenn so gar nichts von deiner Seite kommt, kann ich das nicht. Ich bin immer bemüht neightn_Remote weiter zu verbessern und den Nutzern ein bestmögliches Erlebnis zu bieten. Ich finde es nicht fair, dass du dich (vielleicht zu Recht) beschwerst, mir aber keine Möglichkeit gibst dir zu helfen. Daher nochmals die Bitte: Melde dich unter info@neightn-remote.org. Alternativ, ziehe deine Rezension zurück, wenn du nicht daran interessiert bist das Problem mit mir zusammen zu lösen. Kleiner Hinweis noch: http in Kombination mit Port 443 lässt Apple nicht zu. Das ist kein Bug der App. Liebe Grüße, Enrico
Bis zum letzten update, ein super Tool.
Response from developer
Hallo Jonand4711. Ich habe die Ursache gefunden und muss mich bei allen Nutzern entschuldigen. Die API Anfragen sind bei kleinen Servern zu groß gewesen. Ich habe die Anfragen neu strukturiert und das Update eben hoch geladen. Mit der neuen Version funktioniert wieder alles einwandfrei. Entschuldigung nochmal an alle Anwender für diesen Bug!!!!!
No http
Response from developer
Thank you for your feedback! Based on your input, we've implemented a comprehensive custom headers system that now supports HTTP connections. You can find this new feature in the Server tab → Custom Headers, where you can add authentication headers and other custom HTTP headers that HTTP-based APIs typically require, such as CF-Access-Client-Id, X-API-Key, or any other custom authentication headers your HTTP endpoint needs. The URL input field accepts HTTP URLs without any restrictions, so that shouldn't be the issue. If you're still experiencing problems with HTTP connections, could you let me know: 1. What type of authentication or headers does your HTTP endpoint require? 2. Are you seeing any specific error messages when trying to connect? I'd be happy to help you configure the right headers for your HTTP setup! Since we've added this feature specifically based on user feedback like yours, we'd really appreciate if you could give the app another try and let us know how it works for you now!
Super nützliches Tool
Response from developer
Hallo hollymoeller, vielen Dank für die tolle Rezession. Wir arbeiten stetig daran die App weiter zu verbessern.
