-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom error pages doesn't work for a Marathon app #4013
Labels
area/provider/marathon
area/server
kind/bug/possible
a possible bug that needs analysis before it is confirmed or fixed.
priority/P1
need to be fixed in next release
status/5-frozen-due-to-age
Milestone
Comments
nmengin
added
area/provider/marathon
priority/P1
need to be fixed in next release
kind/bug/possible
a possible bug that needs analysis before it is confirmed or fixed.
area/server
and removed
status/0-needs-triage
labels
Oct 11, 2018
Here's a stacktrace of failing request:
|
Could you try this image |
With the provided image it seems to be working:
|
Closed by #4075. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area/provider/marathon
area/server
kind/bug/possible
a possible bug that needs analysis before it is confirmed or fixed.
priority/P1
need to be fixed in next release
status/5-frozen-due-to-age
Do you want to request a feature or report a bug?
Bug
What did you do?
Deployed a Marathon app with following configuration:
furthermore I've deployed added another Marathon app for handling errors.
What did you expect to see?
The main app is scaled to
0
instances, thus there no backend available to handle requests. I'd expect Traefik to handle request with the error handling backend:backend-api-json-errors
.What did you see instead?
Output of
traefik version
: (What version of Traefik are you using?)What is your environment & configuration (arguments, toml, provider, platform, ...)?
The text was updated successfully, but these errors were encountered: