Debugging ingress

Hi,
So I have deployed a few workloads, one with a nodeport, one with a cluster ip, and one with no port mappings.
I created an ingress rule for all, and mapped to them according to the path.
Whenever I hit one of the paths of the ingress, I get the following:

503 Service Temporarily Unavailable

openresty/1.15.8.1

And when I hit something that is not supported (for instance no path), I get a 504.

I did something as simple as following
https://rancher.com/docs/rancher/v2.x/en/quick-start-guide/workload/quickstart-deploy-workload-nodeport/
But unfortunately it didn’t work for me.
I don’t know if they are firewall issues, I’m on Centos 7, and enabled the firewall rules suggested here:
https://rancher.com/docs/rancher/v2.x/en/installation/options/firewall/

If I login to the node, and wget the url of the container with the local ip, it works fine, so I think something is wrong with ingress, but I don’t know where to start debugging.

1 Like