• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Panel Admin Website offline 403 Error

J

JonathanDa

Guest
Hi everyone,
i case of a right change on my Server of the folder /opt/psa i cannot get on the admin Website of Plesk Panel. i reconfigure some rights but it seems not all, because i get the 403 - FORBIDDEN Error Message.

Code: 
~# /etc/init.d/psa start
Starting psa...                                                       done
Starting xinetd service...                                            done
Starting bind9 service...                                             done
Starting mysql service...                                             done
Starting postgresql service...                                        not installed
Starting psa-spamassassin service...                                  not installed
Plesk: Starting Mail Server... already started
WARNING:
cannot parse ipcs output
Starting mail handlers tmpfs storage
Starting psa...                                                       done
Starting drwebd service...                                            failed
psa is running. i can get access to my imap mail accounts and to the domain websites.

Code: 
~# /etc/init.d/drwebd restart
Restarting Dr. Web daemon...
Dr.Web (R) daemon for Linux/Plesk Edition v5.0.0 (Jun  4 2009)
Copyright (c) Igor Daniloff, 1992-2009
Doctor Web, Moscow, Russia
Support service: http://support.drweb.com
To purchase: http://buy.drweb.com
Shell version: 5.0.0.10060 <API:2.2>
Engine version: 5.0.0.12182 <API:2.2>
Loading /var/drweb/bases/drwtoday.vdb - Ok, virus records: 52
Loading /var/drweb/bases/drw50029.vdb - Ok, virus records: 2691
Loading /var/drweb/bases/drw50028.vdb - Ok, virus records: 3327
Loading /var/drweb/bases/drw50027.vdb - Ok, virus records: 4697
Loading /var/drweb/bases/drw50026.vdb - Ok, virus records: 2792
Loading /var/drweb/bases/drw50025.vdb - Ok, virus records: 5841
Loading /var/drweb/bases/drw50024.vdb - Ok, virus records: 2260
Loading /var/drweb/bases/drw50023.vdb - Ok, virus records: 4796
Loading /var/drweb/bases/drw50022.vdb - Ok, virus records: 5098
Loading /var/drweb/bases/drw50021.vdb - Ok, virus records: 4891
Loading /var/drweb/bases/drw50020.vdb - Ok, virus records: 5033
Loading /var/drweb/bases/drw50019.vdb - Ok, virus records: 3254
Loading /var/drweb/bases/drw50018.vdb - Ok, virus records: 5241
Loading /var/drweb/bases/drw50017.vdb - Ok, virus records: 7585
Loading /var/drweb/bases/drw50016.vdb - Ok, virus records: 5298
Loading /var/drweb/bases/drw50015.vdb - Ok, virus records: 5947
Loading /var/drweb/bases/drw50014.vdb - Ok, virus records: 6039
Loading /var/drweb/bases/drw50013.vdb - Ok, virus records: 5309
Loading /var/drweb/bases/drw50012.vdb - Ok, virus records: 3511
Loading /var/drweb/bases/drw50011.vdb - Ok, virus records: 2495
Loading /var/drweb/bases/drw50010.vdb - Ok, virus records: 4565
Loading /var/drweb/bases/drw50009.vdb - Ok, virus records: 4467
Loading /var/drweb/bases/drw50008.vdb - Ok, virus records: 5196
Loading /var/drweb/bases/drw50007.vdb - Ok, virus records: 2359
Loading /var/drweb/bases/drw50006.vdb - Ok, virus records: 1938
Loading /var/drweb/bases/drw50005.vdb - Ok, virus records: 3335
Loading /var/drweb/bases/drw50004.vdb - Ok, virus records: 3185
Loading /var/drweb/bases/drw50003.vdb - Ok, virus records: 1468
Loading /var/drweb/bases/drw50002.vdb - Ok, virus records: 280
Loading /var/drweb/bases/drw50001.vdb - Ok, virus records: 567
Loading /var/drweb/bases/drw50000.vdb - Ok, virus records: 1194
Loading /var/drweb/bases/drwebase.vdb - Ok, virus records: 423328
Loading /var/drweb/bases/dwrtoday.vdb - Ok, virus records: 491
Loading /var/drweb/bases/dwr50001.vdb - Ok, virus records: 626
Loading /var/drweb/bases/dwntoday.vdb - Ok, virus records: 478
Loading /var/drweb/bases/dwn50002.vdb - Ok, virus records: 925
Loading /var/drweb/bases/dwn50001.vdb - Ok, virus records: 840
Loading /var/drweb/bases/drwrisky.vdb - Ok, virus records: 3316
Loading /var/drweb/bases/drwnasty.vdb - Ok, virus records: 19303
Total virus records: 564018
Key file: /opt/drweb/drweb32.key - Key file was not found! (No such file or directory)
A path to a valid license key file was not specified.
Plesk authorization failed: malformed response (no 'response=' field).
Error: Plesk Software not running.

i had no problems before this fault.

Code: 
~# /usr/local/psa/bin/service --restart drweb
drwebmng: Service /etc/init.d/drwebd failed to start

System error 2: No such file or directory
/opt/psa/admin/bin/drwebmng[7805]: Unable to start drweb antivirus daemon
Error report was sent successfully
Report body:
<?xml version="1.0"?>
<error><type>PleskUtilException</type><message>/opt/psa/admin/bin/drwebmng '--re                               start' failed with message: drwebmng: Service /etc/init.d/drwebd failed to start

System error 2: No such file or directory</message><file>/opt/psa/admin/plib/com                               mon_func.php3</file><line>1050</line><code>0</code><trace>#0 /opt/psa/admin/plib                               /class.ServiceControl.php(442): util_exec('drwebmng', Array)
#1 /opt/psa/admin/plib/api-common/cuService.php(169): ServiceControl-&gt;action(                               )
#2 /opt/psa/admin/plib/api-common/cuService.php(91): cuService-&gt;executeServic                               eAction('drweb', 'restart')
#3 /opt/psa/admin/plib/api-common/cuService.php(73): cuService-&gt;manageService                               ('restart', 'drweb')
#4 /opt/psa/admin/plib/api-common/AbstractCuExecutor.php(26): cuService-&gt;exec                               ute()
#5 /opt/psa/admin/plib/api-common/CuExecutor.php(29): AbstractCuExecutor-&gt;_ex                               ecUtil('cuService', 'execute')
#6 /opt/psa/admin/plib/api-cli/CliUtilityRunner.php(18): CuExecutor-&gt;run()
#7 /opt/psa/admin/plib/api-cli/CliUtilityRunner.php(43): CliUtilityRunner-&gt;ru                               n()
#8 /opt/psa/admin/plib/api-cli/service.php(4): require_once('/opt/psa/admin/...'                               )
#9 {main}</trace><user-ip/><host/><request-url/><request-method/><product-versio                               n>10.3.1 Debian 6.0 1013110726.09
</product-version></error>

Unable to create ServiceControl object: Unable to manage service by drwebmng: dr                               webmng: Service /etc/init.d/drwebd failed to start

System error 2: No such file or directory ('--restart', 'drweb')
he give me these messages and i dont know, how to fix it. is there a possibillity to delete the enabled drweb config without loosing mail accounts and domains.

hope for help, thanks
 
After rebuilding the permission denied parts, I got this with bootstrapper.sh repair.

Code: 
# /usr/local/psa/bootstrapper/pp10.12.0-bootstrapper/bootstrapper.sh repair
===> Preparing upgrade
Stopping psa...                                                       done
Stopping mail handlers tmpfs storage
psa is stopped
Stopping psa...                                                       done
Stopping mail handlers tmpfs storage
===> 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 'K01psa-firewall' missing LSB tags and overrides
insserv: warning: script 'psa-firewall-forward' missing LSB tags and overrides
insserv: warning: script 'psa-firewall' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'K01drwebd' missing LSB tags and overrides
insserv: warning: script 'K01psa-firewall' missing LSB tags and overrides
insserv: warning: script 'psa-firewall-forward' missing LSB tags and overrides
insserv: warning: script 'psa-firewall' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
Module ssl 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 'K01psa-firewall' missing LSB tags and overrides
insserv: warning: script 'psa-firewall-forward' missing LSB tags and overrides
insserv: warning: script 'psa-firewall' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
Stopping psa...                                                       done
Stopping mail handlers tmpfs storage
Starting psa...                                                       done
Starting xinetd service...                                            done
Starting bind9 service...                                             done
Starting mysql service...                                             done
Starting postgresql service...                                        not installed
Starting psa-spamassassin service...                                  not installed
Plesk: Starting Mail Server... already started
Starting mail handlers tmpfs storage
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:
        https://******:8443/ or
        https://******:8443/
        Use 'admin' and '<YOUR ADMIN PASSWORD>' as login name and password.

        Further, use the following commands to start and stop the system:
        /etc/init.d/psa start and
        /etc/init.d/psa stop respectively.

Did I miss permissions of files?
 
Do you still have 403 Error? If yes - what sort of errors in /var/log/sw-cp-server/error_log ?
 
Code: 
2011-10-20 21:50:00: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure 
2011-10-20 23:35:36: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure 
2011-10-21 02:42:37: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure 
2011-10-21 04:15:52: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure 
2011-10-21 07:34:51: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure 
2011-10-21 08:57:23: (connections.c.299) SSL: 1 error:140780E5:SSL routines:SSL23_READ:ssl handshake failure 
2011-10-21 10:14:38: (log.c.135) server stopped 
2011-10-21 10:15:06: (log.c.75) server started 
2011-10-21 10:15:46: (log.c.135) server stopped 
all children busy, launch additional (total 3, limit 30)
2011-10-21 10:16:13: (log.c.75) server started 
all children busy, launch additional (total 3, limit 30)
2011-10-21 10:25:17: (log.c.135) server stopped 
2011-10-21 10:33:33: (log.c.75) server started 
all children busy, launch additional (total 3, limit 30)
2011-10-21 10:37:47: (log.c.135) server stopped 
2011-10-21 10:38:13: (log.c.75) server started 
2011-10-21 10:38:59: (log.c.135) server stopped 
all children busy, launch additional (total 3, limit 30)
2011-10-21 10:39:26: (log.c.75) server started 
all children busy, launch additional (total 3, limit 30)
2011-10-21 10:51:13: (log.c.135) server stopped 
2011-10-21 10:51:35: (log.c.75) server started 
all children busy, launch additional (total 3, limit 30)


My Mail Server has problem 2. I cannot send e-mails.
 
Last edited by a moderator:
cannot use the code for iptables of the link in iptables version v1.4.8. got the message:
Code: 
iptables v1.4.8: option `SSH' requires an argument
Try `iptables -h' or 'iptables --help' for more information.
 
Code: 
sshd: <admin IP address>/<netmask> : allow
sshd: ALL : deny
should i do this with a non-static ip address?

still cannot send emails, mail server is very slow and the admin plattform ist still on 403 - Forbidden error.
did the bootstrapper repair at once with the same result:
Code: 
# /usr/local/psa/bootstrapper/pp10.12.0-bootstrapper/bootstrapper                        .sh repair
===> Preparing upgrade
Stopping psa...                                                      done
Stopping mail handlers tmpfs storage
psa is stopped
Stopping psa...                                                      done
Stopping mail handlers tmpfs storage
===> 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 'K01psa-firewall' missing LSB tags and overrides
insserv: warning: script 'psa-firewall-forward' missing LSB tags and overrides
insserv: warning: script 'psa-firewall' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'K01drwebd' missing LSB tags and overrides
insserv: warning: script 'K01psa-firewall' missing LSB tags and overrides
insserv: warning: script 'psa-firewall-forward' missing LSB tags and overrides
insserv: warning: script 'psa-firewall' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
Module ssl 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 De                        fault-Start values (2 3 5)
insserv: warning: script 'K01drwebd' missing LSB tags and overrides
insserv: warning: script 'K01psa-firewall' missing LSB tags and overrides
insserv: warning: script 'psa-firewall-forward' missing LSB tags and overrides
insserv: warning: script 'psa-firewall' missing LSB tags and overrides
insserv: warning: script 'drwebd' missing LSB tags and overrides
Stopping psa...                                                      done
Stopping mail handlers tmpfs storage
Starting psa...                                                      done
Starting xinetd service...                                           done
Starting bind9 service...                                            done
Starting mysql service...                                            done
Starting postgresql service...                                       not install                        ed
Starting psa-spamassassin service...                                 not install                        ed
Plesk: Starting Mail Server... already started
Starting mail handlers tmpfs storage
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:
        https://h1957256.stratoserver.net:8443/ or
        https://85.214.246.133:8443/
        Use 'admin' and '<YOUR ADMIN PASSWORD>' as login name and password.

        Further, use the following commands to start and stop the system:
        /etc/init.d/psa start and
        /etc/init.d/psa stop respectively.

do i have to reinstall? if yes, can i save my domain and mail data for import after reinstall?
 
Last edited by a moderator:
You must log in or register to reply here.

Similar threads

T
Issue ERROR: Dr.Web Updater: Nothing to update !
Replies
6
Views
774
TimRear
T
S
Issue Getting 404 Not Found NGINX error, not able to access plesk and website went down after update
Replies
2
Views
792
Dave W
Dave W
S
Issue Plesk admin panel not accessible
Replies
0
Views
73
solutionsnewtown
S
O
Resolved Service Plesk Premium Antivirus not running
Replies
4
Views
1K
othmaqsa
O
M
Issue Plesk Update 18.0.34 to 18.0.57 Database 'psa' not found
Replies
10
Views
812
musa.sc
M
Back
Top