• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved website getting no error and maintenance

Hajime Tanaka

Regular Pleskian
Server operating system version
AlmaLinux 8.7 x86_64
Plesk version and microupdate number
18.0.47.5
If I just upload the website of stuff, that would not recognize from 403 or 404, 503 error documents, because that kept getting the show just maintenance only, is there a way to remove this annoying?

Screenshot:
 
@IgorG @maartenv , okay I have confirmed whether this is a bug known as possible or not.

I've followed this but apache2 is replaced by httpd following: Developer Portal

I followed this everything and here,

1. sudo yum install httpd -y was already resolved and installed default by AlmaLinux enabled.

2. /etc/httpd/conf.modules.d/00-base.conf: `LoadModule rewrite_module modules/mod_rewrite.so` was already there existed and default by AlmaLinux enabled.

3. /etc/httpd/conf/httpd.conf, found this for AllowOverride None and I've changed all from None to All
Before:

Code:
<Directory />
    AllowOverride none
    Require all denied
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
    AllowOverride None
    # Allow open access:
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
    #
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    #
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    #
    # The Options directive is both complicated and important.  Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    #
    Options Indexes FollowSymLinks

    #
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    #
    AllowOverride None

    #
    # Controls who can get stuff from this server.
    #
    Require all granted
</Directory>


After:
Code:
<Directory />
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html"

#
# Relax access to content within /var/www.
#
<Directory "/var/www">
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>

# Further relax access to the default document root:
<Directory "/var/www/html">
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted
</Directory>
Then I restarted the httpd and PHP FPM services.

Still the same issue.

So I've decided to follow this https://support.plesk.com/hc/en-us/...nable-Apache-or-Nginx-rewrite-rules-in-Plesk-

Added to Additional Apache directives from Plesk.
Code:
RewriteEngine on
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

Then I restarted the httpd and PHP FPM services same time again.

It's still the same issue on the Plesk Site Maintenace page. That is caused by Almalinux is unlikely to change and is different from CentOS or Plesk might be bugged.
 
Back
Top