• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

MS SQL password

V

valefar

Guest
I changed the password on the MS SQL sa password outside of Plesk. That was a mistake.

I went into Plesk to change the sa password that it uses to connect to MS SQL, but it asks for Old Password. Apparently I don't remember the old password correctly, and Plesk fails to update its sa password because of this.

I figure Plesk is actually trying to talk to MS SQL and change the sa password directly, hence it asking for the old password. So I tried putting in the current sa password (in SQL) as the Plesk old password, but it still fails to connect. I think it's still using the original sa password that I set up when I installed MS SQL.. the password that I cannot remember.

Is there a hidden Plesk utility to change what it "thinks" the old password is, or to straight-up change the sa password that it uses without having to supply the old password?

Until I resolve this, Plesk can't interface with my MS SQL and I have to do all database tasks manually outside of Plesk.
 
Answered my own question after doing some digging.

I had also changed the SQL port from the default 1433, and it was no longer responding to Plesk as localhost.

Had to tap into Plesk's mysql database and change the MSSQLServer parameter to localhost,port#. I was also able to manually change Plesk's idea of the sa password while I was in there.

Now Plesk is happy again.

Would be nice if this kind of stuff was documented. :)
 
Back
Top