You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 23, 2019. It is now read-only.
Historically, we listened on port 8080 with a separate web process. Especially now that docker runs natively on OS/X, we're likely to conflict on that port. It might be best to stop listening on 8080 completely and instead point people to the standard zipkin port: 9411
…#116)
It has been a while since zipkin-web. It is better for us to use the
canonical port for zipkin vs something it doesn't naturally advertise.
Fixes#103
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Historically, we listened on port 8080 with a separate web process. Especially now that docker runs natively on OS/X, we're likely to conflict on that port. It might be best to stop listening on 8080 completely and instead point people to the standard zipkin port: 9411
cc @klingerf @kristofa @abesto
The text was updated successfully, but these errors were encountered: