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

Unable to login after installing Customer & Business Manager

Silvercn

New Pleskian
Hi guys,

Im using Debian squeeze.
All works fine, but after installing the customer & business manager. Im not able to login to plesk-billing even the normal way to sso.
So after installing the business manager, plesk showed up to complete the registration in dashboard...so i did, after that it told me to authentificate with plesk, but that failed every time. I logged out from plesk, and wanted to relogin, but now it says "Error: Authentication failed: invalid username or password specified".
I got an similar error when i was trying to login into the container. But found out that chrome cant handle it right way. So i used Firefox to prevent the problem. But Chrome issnt the Problem about the new Problem...

I found a way to fix that, but didnt used it, cause its for Plesk 10.
Link: http://kb.parallels.com/en/9509
Can i use that to resolve the Problem, or any other solution to fix that?

Thanks
 
AFAIK there is no differences and you can try this method.
 
Getting error message, should i force te command?

"/usr/share/plesk-billing/sso --command=detach --app-type=admin
The 'sso' utility was failed with the unknown message: <message>Server error (code 500): Exception with message 'SQLSTATE[HY000]: General error: 14 unable to open database file' caught at top level. (HTTP code: 500)</message>. All details of the problem has been stored into the '/usr/share/plesk-billing/sso.crash.log' file.
You can try start the 'detach' command with the '--force' option to ignore errors."
 
What about bootstrapper repair procedure? Have you tried it?
 
Try to use forum search engine. It was mentioned here a lot of times.
 
Hi there,

using the command "/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair"

atleast this came out:

===> Preparing upgrade
Stopping psa... done
psa is stopped
Stopping psa... done
===> Cumulative database upgrade has been started
===> Upgrade completed.
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'K01drwebd' missing LSB tags and overrides
insserv: warning: script 'kavehost' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
insserv: script vzquota: service vzreboot already provided!
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'K01drwebd' missing LSB tags and overrides
insserv: warning: script 'kavehost' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
insserv: script vzquota: service vzreboot already provided!
Module ssl already enabled
Module headers already enabled
ln: creating symbolic link `/var/named/run-root/etc/bind/rndc.conf': File exists
update-rc.d: using dependency based boot sequencing
update-rc.d: error: unable to read /etc/init.d/named
mknod: `/var/www/vhosts/chroot/dev/null': File exists
Module suexec already enabled
Module include already enabled
Module rewrite already enabled
Module userdir already enabled
===> Cumulative upgrade has been started
===> Upgrade completed.
Module dav already enabled
Considering dependency dav for dav_fs:
Module dav already enabled
Module dav_fs already enabled
Module auth_digest already enabled
Module authz_user already enabled
Module dav_lock already enabled
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: psa start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (2 3 5)
insserv: warning: script 'K01drwebd' missing LSB tags and overrides
insserv: warning: script 'kavehost' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
insserv: script vzquota: service vzreboot already provided!
Stopping psa... done
Starting xinetd service... done
Starting mysql service... done
Starting bind9 service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
Starting psa... done
Starting drwebd service... failed

Congratulations!
All stages of the upgrade were successful.
psa is now running on your system.
To complete the system configuration process, please proceed to URL:"

Howerver, now i got to my Plesk Site and there is no login anymore just a written text on a white Page.

"Server error (code 500): Exception with message 'SQLSTATE[HY000]: General error: 14 unable to open database file' caught at top level."

So... what should i do next? The bootstrapper repair takes me to nothing just more trouble.

Edit: I just read a bit forward, and used "/usr/local/psa/bin/sso --disable"
That disable the sso and im able to login in normal Plesk. Anyway that doesnt fix it at all, but iam able to login in normal Plesk.

But if you find a workaround to get billing working let me know.!
 
Last edited:
Back
Top