Skip to content

Common Issues

Quick solutions to problems that come up frequently. Click any item to expand it.

I can't log in

There are a few things to check:

  • Verify your username. Usernames are case-sensitive. Make sure you are typing it exactly as your administrator set it up.
  • Check if your account is enabled. Your administrator may have disabled your account. Contact them to confirm your account is active.
  • Wait a few seconds and try again. Campus WoL uses rate limiting to protect against brute-force attacks. If you have made several failed attempts in a short period, the system temporarily slows down responses. Wait a few seconds for the token bucket to refill, then try again.
I don't see a classroom or site

Your account may be site-scoped, meaning it is restricted to specific sites. Site scoping is a security feature that limits what each user can see and manage.

If you expect to see a site or classroom that is not appearing, contact your administrator. They can check your site assignments and adjust them if needed.

Permission denied on an action

Your current role does not have permission to perform that action. Campus WoL uses RBAC (role-based access control) with three roles: Viewer, Operator, and Admin. Each role has a specific set of allowed actions.

See Role-Based Access Control for the full permissions matrix showing what each role can do. If you need elevated access, ask your administrator to adjust your role.

Discovery scan returns no results

Discovery scans only find devices that are powered on and connected to the network. A device that is shut down does not respond to network probes, so it will not appear in scan results.

If you are scanning and getting no results:

  • Check the target VLAN. Make sure the scan is targeting the correct network segment for the classroom.
  • Verify devices are powered on. At least some devices in the target VLAN must be on for the scan to return results.
  • Check the scan-agent. If the scan-agent is offline, scans will silently fail. See Agent Health to verify its status.
Schedule didn't run

If a scheduled wake or scan did not execute at the expected time:

  • Check if the schedule is enabled. Each schedule has an enable/disable toggle. If the toggle is off, the schedule will not run regardless of its cron expression.
  • Check agent health. Schedules that trigger wake operations depend on the wol-agent. Schedules that trigger scans depend on the scan-agent. If the required agent is offline, the schedule will fail. See Agent Health.
  • Review execution history. Open the schedule and check its execution history for error details. The history shows whether the schedule was triggered, whether it succeeded or failed, and any error messages returned.