Docker problem: empty reply from server when accessing API from Docker container (macOS)

[grimkrit]

I am experiencing an issue where the Local REST API plugin in Obsidian returns an "Empty reply from server" error when attempting to access it from a Docker container running on macOS. This occurs despite all network and plugin configurations appearing to be correct.

Environment:

• Obsidian Version: (Please provide your Obsidian version, e.g., 1.8.10)
• Local REST API Plugin Version: (Please provide your plugin version, e.g., 3.2.0)
• Operating System: macOS (Specify version, e.g., Sonoma 14.4)
• Docker Desktop Version: (Please provide your Docker Desktop version)
• Agent Zero Container: Running in a Kali Linux environment.

Steps to Reproduce:

1. Obsidian Plugin Configuration:

   • HTTP Server is enabled.
   • Bind Address is set to 0.0.0.0.
   • 'Require TLS' is disabled.
   • A new API key has been generated and is confirmed to be correct (previous API key error message is gone).

2. macOS Firewall: Confirmed to be disabled.

3. Docker Container Network Connectivity:

   • Confirmed full internet connectivity from within the Docker container (ping 8.8.8.8 and curl http://example.com both work).
   • Docker Desktop has been restarted.

4. Plugin Listening Status:

   • lsof -i :27124 on macOS confirms the plugin is listening on *:27124.
   • netcat -zv host.docker.internal 27124 from within the Docker container successfully connects to the port.

5. Attempted API Call from Docker Container:

   curl -v -H 'x-api-key: YOUR_API_KEY' http://host.docker.internal:27124/notes

   (Also tested with /[vault](http://localhost:50080/#) endpoint)

Expected Behavior:

The API should return a valid JSON response (e.g., an empty array for notes if no notes exist, or vault information for /[vault](http://localhost:50080/#)).

Actual Behavior:

The curl command consistently returns curl: (52) Empty reply from server.

Troubleshooting Performed:

• Verified all plugin settings (HTTP Server, Bind Address, TLS).
• Confirmed macOS firewall is off.
• Generated multiple new API keys.
• Confirmed Docker container network connectivity (internet access).
• Confirmed plugin is listening on the correct port and address (lsof).
• Confirmed TCP connection can be established from container to plugin (netcat).
• Checked Obsidian's developer console for errors (empty).
• Checked obsidian.log file for errors (only update checks, no plugin-related errors).

Additional Notes:

It appears the plugin accepts the TCP connection but fails to send any HTTP response, and no errors are logged by Obsidian itself, making debugging difficult. This suggests a potential issue within the plugin's HTTP server implementation.

[coddingtonbear]

I'm afraid I'm using this in a docker container regularly and I'm not able to reproduce any errors; so I have to assume this is a problem in your specific container configuration. My guess would be that you haven't properly routed ports from the external environment into the internal one.

I'll convert this into a discussion, though, so others might be able to help you out if they have any ideas!