dial tcp ***:***: i/o timeout

[harsharora05]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Misc

Discussion Details

When I set my security group to allow TCP from 0.0.0.0/0, everything works fine. But when I add my Wi-Fi IP to the TCP rule in the security group, I’m not able to SSH into my machine. If I switch to my personal hotspot, I can SSH into the virtual machine—but only from my Mac.
However, when the GitHub Action runs using my mobile hotspot, it shows a network error

Docker file :

name : deploy backend to EC2
on:
push:
branches:
- main
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- name: clone repo
uses: actions/checkout@v5
- name: Login to Docker Hub
uses: docker/login-action@v3
with:
username: ${{ secrets.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_TOKEN }}
- name: Build and push Docker image
id: push
uses: docker/build-push-action@3b5e802
with:
context: .
file: ./docker/dockerfile.backend
push: true
tags: harsharora17/my_backend:${{ github.sha }}
- name: Authorize SSH Connections
uses: mnavarrocarter/[email protected]
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws-region: 'us-east-1'
aws-security-group-id: ${{ secrets.AWS_SSH_SECURITY_GROUP_ID }}
protocol: 'tcp'
port: ${{ secrets.PORT }}

        - name: Execute remote SSH commands using SSH key
          uses: appleboy/ssh-action@v1 
          with:
            host: ${{ secrets.HOST }}
            username: ${{ secrets.USERNAME }}
            key: ${{ secrets.KEY }}
            port: ${{ secrets.PORT }}
            script: |
                sudo docker stop my_backend 
                sudo docker rm my_backend 
                sudo docker rmi -f harsharora17/my_backend 
                sudo docker pull harsharora17/my_backend:${{ github.sha }} 
                sudo docker run -e DATABASE_URL=${{secrets.DB_URL}} --name my_backend -p 3001:3001 -d harsharora17/my_backend:${{ github.sha }} 

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐