• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Next level web

New Pleskian
Server operating system version
AlmaLinux 8.7 (Stone Smilodon)
Plesk version and microupdate number
Plesk Obsidian Version 18.0.58 Update #2
We have a dedicated Plesk server. Recently, we migrated a multisite to our server, which already hosted another multisite. When attempting to log in to the wp-admin of the newly migrated multisite, we're redirected to the login page of the other multisite on our server.

I came across an article (WordPress multisite redirect loop - Our tricks to solve the error) and applied the suggested code to the wp-config file, but it didn't resolve the issue.

I've searched through files and the database for any incorrect URLs or redirection rules but haven't found anything amiss.

The only anomaly is within the Plesk WordPress Toolkit, which displays the incorrect website name, although the domain settings appear normal. I tried to update the website url in WP toolkit but it says completed. But does not help.

We're experiencing this issue with the following site: Frentzo.com/nl/wp-admin

What could be the cause?
 
- An entry in the wp-config.php file might define the homepage or the siteurl incorrectly.
- The home or siteurl datasets in your *_options table might contain the wrong URL.
- An .htaccess file redirect entry might point to the wrong URL.
- The site contains a caching plugin so that the cached page redirects to the wrong URL.
 
- An entry in the wp-config.php file might define the homepage or the siteurl incorrectly.
- The home or siteurl datasets in your *_options table might contain the wrong URL.
- An .htaccess file redirect entry might point to the wrong URL.
- The site contains a caching plugin so that the cached page redirects to the wrong URL.
The last point could be the issue. The other things I already checked. It is maybe server issue?
 
Does someone has a solution? We reinstalled the multisite on our server. In the beginning it was working fine. Now it is redirecting again but to a differant multsite on our server an other one than it was redirecting.
 
Some addional information we still have problems.

We have recently been experiencing issues with our multisite setups on our Plesk server; they are incorrectly redirecting to each other. Additionally, the WP-toolkit in Plesk is displaying incorrect names for the multisite settings.

Initially, we had the multisite 1 with five sub-websites on the server, which always worked without any issues. We have recently added two other multisites: # and #
# functioned correctly for several weeks but then started to redirect to #. After reinstalling the multisite,# began redirecting to #. # is now also redirecting to #. The WP-toolkit also incorrectly shows # as the name for these sites.

The site # was transferred using the All-in-One Migration plugin, # was created manually, and # was already existing and previously functioned well.

The multisites now seem not to be functioning correctly, only showing cached versions.

We have added the following definitions to the wp-config.php file:

phpCopy code
define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');

In addition, we have added the following lines to the Nginx additional configuration:

nginxCopy code
rewrite ^/([_0-9a-zA-Z-]+)/wp-admin$ /$1/wp-admin/index.php;
rewrite ^/([_0-9a-zA-Z-]+)/wp-admin/$ /$1/wp-admin/index.php;
rewrite ^/([_0-9a-zA-Z-]+)/((wp-(?:content|includes|admin)).*)$ /$2 break;
if ($request_uri !~ "^/(wp-(?:content|includes|admin)).*") {
rewrite ^/([_0-9a-zA-Z-]+)/(.*.php)$ /$2 break;
}
set $test "";
if (!-e $request_filename) {
set $test P;
}
if ($uri !~ ^/(plesk-stat|webstat|webstat-ssl|ftpstat|anon_ftpstat|awstats-icon|external-nginx-static-location)) {
set $test "${test}C";
}
if ($test = PC) {
rewrite ^/.*$ /index.php;
}

In Plesk, we have created aliases that redirect to #. We have also checked all databases, .htaccess, and wp-config files for incorrect URLs, but nothing unusual has been found.

Do you have any idea what could be causing these redirect issues?
 
Ok I understand. I asked there also. They did not have an answer, they where also saying ask WP toolkit support. In the WP toolkit it is giving the wrong domain names from other multisites. How is that behevour working? Is it just scanning the links of the wp-admin area? And than giving the wrong name in the WP toolkit. In the domain section in Plesk, the names are correct
 
It gives the same domain name in to all our multistes in WP toolkit but in fact it are 3 differant Multisites. We put labels so we can still now what is real site.
 

Attachments

  • multisiteswptoolkit.png
    multisiteswptoolkit.png
    19.4 KB · Views: 7
Back
Top