Troubleshooting Membrane API Gateway

Common problems you may run into while running Membrane API Gateway, and how to fix them.

Bad Gateway (502) Errors

A 502 Bad Gateway response means Membrane could not reach the backend it is routing to. Make sure the backend service is running and reachable, and that its address is configured correctly in your apis.yaml or Proxies configuration.

404 Invalid Path or Method

A 404 Not Found response with Invalid path or method means no API matches the port, host, method and path of the request. See Invalid path or method for the causes and fixes.

Port Already in Use

If port 2000 is already taken by another process, stop the conflicting service or change the port Membrane listens on in your API configuration.

Docker Volume Changes Not Applying

If edits to apis.yaml don't take effect after a restart, verify the volume mount path in your docker run command points to the same file you are editing.

Still stuck? Ask on GitHub Issues, or continue with the Getting Started guide.