Skip to Content
Browse documentation

Manage Shell Access in WAP

Choose Bash, Eenos jail shell or No Shell for hosting accounts with single and bulk controls, and verify actual SSH access separately.

Open Hosting → User Accounts → Manage Shell Access to select the shell environment for hosting accounts. The table lists active accounts with selection checkboxes, User, Domain, Current Shell and Action, plus search and pagination.

Requirements and choices

Use authenticated administrator WAP access over HTTPS with JavaScript enabled. Demo sessions cannot apply changes. Confirm the account identity, intended access requirement and current shell before granting more access.

ChoiceAccepted shellMeaning
Bash Shell/usr/bin/bashStandard interactive shell; grant only to trusted users.
Jail Shell/usr/local/eenos/bin/jailshellEenos restricted shell environment.
No Shell/usr/sbin/nologinDisable interactive shell access through this shell setting.

The server accepts only these supported shell paths. The selector is not a free-text command field. Shell choice does not configure SSH keys, reset passwords, open firewall ports or install/start SSH.

Shell access is a security-sensitive privilege

Choose the least access needed. Jail shell is not a guarantee of complete tenant isolation, and No Shell is not proof that every possible file-transfer/session path is disabled. SSH/SFTP behavior also depends on authentication, SSH configuration and any forced subsystem policy.

Change one account

Select Change Shell on its row. The dialog shows Hosting Account, Domain, Current shell and radio choices for Bash Shell, Jail Shell and No Shell. Select the intended choice, then Change Shell, or cancel.

The current shell initializes the choice when recognized. Review the selection explicitly for an unknown/unexpected current value. Reload after the result and verify both panel shell status and actual authorized login behavior as appropriate.

Bulk controls

The top controls are Enable Bash for Selected, Enable Jail Shell for Selected and Disable Shell for Selected.

  1. Select intended active accounts.
  2. Choose the appropriate bulk shell action.
  3. Review New shell setting and every Selected accounts username in Change Shell for Multiple Accounts.
  4. Select Change Shell, or cancel.
  5. Verify every account individually.

The header checkbox selects current-page rows; accumulated selections persist across pagination/redraws. No selection displays Select at least one account before changing shell access. The same shell applies to every submitted account.

Effects, errors and recovery

The helpers update account shell metadata and invoke operating-system shell changes, recording account audit events. Metadata and operating-system changes are separate effects; a saved label or aggregate bulk result does not independently verify every actual login shell.

This shell is not supported, missing-account or form errors require a supported choice and existing account. Unable-to-change and multiple-shell-change failures require reviewing account state and server logs before retrying. Do not assume every earlier account succeeded just because a bulk message reports success.

Record previous shells before changing a group. To reverse a change, apply each account's intended previous supported shell and verify it. Revoking shell access here is not a documented terminate-all-existing-sessions operation.

Do’s and don’ts

  • Do review the privilege increase before selecting Bash.
  • Do verify both configured shell and intended access after changes.
  • Do restore accounts individually when their previous shell choices differed.
  • Do not treat shell selection as a password/key/firewall manager.
  • Do not use bulk Bash access as a general troubleshooting step.

Previous: Change Ownership. All twelve User Accounts menus now have guides. Next sidebar group: Hosting → Resellers.