On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at Plesk 360 (formerly known as My Plesk) please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

Errors 404 on websites for some JS, CSS, images and PHP files.

Avatar
Miguel Monteiro
Updated
Follow
kb: bug ABT: Group A Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux

Symptoms

  • When browsing the website example.com, errors like the following are shown in the web browser console:

    CONFIG_TEXT: The script from “https://example.com/wp-includes/js/wp-embed.min.js?ver=5.4” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.[Learn More]example.com
    Loading failed for the <script> with source “https://example.com/wp-includes/js/wp-embed.min.js?ver=5.4”.

  • In Network tab, few css or js show 404 error.

  • Some specific pages show File not Found​, EG: example.com/wp-admin/profile.php​.

  • Sometime the following is added at the end of the website address: /login_up.php?success_redirect_url=https%3A%2F%2Fexample.com%2F

  • Some requests made by Apache user (apache, apache2 or www-data) to the port 8880 used by Plesk web server are not closed:

    # lsof -i:8880
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    sw-cp-ser 1166 sw-cp-server 10u IPv4 126087305 0t0 TCP *:8880 (LISTEN)
    sw-cp-ser 1166 sw-cp-server 12u IPv6 126087307 0t0 TCP *:8880 (LISTEN)
    sw-cp-ser 1166 sw-cp-server 14u IPv4 142261273 0t0 TCP localhost.localdomain:8880->localhost.localdomain:33744 (ESTABLISHED)
    sw-cp-ser 1166 sw-cp-server 19u IPv4 142259627 0t0 TCP localhost.localdomain:8880->localhost.localdomain:33238 (ESTABLISHED)
    apache2 11707 www-data 129u IPv4 141850850 0t0 TCP localhost.localdomain:34678->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 130u IPv4 141849230 0t0 TCP localhost.localdomain:34306->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 131u IPv4 141849229 0t0 TCP localhost.localdomain:34304->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 132u IPv4 141850851 0t0 TCP localhost.localdomain:34680->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 133u IPv4 141850849 0t0 TCP localhost.localdomain:34676->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 134u IPv4 141850852 0t0 TCP localhost.localdomain:34682->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 135u IPv4 142243627 0t0 TCP localhost.localdomain:57594->localhost.localdomain:8880 (CLOSE_WAIT)
    apache2 11707 www-data 136u IPv4 136298003 0t0 TCP localhost.localdomain:53848->localhost.localdomain:8880 (CLOSE_WAIT)​
    sw-cp-ser 15166 root 10u IPv4 126087305 0t0 TCP *:8880 (LISTEN)
    sw-cp-ser 15166 root 12u IPv6 126087307 0t0 TCP *:8880 (LISTEN)
    simple-js 27964 grafana 1u IPv4 142259626 0t0 TCP localhost.localdomain:33238->localhost.localdomain:8880 (ESTABLISHED)
    simple-js 27964 grafana 3u IPv4 142260968 0t0 TCP localhost.localdomain:33744->localhost.localdomain:8880 (ESTABLISHED)

Cause

Bug in Plesk with ID #PPP-50362 which will be fixed in one of the future updates of Plesk.

Resolution

Until the bug is not fixed, apply the following solution:

  1. Connect to the server via SSH.

  2. Verify the integrity of Apache configuration:

    • On CentOS/CloudLinux/RedHat servers:

      # httpd -t
      Syntax OK

    • On Debian/Ubuntu servers:

      # apachectl -t
      Syntax OK

  3. If the configuration is fine, restart Apache:

    • On CentOS/CloudLinux/RedHat servers:

      # systemctl restart httpd

    • On Debian/Ubuntu servers:

      # systemctl restart apache2

Comments

1 comment

Sort by Date Votes

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles