Skip to content

Setup Problems and Support

Jump to bottom
mike-snhu edited this page Aug 13, 2026 · 1 revision

Setup Problems and Support

Setup problems can occur when software must work across different computers, operating systems, security settings, user accounts, and networks.

When something does not work, identify what you were doing, what you expected, and what actually happened. You do not need to understand the error message before asking for help.

First: Keep Your Course Work Moving

If a local Windows, macOS, or Linux setup is not working, use the Codio Virtual Desktop (CVD) while you troubleshoot the local computer.

CVD setup instructions:
https://github.com/GC-STEM/it140-m1-setup-tasks/blob/main/codio/README.md

Read the Script Summary Before Continuing

The automation scripts end with a summary designed to tell you whether the phase succeeded and what to do next.

  • A normal successful configuration or update typically reports PASS and exit code 0.
  • A successful verification reports COMPLIANT, Failed: 0, and exit code 0.
  • If you see FAIL, PARTIAL, NOT COMPLIANT, a nonzero exit code, or a remediation message, do not guess at a repair or blindly continue.
  • If the summary says a restart is needed, save your work and follow the restart instructions in the README.
  • Follow the Next step shown by the script when one is provided.

What Information Should I Collect?

Before asking for help, collect as much of the following as you can:

  • Environment: CVD, Windows, macOS, or Linux
  • Operating-system version, if using your own computer
  • README section or numbered step where the problem occurred
  • What you were trying to do
  • What you expected to happen
  • What actually happened
  • Exact command you entered, if applicable
  • Complete error message or final script summary
  • Script or application name
  • Troubleshooting steps you already tried
  • Screenshot, if the problem is visible in a graphical interface
  • Relevant setup log or transcript, if one was created

The scripts store logs in the it140/logs folder under your user home directory. On the CVD this is:

~/it140/logs/

A CLI problem occurs in a command-line interface such as Terminal or PowerShell. A GUI problem occurs in a graphical application such as VS Code, Chrome, or a settings window. If you are unsure which term applies, just describe what you see.

Codio: Update Appears to Stop

The CVD Update script normally takes several minutes and can take much longer when Ubuntu has many pending updates, a large package must download, the network is slow, or an Ubuntu download server is busy.

The Terminal may appear to stop on a line beginning with Get: or Ign:. An Ign: line does not necessarily mean the update failed.

If no new output appears:

  1. Keep the Terminal open.
  2. Do not press keys or start another update command.
  3. Wait up to 30 minutes after the last new line appears.
  4. Continue waiting if new lines occasionally appear, even if the total update time exceeds 30 minutes.

If no new text appears for 30 consecutive minutes and the last line begins with Get: or Ign::

  1. Press Ctrl+C once.
  2. Wait for the script to stop and display its summary.
  3. Close the Terminal.
  4. Open a new Terminal.
  5. Run update_it140.sh one more time.

Important

Do not interrupt the script while the Terminal displays messages such as Unpacking, Setting up, or Processing triggers. These messages mean Ubuntu is installing or configuring software.

If the second Update run also fails or repeatedly stops at the same download, stop. Take a screenshot and include the relevant log from ~/it140/logs/ when asking for help. Do not attempt manual sudo, APT, package, or file repairs unless course support directs you to do so.

Protect Your Private Information

Before posting a screenshot, error message, log, or terminal output, check it for private information.

Do not post:

  • Passwords
  • Authentication or verification codes
  • GitHub personal access tokens
  • Recovery codes
  • Student identification numbers
  • Private contact information
  • Other credentials or secrets
  • Complete solutions to graded assignments

If you are unsure whether something is safe to share, ask your instructor before posting it publicly.

Using AI for Setup Troubleshooting

An AI assistant can help explain an error message, describe what a command does, or suggest a troubleshooting step. Give it specific information instead of only saying that something "doesn't work."

You can adapt this prompt:

I am setting up the IT 140 course IDE.

Environment: [Codio CVD / Windows / macOS / Linux]
Operating system and version: [if applicable]
Setup guide and step: [README section or numbered step]
Command or action I performed: [exact command/action]
Expected result: [what the instructions said should happen]
Actual result: [what happened]
Error message or script summary: [paste exact text]
Troubleshooting already attempted: [steps tried]

Explain what the error means in beginner-friendly language. Suggest one safe troubleshooting step at a time. Do not recommend deleting files, disabling security controls, bypassing administrator restrictions, or changing important system settings unless the official IT 140 setup instructions call for that change.

Review AI suggestions before running commands. If an AI tool tells you to delete files, disable security controls, change important system settings, or run a command you do not understand, stop and ask your instructor or technical support first.

Where Should I Ask?

Module One setup instruction or platform-specific problem

Use the Module One Setup Tasks repository for unclear setup instructions, failed setup commands, unexpected platform-script behavior, or a documented result that does not match what you see:

https://github.com/GC-STEM/it140-m1-setup-tasks

During testing or when directed by course staff, use its Issues tab for reproducible setup or documentation problems.

Course-wide automation or repository issue

Use the main IT 140 repository for course-wide automation or repository-status problems:

https://github.com/GC-STEM/it140

Question that may help other students

Use the IT 140 GitHub Discussions area or your course section's General Questions discussion, as directed by course instructions:

https://github.com/GC-STEM/it140/discussions

Before creating a new post, search for a distinctive part of the error message, script name, or application name. Follow solutions posted or confirmed by course faculty or technical support.

SNHU account, Brightspace, Codio access, or another university system

Use the SNHU IT Service Desk through Brightspace:

  1. Log in to the course site.
  2. Click the Help drop-down menu near the top right of the page.
  3. Click IT Service Desk.
  4. Click Ask for Technology Help.
  5. If the issue is time sensitive, click Chat Now or call the listed phone number.
  6. If the issue is not time sensitive, submit a support ticket.

Include the course, environment, setup step, exact error, and any safe screenshot or log that may help diagnose the problem. Your instructor can help determine whether a problem is related to course instructions or a university system.

Return to Setup

IT 140 Setup Tasks

Start Setup

Course Resources

Clone this wiki locally