Why is there no access to the rancher container?

Question

Docker

All the best to all!
Deploying Rancher2 per this tutorial on a single node as an introduction. The node is located in the internal network and has the address 192.168.21.10.
I deployed the nginx container in the same way as described: clicked Add Port and specified 80 in Publish the container port. The rest of the values ​​were left as default. Then added Ingress as described.
As a result, there is no access to the container. On everyone was perverted both with ports, and with adjustments. Even at the step of deploying the container, supposedly I have to access it using a randomly assigned port, i.e. 192.168.21.10:31100 but no access. Although on the node curl -I 192.168.21.10:31100 gives out 200.
I sin in the direction of iptables, but everything should start out of the box.

Answer 1

Because you need to change the default ports when creating a rancher to access the web-face: for example, 80 to 8080, and 443 to 8443. When deploying the nginx container, you can not add any ports (if you do not want to connect to the container console from the web). When creating an ingress, you must specify the port 80, because it is this port that is forwarded, and no other. This can be seen after creating the ingress on the workloads page.
Here's a beard.