基于《Ansible Up and Running》实验：部署Nginx后localhost:8080无响应

Hey there! Let's work through this step by step to get your Nginx setup responding on port 8080. Here are the key checks to run:

1. Verify the Ansible Playbook Ran Successfully #

First things first—did your playbook execute without errors?

• Run your playbook again with verbose output to catch any hidden issues: ansible-playbook web-notls.yml -v
• Double-check that the files/nginx.conf file exists in the same directory as your playbook (inside a subfolder named files). The copy module looks for source files here by default, so a missing file would cause a failure.

2. Check if Nginx is Running Properly #

Log into your target machine (or run these commands locally if webservers points to localhost):

• Check Nginx's current status: sudo systemctl status nginx
  • If it's not running, use sudo journalctl -u nginx to view logs and identify why it failed to start.
• Test your Nginx configuration for syntax errors: sudo nginx -t
  • This will flag any invalid config lines that might be preventing Nginx from launching.

3. Confirm Nginx is Listening on Port 8080 #

By default, Nginx listens on port 80—your config might not have been updated to use 8080:

• Check which ports Nginx is actively using: sudo ss -tulpn | grep nginx
• Open your copied config file (/etc/nginx/sites-available/default) and verify there's a line like listen 8080; (instead of the default listen 80;). If not, update it, then reload Nginx with sudo systemctl reload nginx.

4. Check Firewall Settings #

Ubuntu 16.04 uses UFW by default—make sure port 8080 is open to incoming traffic:

• Check current firewall rules: sudo ufw status
• If 8080 isn't listed, allow it with: sudo ufw allow 8080/tcp

5. Validate Your Ansible Inventory Targets #

Your playbook targets the webservers group—ensure this group includes the correct host:

• Open your Ansible inventory file and confirm it has an entry like:

  [webservers]
  localhost ansible_connection=local
  

• If webservers points to a remote machine, you should test accessing the remote machine's IP address:8080, not localhost on your control node.

6. Test Local Connectivity #

On the target machine, run curl localhost:8080 directly:

• If this returns content, the issue is likely with network routing or firewall rules between your client and the target.
• If it doesn't return anything, go back to checking Nginx's status and config for errors.

内容的提问来源于stack exchange，提问作者lsambo