Context
• Application: Shopware 6.x Storefront
• Server: Ubuntu 22.04, aaPanel with Nginx + PHP 8.3 (PHP-FPM via socket)
• Domain: doitauto.de → root points to /www/wwwroot/doitauto.de/public
• SSL via Let’s Encrypt
The same Shopware installation works perfectly under Plesk, but under aaPanel we encounter problems with the Search / Suggest (AJAX) functionality.
⸻
Symptoms
• When using the storefront search field → error “Leider ist etwas schiefgelaufen” (“Something went wrong”).
• Direct test with curl:
curl -v -H 'X-Requested-With: XMLHttpRequest' \
'https://doitauto.de/suggest?search=test'
→ Response: HTTP/2 404
→ Error originates from Shopware (Symfony 404), not Nginx:
<div class="alert alert-danger">
Leider ist etwas schiefgelaufen
</div>
• Router test inside Shopware:
bin/console router:match '/suggest' --method=GET --host=doitauto.de --scheme=https
→ Matches correctly: frontend.search.suggest
• Store-API test:
curl -v -H 'Content-Type: application/json' \
-H 'sw-access-key: <AccessKey>' \
--data-binary '{"search":"test"}' \
'https://doitauto.de/store-api/search-suggest'
→ Returns 405 Method Not Allowed (“GET received, POST expected”),
although POST is being sent.
→ This only happens under aaPanel, not under Plesk.
⸻
Current aaPanel Nginx configuration
server {
listen 80;
listen 443 ssl http2;
server_name doitauto.de www.doitauto.de;
root /www/wwwroot/doitauto.de/public;
index index.php;
location / {
try_files $uri /index.php$is_args$args;
}
location ^~ /store-api {
try_files $uri /index.php$is_args$args;
}
include enable-php-83.conf;
}
• All @rewrite and rewrite ^ /index.php last; directives were removed (to avoid POST → GET conversion).
• Still, /suggest returns 404 and /store-api/search-suggest returns 405.
⸻
Working Plesk Nginx configuration (for comparison)
server {
listen 80;
listen 443 ssl http2;
server_name doitauto.de www.doitauto.de;
root /var/www/vhosts/doitauto.de/httpdocs/public;
index index.php;
location / {
try_files $uri /index.php$is_args$args;
}
location ^~ /store-api {
try_files $uri /index.php$is_args$args;
}
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/run/php/php8.3-fpm.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
}
}
Under Plesk this configuration works flawlessly, Search and Suggest return 200 OK.
⸻
Question to aaPanel team / community
• Why does this issue only occur under aaPanel, but not under Plesk with the same Shopware setup?
• Does aaPanel add extra rewrite/include snippets that affect POST requests or Ajax routes (/suggest, /store-api/search-suggest)?
• Are there specific adjustments required in aaPanel for Shopware 6, so that all POST requests reach index.php without being converted into GET?
• Expected behavior:
• POST requests must remain POST when forwarded to PHP.
• /suggest should not return 404 if the Shopware router has the route enabled.
• /store-api/search-suggest should accept POST requests as defined in Shopware.
👉 With this report you show clearly: same Shopware, same version → works under Plesk, fails under aaPanel.
This should help aaPanel support identify if their rewrite templates or panel-generated Nginx configs need adjustment.
