site created, server not found

found mis-match between domain.com and https://www.domain.com.

That all occurs during setup. make sure when you type stuff in that it’s all one or the other, and make sure your server handles one or the other, redirecting the one you’re not using.

@ Andrea_r, My sins run ahead of me – may I ask what is the fix, please?

A good lot of SQL search and replace.

also a link to your site woudl help. Often a thread will go on for a page or so, and when we finally get a link, we’re able to diagnose the issue straight away.

@ipstenu – Sorry but that is far beyond my understanding – but I can learn.

@andrea_r – the website is https://www.sweetblogspot.com

I am happy to send you user and pass info by email
[email protected]

Apologies if this breaches protocol.

Trawling through the database I found the following:

wp_blogs:
blog_id 1 Site_id 1 path:www.domain.com all else same but for Lang_id 0
blog_id 7 Site_id 1 path:www.domain.com all else same but for Lang_id 1
– should the lang-id be the same??

wp_sitemeta:
metakey: subdomain install, metavalue: 0
metakey: global_terms_enabled, metavalue: 0
– perchance this is where the problem lays??? I suspect the metavalues should be 1, but would like confirmation.

wp_site = https://www.domain.com

In your wp-config.php file, what do you have for DOMAIN_CURRENT_SITE?

define( 'DOMAIN_CURRENT_SITE', 'https://www.domain.com'); or define( 'DOMAIN_CURRENT_SITE', 'https://domain.com');

(NOTE: I’m NOT saying you should change it! I just want to know what it is!!)

Did you set up subfolder install s or subdomains? Becasue your db diving is going down rabbit holes.

@ipstenu – It is set as:
define( ‘MULTISITE’, true );
define( ‘SUBDOMAIN_INSTALL’, true );
$base = ‘/’;
define( ‘DOMAIN_CURRENT_SITE’, ‘www.sweetblogspot.com’ );
define( ‘PATH_CURRENT_SITE’, ‘/’ );
define( ‘SITE_ID_CURRENT_SITE’, 1 );
define( ‘BLOG_ID_CURRENT_SITE’, 1 );

@andrea_r – frankly I am now a little unsure – can I specify one at this stage? ie-if I specify folders, then the https://www.domain.com is valid, and I think the subdomain will still show as site2.domain.com/blog/etc.
Am I right? – or am I looking at a rebuild…

@andrea_r – frankly I am now a little unsure – can I specify one at this stage? i

look at this line:

define( ‘SUBDOMAIN_INSTALL’, true );

This means you have subdomains for new sites. Did you set up wildcard subdomains? That’s a requirement.

I have a note i to my ISP asking for confirmation.

Subdomain True means that the sites show as site2.domain.com I understand.

The base entry is still https://www.domain.com, correct me if I am wrong.

What I see is a problem resulting from a mis-match of domain.com and https://www.domain.com. That is why I wonder if the:
wp_sitemeta:
metakey: subdomain install, metavalue: 0
metakey: global_terms_enabled, metavalue: 0
has relevance. I always thought the 0 meant not, and the 1 meant yes.

I wondered if changing those values might solve the problem of the missing server.

metakey: global_terms_enabled, metavalue: 0
has relevance. I always thought the 0 meant not, and the 1 meant yes.

I wondered if changing those values might solve the problem of the missing server.

No, this one at the top has nothing to do with it.

Those values will be 0 or 1 only if they are boolean. Changing them in the db will not magically make the subdomains work – as I stated above, that has to be set up server side. If your host has not set them up in apache, and you didn’t do the DNS record for it, then it will not work.

See: https://codex.www.ads-software.com/Create_A_Network#Step_2:_Setting_Wildcard_Subdomains

@andrea_r – so what is the answer?

If I remove all but the contents folder, (backup the DB) re-install the WP, go through the re-install/network setup for sub-domains and point it at the existing DB, will this work? It would be good to have the site2.site1.com setup.

If we run this road, are there other files I need to protect in the existing install?

I would be sad to lose the existing blogs but I do have the information copied (screenprints) to re-install if all alse fails.
Regards

so what is the answer?

I gave it to you in the link I posted.

If I remove all but the contents folder, (backup the DB) re-install the WP, go through the re-install/network setup for sub-domains and point it at the existing DB, will this work?

No, because none of that has anything to do with setting up wildcard subdomains on the server, as is pointed out in the link I gave you.

It;s got nothing to do with the files. It’s your server. Are wildcard subdomains set up on the server? Did you ask your webhost?

Sequel. The ISP finally got the subdomain wildcard fixed. The error of wp-config.php vs the WP install domain settings is still there, but with WP3.1.3 it does not seem to matter.
We shall see what future versions do to keep this crossup of settings under control.
Just a final word, if the ISP says they have fixed the *wildcard issue and things still don’t work, keep going back – eventually they will get someone who can “fix the switch”