Workshop
- Identity provider
- WARP and device posture
- Cloudflare Tunnel
- Access and Private Network
- Browser isolation and App launcher
- Digital experience monitoring
AcmeCorp’s users can now connect to Cloudflare with WARP. Next, let’s onboard company’s applications. There are 3 AcmeCorp’s applications running on your Linux server:
Use Cloudflare Tunnel (cloudflared
) as an on-ramp for all of these.
1. Connect to the Ubuntu VM
Note the 3 AcmeCorp’s applications running by typing this command:
sudo docker ps --format "{{.Names}}: {{.Ports}}"
⚙️ nocopy ⚙️
## You should see the following Output: ##
# website: 0.0.0.0:80->80/tcp, :::80->80/tcp
# intranet: 0.0.0.0:8000->80/tcp, :::8000->80/tcp
# samba: 0.0.0.0:139->139/tcp, :::139->139/tcp, 137-138/udp, 0.0.0.0:445->445/tcp, :::445->445/tcp
2. Create a tunnel and onboard public website
cloudflared
and automatically configure the tunnelcloudflared
before you try installing it again:sudo cloudflared service uninstall && sudo rm -rf /etc/systemd/system/cloudflare* && sudo systemctl daemon-reload
cloudflared
will tunnel that traffic to the origin server's port 803. Connector diagnostics
Now, your tunnel should be working. But before we test that, let’s open Connector diagnostics for our tunnel. Here, you can see the traffic coming through the tunnel, and you can troubleshoot any potential issues.
Here you can see the Data Centers your tunnel is connected to, its cloudflared
version, private IP, and so on.
Click on Begin log stream to start monitoring traffic going through the tunnel
4. Test access to public website
Open the FQDN you just defined, for example, ancient-uncle.cfiq.io from any browser on your VM Windows host. You should see AcmeCorp’s website:
You can also see these requests coming through in the Connector Diagnostics you configured in Step 3: