Skip to content

Knowledgebase

Use command and configuration examples from our knowledgebase safely

development

Our technical guides include examples to explain a task. Before running one, confirm that it applies to your service, control panel and application version. An example hostname or directory is not a value to use unchanged on your own account.

01 Identify the environment and required permission

Check whether the instruction belongs in a local terminal, the hosting account's SSH session, a database console or an application configuration file. A root-level WHM command is not intended for a shared-hosting user. Stop and ask us when the required access or destination is unclear.

02 Replace placeholders deliberately

Look for values such as example.com, [database name] and /path/to/project. Replace only the intended fields with values from your own service. Keep passwords and tokens in the recommended private storage rather than pasting them into a public message.

Code or configuration example
# Example of a read-only request to your own public website:
curl -I https://www.example.com/

The command illustrates a request for response headers. Replace the hostname with your intended public site and understand what the command does before using it. Do not interpret a successful header response as proof that every website function works.

03 Preserve the command's characters

Copy code as plain text. Check that ordinary quotes, double hyphens, slashes and line breaks have not been changed by a word processor or messaging app. A typographic dash is not interchangeable with the two hyphens used by many command options.

Do not copy an explanatory shell prompt such as $ as part of the command unless the guide explicitly requires that character. Keep multi-line commands together only when the syntax expects it.

04 Plan verification and recovery

  1. Read the complete procedure before starting.
  2. Back up the data or configuration that will change.
  3. Test in staging when the action affects a live application.
  4. Run the intended command once and read its output.
  5. Verify the stated result before moving to the next step.

05 Questions we receive

Should I add force flags when a command fails?

No. Read the error and establish why the action was refused. A force option can remove a protection or change the scope of an operation.

What should I send our team?

Include the article title, intended task, command with secrets redacted, and exact error. Tell us whether any earlier step already changed files or data so we can guide the next action safely.

06 Official references and further reading

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support