Technical Help: Resetting Your Password, Fixing Connectivity Issues, and Resolving the “Test Stage Missing” Lab Error in the GitLab Safety Exercise

Introduction

Whether you’re new to the Practical DevSecOps training platform or a seasoned learner, encountering roadblocks can be frustrating. This guide consolidates three of the most common support topics into a single, easy‑to‑follow article:

1. How to reset your portal password

2. Troubleshooting network‑related access problems

3. Resolving the “test stage seems to be missing” error in the How to Embed Safety into GitLab lab

Follow the step‑by‑step instructions, practical examples, and troubleshooting tips below to get back on track quickly.

1. Resetting Your Portal Password

Why a password reset might be needed

• Forgotten or mistyped credentials

• Security policy requiring periodic password changes

• Account lockout after multiple failed login attempts

Step‑by‑Step Reset Process

1. Open the password‑reset page. Here is the link below

   https://id.practical-devsecops.training/realms/public/account/
   

2. Locate the “Change Password” section – it is usually positioned near the top of the page.

3. Enter your current password (if you remember it) and then type the new password twice.

4. Follow any password‑policy hints (e.g., minimum length, required symbols).

5. Click “Submit”. You should see a confirmation message indicating that the password was updated successfully.

Tips for a Strong, Memorable Password

• Use a passphrase: combine 3–4 unrelated words (e.g., BlueCactus!2025).

• Include at least one uppercase letter, one number, and one special character.

• Avoid personal information such as birthdays or names.

If you do not receive a confirmation or encounter an error, clear your browser cache or try a different browser, then repeat the steps.

2. Troubleshooting Connectivity Issues

Access problems can stem from many sources—your local environment, corporate security controls, or the training platform itself. Below is a systematic checklist to isolate and resolve the most common culprits.

2.1 Checklist for Immediate Fixes

2.2 Detailed Troubleshooting Flow

1. Confirm the site is up – check https://status.practical-devsecops.training (if available) or use a service like DownDetector.

2. Ping the domain from a terminal:

   ping id.practical-devsecops.training
   

   If you receive timeouts, the issue is likely network‑level.

3. Trace the route to pinpoint where packets are dropped:

   traceroute id.practical-devsecops.training   # macOS / Linux
   tracert id.practical-devsecops.training      # Windows
   

4. Contact your IT department if the trace stops at a corporate gateway—request an exception for the training domain.

2.3 Pro Tips

• Keep a dedicated browser profile for training (no extensions, default settings).

• If you frequently switch between work and personal networks, consider using a portable browser on a USB stick.

• Document any corporate proxy settings; you may need to add them to the browser’s proxy configuration.

3. Fixing the “Test Stage Seems to Be Missing” Error in the GitLab Safety Lab

The How to Embed Safety into GitLab lab asks you to rename a job from test to oast. The error “test stage seems to be missing” appears when the stage name is inadvertently altered instead of the job name.

3.1 Understanding Jobs vs. Stages

• Job – a single unit of work (e.g., oast).

• Stage – a logical grouping of jobs (e.g., test).

Both are defined in the .gitlab-ci.yml file, and the CI/CD runner expects the exact stage name that already exists.

3.2 Correct YAML Snippet

oast:                     # <-- This is the **job** name you rename
  stage: test            # <-- Keep the **stage** name unchanged
  script:
    - docker run --rm -v $(pwd):/src hysnsec/safety check -r requirements.txt --json > oast-results.json
  artifacts:
    paths: [oast-results.json]
  when: always
  allow_failure: true

3.3 Step‑by‑Step Fix

1. Open the .gitlab-ci.yml file in your preferred editor.

2. Locate the block that begins with test: (the original job name).

3. Change only the label before the colon from test: to oast:. Do not modify the line stage: test.

4. Save the file and commit the change:

   git add .gitlab-ci.yml
   git commit -m "Rename test job to oast for safety lab"
   git push origin <your‑branch>
   

5. Return to the lab UI and click Check. The challenge checker will now recognize the correctly named job.

3.4 Common Pitfalls

3.5 Quick Validation

Run a local pipeline simulation (if you have GitLab Runner installed) to verify syntax before committing:

gitlab-runner exec docker .gitlab-ci.yml

If the job executes without stage errors, the lab should pass.

4. Frequently Asked Questions & Quick Tips

FAQ

• Q: I reset my password but still can’t log in.
  A: Clear browser cookies for the domain, or try a different browser.

• Q: My corporate firewall blocks the portal even after disabling VPN.
  A: Request an explicit whitelist for id.practical-devsecops.training from your IT security team.

• Q: The GitLab lab still shows the error after I think I fixed it.
  A: Ensure you committed the change and pushed to the correct branch. The checker only evaluates the remote repository.

Quick Tips

• Bookmark the password‑reset URL for future reference.

• Keep a network troubleshooting cheat sheet (ping, traceroute, incognito) handy.

• Use Git diff (git diff HEAD~1) to verify only the intended lines changed in the .gitlab-ci.yml.

Conclusion

By following the structured procedures outlined above, you can quickly reset your portal password, overcome typical connectivity hurdles, and resolve the “test stage seems to be missing” error in the GitLab safety lab. Mastering these troubleshooting skills not only smooths your learning journey but also reinforces the DevSecOps mindset of proactive problem solving.

If you encounter any other issues, please reach out to the Technical Support team via the learning platform’s help desk. Happy securing!