• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question How to provide CLI Commands with spaces

Martin.B

Plesk Certified Professional
Plesk Certified Professional
Server operating system version
Ubuntu 22
Plesk version and microupdate number
Plesk Obsidian 18.0.53.2
Hi,
it seems like Plesk CLI Commands are unable to process space characters in Parameters.
For example:
Bash:
# plesk bin service_plan --info "Default Admin"
An error occurred while getting the hosting plan information: Unknown option 'Admin': /usr/local/psa/bin/service_plan --info Default Admin
I tried using double quotes, single quotes, Escaping with Backslash… The command always fails at the space.
The same happens with every cli command we tried.

Does anyone know of a way to provede the command with the correct names, which contain spaces?
 
Thanks for your reply. It really helped.

When I try to execute the command from the bash, which is started by ssh, I have this problem. When I start a new bash from within it works as it should.
I don't really understand why this happens, but now I can at least work correctly with the CLI.
 
Back
Top