admin管理员组文章数量:1134247
So, this is the situation. I have a working top level domain site () and I set up a wild card subdomain (
*.example
) and multisite settings in WordPress. It works as expected, as in if I go to network and create a new site (e.g. ), it does that. However, when I check the settings for that new site under Site > edit, instead of using the subdomain URL, it uses the top level domain URL. If I then manually correct this, I am still being redirected (e.g.
keeps being redirected to the top level
wp-admin
page). I also noticed that when I manually correct the URL to b2b.example
and I visit /wp-admin
it goes back to example
.
I suspect this has to do with my .htaccess
, but I'm not very sure of it, so any help is welcome. The site is redirected from http to https for all domains, including the wildcard sub domains.
Here is (part of) my .htaccess
:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\Comodo\DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/.+$
RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
#Rewrite http to https
RewriteEngine On
RewriteCond %{HTTPS} !=on [NC]
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
Header always set Content-Security-Policy "upgrade-insecure-requests;"
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
Can anyone give me some advice?
So, this is the situation. I have a working top level domain site (https://example.com
) and I set up a wild card subdomain (*.example.com
) and multisite settings in WordPress. It works as expected, as in if I go to network and create a new site (e.g. https://b2b.example.com
), it does that. However, when I check the settings for that new site under Site > edit, instead of using the subdomain URL, it uses the top level domain URL. If I then manually correct this, I am still being redirected (e.g. https://b2b.example.com/wp-admin
keeps being redirected to the top level wp-admin
page). I also noticed that when I manually correct the URL to b2b.example.com
and I visit /wp-admin
it goes back to example.com
.
I suspect this has to do with my .htaccess
, but I'm not very sure of it, so any help is welcome. The site is redirected from http to https for all domains, including the wildcard sub domains.
Here is (part of) my .htaccess
:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\Comodo\DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/.+$
RewriteRule ^(.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
#Rewrite http to https
RewriteEngine On
RewriteCond %{HTTPS} !=on [NC]
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
Header always set Content-Security-Policy "upgrade-insecure-requests;"
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
Can anyone give me some advice?
Share Improve this question edited Nov 6, 2023 at 13:21 MrWhite 3,8911 gold badge20 silver badges23 bronze badges asked Nov 3, 2023 at 16:27 Sven VSven V 113 bronze badges 1 |1 Answer
Reset to default 1Take a look at your wp-config.php
file. For a subdomain installation, you should have something like this:
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'rareteas.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
If you have SUBDOMAIN_INSTALL set to false, change it to true, which is necessary for a subdomain multisite.
Next, take a look at your database. Sometimes URLs get written directly into the tables and don’t want to leave without a bit of coaxing. Access your database via phpMyAdmin or similar and check the wp_site
, wp_blogs
, wp_options
(for each site, the table might be wp_2_options
, wp_3_options
, etc.), and wp_sitemeta
tables. Make sure the URLs are correct and reflect the subdomain structure you’re aiming for.
And if you're using domain mapping or have any domain redirect plugins, it's worth disabling them temporarily to see if it alleviate the issue.
本文标签: redirectWildcard multisite wpadmin url wrongfully redirected
版权声明:本文标题:redirect - Wildcard multisite wp-admin url wrongfully redirected 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1736758437a1951412.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
.htaccess
file you've posted that would cause this behaviour. Check theX-Redirect-By
HTTP response header on the initial (redirect) response - this may give you a clue as to what is triggering the redirect. – MrWhite Commented Nov 6, 2023 at 13:15