The following is a non-exhaustive list of ports used by Sentry services or any dependency of a Sentry service in development setups. It serves two purposes:
- Finding out why a port is used on your work machine and which process to kill to make it free.
- Finding out which ports are probably safe to assign to new services.
|8000||Sentry Dev||Sentry API + frontend. Webpack listens on this port and proxies API requests Django app|
|8001||uWSGI||Starts/stops with |
|7999||Sentry frontend prod proxy||For testing local UI changes against a prod API|
|8000||Develop docs||The website around this document. Conflicts with Sentry Dev.|
|3000||User docs||User-facing documentation. May conflict with Relay if Relay is run outside of devservices.|
|9001||Sentry Dev Styleguide server||Bound when running |
|9000||Legacy default port for |
|9001||Barebones frontend without webpack or Relay. Sentry Dev is likely better. Conflicts with Sentry Dev Styleguide server.|
|8000||Relay mkdocs documentation||At some point this is going to get merged into our existing docs repos. Conflicts with Sentry Dev.|
lsof -nP -i4 | grep LISTENto find occupied ports on macOS.
- The Dashboard UI of Docker for Mac shows you running docker containers/devservices together with assigned ports and option to start/stop.
You can edit this page on GitHub.