"Cycle prohibited" generally means that ATS has been configured to connect to itself and upon detecting this, prevents the infinite loop. This is detected by watching the "Via" header and seeing if it has the same via data as the current ATS (which, if true, means there is a cycle). If I had to debug it, I would enable debug messages with the "http" tag. That generates a lot of data, including where ATS is trying to connect when it goes upstream. I would look at that to make sure it's going where it is supposed to and not to itself.
On Thu, Apr 9, 2020 at 9:18 AM Kamil <[email protected]> wrote: > Hi, > I have ATS configured to act as a reverse proxy for AWS S3 bucket. That > works fine if I call it inside the docker container running it or when I am > calling http://localhost in the web browser on my computer. However I am > getting Cycle Prohibited error when I am trying to open it in my local > network using the private IP of my laptop. > I am trying to find anything regarding that in the docs, but there is not > too much. How can I make it working outside of my localhost? > brgds, >
