Thanks for the clarification. Now I understand your comment.
However 172.30.32.0/23 covers both 172.30.32.0/24 and 172.30.33.0/24. The first http was when I tried with a single subnet and the second http was what I ended up with based on the information I found what other shave been using.
As both both 172.30.32.0/24 and 172.30.33.0/24 were mentioned I combined them into 172.30.32.0/23 for simplicity. But whatever I have tried sofar it does not seem to work.
I have seen some comments about the NGINX configuration itself reated to double forwards providing similar issues but I am not quite sure whether that is related. Neither do I know how I can validate this as I do not know how I can check the NGINX default config files.