Home Lab Access & Prerequisites Accessing Lab Demos, Course Videos, and Post‑Lab Resources in Your DevSecOps Training

Accessing Lab Demos, Course Videos, and Post‑Lab Resources in Your DevSecOps Training

Last updated on Mar 03, 2026

Accessing Lab Demos, Course Videos, and Post‑Lab Resources in Your DevSecOps Training

Welcome to the DevSecOps learning hub! Whether you’re just starting the “Full Enterprise‑Grade DevSecOps Pipeline” demo or you’ve completed the hands‑on labs, you’ll need clear guidance on how to log in, what resources remain available after the lab period ends, and how to troubleshoot common video‑playback issues. This article consolidates the most frequently asked questions, provides step‑by‑step instructions, and offers practical tips so you can focus on mastering DevSecOps concepts instead of hunting for credentials or fighting firewalls.


Table of Contents

  1. Logging into GitLab for the “Full Enterprise‑Grade DevSecOps Pipeline” Demo

  2. What Happens to Your Access After the Lab Expires?

  3. Fixing the “Sorry, because of its privacy settings, this video cannot be played here” Error

  4. Quick Reference Checklist

  5. Additional Tips & Best Practices


1. Logging into GitLab for the “Full Enterprise‑Grade DevSecOps Pipeline” Demo

Why the confusion?

The introductory labs introduce the platform but do not provide the GitLab credentials used in the later “Full Enterprise‑Grade DevSecOps Pipeline” demo. Those credentials are supplied only in the dedicated Lab Guide for that specific module.

How to obtain the credentials

  1. Open the Lab Guide

    • Navigate to the Learning PathModulesFull Enterprise‑Grade DevSecOps Pipeline.

    • Click Download Lab Guide (PDF) or view it directly in the browser.

  2. Locate the “GitLab Access” section

    • It is usually highlighted in the guide (see the screenshot in the original question for reference).

    • The section lists a username and a temporary password that are valid for the duration of the lab (typically 60 days).

  3. Log in to GitLab

    • Go to https://gitlab.<your‑training‑domain>.com.

    • Enter the provided username and password.

    • You will be prompted to change the password on first login—choose a strong, memorable passphrase.

What to do if you can’t find the credentials

  • Check the “Resources” tab on the course landing page – the Lab Guide is often duplicated there.

  • Contact Support via the Chatwoot and request a real agent for help you.


2. What Happens to Your Access After the Lab Expires?

Resource Access Duration What You Keep How to Preserve It
Course Videos 3 years from enrollment (subject to change) Unlimited streaming of all recorded lectures No action needed; videos remain in your account.
Hands‑On Labs 60 days from first login Access to the live lab environment ends after 60 days. Export any artefacts (e.g., pipeline YAML, Docker images) before the expiration date.
PDF Manual / Lab Guide Permanent (once downloaded) The PDF stays on your device forever. Save a copy to a personal cloud drive or local backup.

Steps to Secure Your Work Before Lab Expiration

  1. Download artefacts – Use the “Export” button in the lab UI or run git clone to pull repositories locally.

  2. Snapshot your environment – If you used a cloud‑based lab, take a snapshot or export the Docker images (docker save).

  3. Document your pipeline – Save the .gitlab-ci.yml file and any custom scripts to a personal repository.


3. Fixing the “Sorry, because of its privacy settings, this video cannot be played here” Error

This error is usually caused by network restrictions, corporate firewalls, or regional content blocks. Follow the troubleshooting flow below:

Step‑by‑Step Troubleshooting

  1. Use a Personal Device

    • Company‑issued laptops often have security agents that block external video streams.

    • Switch to a personal computer or a personal tablet for testing.

  2. Check Your Network

    • Verify that you are on a stable, unrestricted Wi‑Fi or wired connection.

    • Avoid public Wi‑Fi that requires captive portals (e.g., coffee‑shop login pages).

  3. Try an Alternate Network

    • If possible, connect via a mobile hotspot or a different ISP to rule out ISP‑level blocking.
  4. Use a VPN

    • A reputable VPN can route traffic through a region where the video host is not blocked.

    • Ensure the VPN complies with your organization’s security policy.

  5. Clear Browser Cache & Cookies

    • Old session data can interfere with embedded video players.

    • In Chrome/Edge: Settings → Privacy and security → Clear browsing data.

  6. Disable Browser Extensions

    • Ad‑blockers or privacy extensions may block the video iframe.

    • Temporarily disable them and reload the page.

  7. Test in an Incognito/Private Window

    • This bypasses most extensions and cached data.
  8. Contact Support if All Else Fails

    • Provide a screenshot of the error, your device OS, browser version, and network type.

    • Reach out to real agent by request it in the Chatwoot(chatbot)

Quick FAQ

  • Q: Do I need a corporate VPN to watch the videos?
    A: Only if your corporate firewall blocks the video CDN. A personal VPN works as an alternative.

  • Q: Can I download the videos for offline viewing?
    A: Yes. Each video page includes a “Download” button for learners with a valid subscription.


4. Quick Reference Checklist

  • Before Starting the Full Pipeline Demo

    • ☐ Download the Lab Guide PDF.

    • ☐ Locate GitLab credentials in the guide.

    • ☐ Log in and change the temporary password.

  • During the Lab (First 60 Days)

    • ☐ Export repositories and pipeline definitions daily.

    • ☐ Snapshot any custom Docker images.

  • After Lab Expiration

    • ☐ Verify you still have access to course videos (3‑year window).

    • ☐ Keep the PDF manual saved locally.


5. Additional Tips & Best Practices

  • Bookmark Key URLs:

    • GitLab: https://gitlab.<your‑domain>.com

    • Course Videos: https://learn.<your‑platform>.com/videos

  • Version Control Your Lab Work: Even though the lab environment is temporary, treat your code as production‑grade. Commit often and push to a personal GitHub or GitLab account.

  • Document Network Requirements: Keep a note of any required ports (e.g., 443 for HTTPS, 22 for SSH) and share it with your IT department if you encounter connectivity issues.


By following the guidance above, you’ll smoothly navigate the GitLab login process, retain valuable learning assets after the lab period, and overcome video‑playback hurdles. If you run into any other roadblocks, remember that the Chatwoot and our dedicated support team are just a message away. Happy learning, and enjoy building your enterprise‑grade DevSecOps pipeline!