Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon
Labs

Testing a Connection

In this hands-on lab, you will need to troubleshoot connectivity issues between `Client1` (10.0.1.11) and `Server1` (10.0.1.10). You will need to determine why the website at 10.0.1.10 is unreachable, and prep the host to make sure connectivity is in place to permit SSL traffic once it's configured.

Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Intermediate
Duration
Clock icon 1h 0m
Published
Clock icon Nov 14, 2018

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Confirm the problem.

    On Client1 (10.0.1.11)

    Confirm that the problem exists by curling the headers of 10.0.1.10 from 10.0.1.11:

    curl -I 10.0.1.10

  2. Challenge

    Confirm, and maybe resolve, Apache's status.

    On Server1 (10.0.1.10):

    Verify a service is listening on port 80:

    ss -lntp | grep :80

    If nothing is listening, check if Apache is running:

    systemctl status httpd

    Start Apache if necessary:

    systemctl start httpd

    Did that resolve the problem?

  3. Challenge

    Check firewall rules.

    On Server1 (10.0.1.10):

    Verify that the firewall is configured to permit http traffic:

    firewall-cmd --list-services

    If http isn't present, it will need to be added:

    firewall-cmd --permanent --add-service=http

    And the firewall rules will need to be reloaded to take effect:

    firewall-cmd --reload

    Verify that the problem is resolved.

  4. Challenge

    Permit https traffic in the firewall and verify.

    On Server1 (10.0.1.10):

    You will need to open port 443 in the firewall. You can do it with:

    # firewall-cmd --permanent --add-service=https

    And then reloading the firewall config with this:

    # firewall-cmd --reload

    You will need to facilitate listening on port 443 from Server1 (10.0.1.10). You can do this by installing the nmap-ncat package for CentOS:

    # yum install nmap-ncat

    And then using it to listen on port 443:

    # nc -l -p 443

    On Client1 (10.0.1.11):

    Install telnet:

    $ yum install -y telnet

    You can verify that 443 is accessible by using telnet:

    $ telnet 10.0.1.10 443

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans