-
Notifications
You must be signed in to change notification settings - Fork 444
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
404s for toxics and reset #106
Comments
Any reason you can't upgrade to Toxiproxy 2.0? |
I knew there was something simple! Haha. What's the download path to the deb? The docs point at 1.2, which is the reason I'm using it |
Here's the link: https://github.com/Shopify/toxiproxy/releases/download/v2.0.0/toxiproxy_2.0.0_amd64.deb |
That did it. Thanks a ton! |
Our pleasure. :) |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I set up Toxiproxy(1.2.1 from the .deb) with 3 servers. When i go to
http://localhost:8474/proxies
or doToxiproxy.all
I get results back, but when I try to examine the toxics for any of the servers, it 404s. Same withToxiproxy.reset
. Surely there's something simple I'm missing.Individual proxies work as well.
Toxiproxy[:my_service]
works fine. It'sToxiproxy[:my_service].toxics
that 404sThe text was updated successfully, but these errors were encountered: