• 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.

Input Prevent generating database passwords containing '#'

qf53

New Pleskian
Quick suggestion:

Would it be possible to prevent generating database passwords that contain '#'?
This causes errors in .env files because '#' is used to comment stuff out.
 
You should not deny any characters used for passwords. Instead you have to properly escape the characters where needed. You have to use quotes around the password in .env files for example.
 
You should not deny any characters used for passwords. Instead you have to properly escape the characters where needed. You have to use quotes around the password in .env files for example.
Which gets ugly when the password contains quotes. In-band signaling is nasty.
 
Back
Top