I could post all of the steps that I have taken here…if that’s OK…not sure if it is. I’ve spent a LOT of time stuck on this one and I would love to actually understand what I am missing.
Also one more thing:
Does it matter that I am running all of these commands (on all App servers) as root user? I was unable to install/start/enable firewalld without first switching to root user.
Does it matter that I am running all of these commands (on all App servers) as root user? I was unable to install/start/enable firewalld without first switching to root user.
Does the network interface that I choose affect the overall outcome of this task? For my last attempt I went with WAN.
Also, it appears that I am getting closer to the finish line (thank you @francilio & @amuthan1983), but I am getting an access forbidden error when trying to curl nginx. I’m not sure why this is happening. The telnet commands appear to be working as expected now, as in Jump host is connecting to nginx , but not to Apache & the LB Server is connecting to NGINX and to Apache.
…feels like I’m really close, but not sure.
Apologies for all of the questions, but for some reason this task is really tripping me up.
It is difficult for me to tell where exactly you may have gone wrong without getting some more details with regards to the steps that you have taken, but from the image/screenshot, it looks to me like you failed to implement step 2:
Allow incoming connections from LB host only on Apache port and block for all others.
Try adding a rich rule that forwards traffic from LB to Apache.
The server block should be listening on the nginx port 8096, not on the apache port 8087. Leave proxy_pass http://172.16.238.10:8087/; as it is because Nginx is running as a reverse proxy server for Apache (as stated in the instructions).
I hope this helps:-)
…and make sure to restart nginx & apache after you’ve made your changes:
systemctl restart nginx
systemctl status httpd
BTW, I assume that you are running these command as the root user because there is no sudo prepended to your commands…
Hi @juliettet, Thank you for pointing out. I recognized my silly mistake while doing this task. But the task is marked as failed and not letting me know to retry since yesterday. Any thoughts as how to bring it back to review mode so i can give a try ?
You should have an option (in your dashboard, on the right side of the task that was marked as failed) to mark for review. Click on that & when someone responds with the correct answer/response, click on the check mark to mark the response as correct. After that, you should see an option to retry the task back in your main dashboard.