Reverse proxy appears 404[HELP] about zoraxy

[Morethanevil]

Your request comes from the internet to your hostmachine and then in the docker container. 127.0.0.1, localhost points INSIDE the container., because Zoraxy runs inside the container. This is not a bug, this is normal. Your setup would work if it were not a container then localhost, 127.0.0.1 would be your host machine.

This is why it works with your public IP and port ☺️

[allmors]

You can set a static IP for Zoraxy. This works too. Then you can use the static IP of Zoraxy and the port inside the container. You can find a little guide in the wiki

Thanks for your answers, I made a mistake

[tobychui]

@allmors This is expected behavior when deploy inside docker. The solution is reverse proxy through the public ip address of your instance (assuming it is directly exposed to the internet with a public IP address). Good to see that you have already figure out the solution yourself!

If your problem have been resolved and you got no further questions, please close this issue.

[allmors]

@allmors This is expected behavior when deploy inside docker. The solution is reverse proxy through the public ip address of your instance (assuming it is directly exposed to the internet with a public IP address). Good to see that you have already figure out the solution yourself!

If your problem have been resolved and you got no further questions, please close this issue.

Well, I thought it would be like nginx proxy manager. Even if it is a container deployment, it can still use the host's loopback address.

If it is normal through the public network, then the port must be exposed, which feels a bit redundant.

[Morethanevil]

You can set a static IP for Zoraxy. This works too. Then you can use the static IP of Zoraxy and the port inside the container. You can find a little guide in the wiki

[allmors]

You can set a static IP for Zoraxy. This works too. Then you can use the static IP of Zoraxy and the port inside the container. You can find a little guide in the wiki

I forgot that the docker container has a network card docker0, because all projects are deployed by docker, I should not use 127.0.0.1, but the loopback address of docker0, such as 172.17.0.1

If possible, you can refer to nginx proxy manger, which supports local host loopback address.