Jump to content

Erreur 403 FileManager prestashop


Galko

Recommended Posts

Bonjour,

J'ai un petit problème avec mon prestashop hébergé sur un serveur plesk.

Lorsque je tente d'ouvrir le gestionnaire de fichier j'ai une erreur 403 me disant que je n'ai pas le droit de faire ça.

Voici l'erreur que j'ai dans ma console qui correspond à l'ouverture de ce dernier

VM1967:2  GET https://www.xxxx.com/xxxx/filemanager/dialog.php?type=1&descending=false&sort_by=&lang=fr 403 (Forbidden)

J'ai creative element dans ce site et pareil je ne peux pas ouvrir ma bibliothèque d'image.

Voici mes tentatives :

Placer ce code dans les Additional Apache directives du conteneur du site internet (toujours 403):

<Directory "/var/www/vhosts/xxxxx.com/httpdocs/xxxx/filemanager">
    AllowOverride All
    Require all granted
</Directory>

Changer les permissions des fichiers php dans filemanger (voir capture d'écran) (toujours 403)

J'ai vérifier le htaccess et il semble conforme à l'original.

Et le mobsecurity du plesk n'est pas activé ...

 

Une solution ? 

 

This is translated for english people i can answer in english if needed :

 

Hello,

I have a small problem with my prestashop hosted on a plesk server.

When I try to open the file manager I get a 403 error telling me that I'm not allowed to do that.

Here's the error I get in my console when I try to open it: 

VM1967:2 GET https://www.xxxx.com/xxxx/filemanager/dialog.php?type=1&descending=false&sort_by=&lang=fr 403 (Forbidden)

I have creative element in this site and I can't open my image library.

Here are my attempts:

Place this code in the Additional Apache directives of the website container (always 403):

<Directory “/var/www/vhosts/xxxxx.com/httpdocs/xxxx/filemanager”>
    AllowOverride All
    Require all granted
</Directory>

Change php file permissions in filemanger (see screenshot) (always 403)

I've checked the htaccess and it seems to conform to the original.

And the plesk mobsecurity is not activated ...

Any solution? 

Translated with DeepL.com (free version)

 

 

screen_1.png

capture.png

total.png

Edited by Galko (see edit history)
Link to comment
Share on other sites

Bonjour Voici le .htaccess 

 

# Use the front controller as index file. It serves as a fallback solution when
# every other rewrite/redirect fails (e.g. in an aliased environment without
# mod_rewrite). Additionally, this reduces the matching process for the
# start page (path "/") because otherwise Apache will apply the rewriting rules
# to each configured DirectoryIndex file (e.g. index.php, index.html, index.pl).
DirectoryIndex index.php

# By default, Apache does not evaluate symbolic links if you did not enable this
# feature in your server configuration. Uncomment the following line if you
# install assets as symlinks or if you experience problems related to symlinks
# when compiling LESS/Sass/CoffeScript assets.
# Options FollowSymlinks

# Disabling MultiViews prevents unwanted negotiation, e.g. "/app" should not resolve
# to the front controller "/app.php" but be rewritten to "/app.php/app".
<IfModule mod_negotiation.c>
    Options -MultiViews
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On
    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Keep legacy entry points
    RewriteRule ^(ajax|ajax_products_list|ajax-tab|backup|cron_currency_rates)\.php - [P]
    RewriteRule ^(displayImage|drawer|footer\.inc|functions|get-file-admin)\.php - [P]
    RewriteRule ^(grider|header\.inc|init|login|password|pdf|searchcron)\.php - [P]

    # If the URL is a legacy on index.php?controller=..., do not rewrite (let the legacy take it)
    RewriteCond  %{QUERY_STRING} (^|&)controller=|(^|&)tab=
    RewriteRule .* - [P]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the start page because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    #   following RewriteCond (best solution)
    # RewriteCond %{ENV:REDIRECT_STATUS} ^$
    # RewriteRule ^index\.php(/(.*)) %{ENV:BASE}/$2 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule .? - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule .? %{ENV:BASE}/index.php [L]
</IfModule>

<IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
        # When mod_rewrite is not available, we instruct a temporary redirect of
        # the start page to the front controller explicitly so that the website
        # and the generated links can still be used.
        RedirectMatch 302 ^/$ /index.php/
        # RedirectTemp cannot be used instead
    </IfModule>
</IfModule>

Je ne vois pas de restriction à ce niveau après je me trompe peut être...

Bien à vous

Link to comment
Share on other sites

1 minute ago, Prestashop Addict said:

Le filemanager est appelé depuis une page cms ?

Depuis une page CMS ou Creative Element c'est pareil j'ai la même erreur 403

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...