WordPress Multisite not working inside subdomain

Your host may not permit nested subdomains. Ask them if they do before going ANY further. Normal wildcard subdomains are at *.somewebsite.com.

If nested subdomains are not allowed then how come it works for URL/blogs that are not created?

In part, that depends on your host. Nested subdomains are a tricky thing.

Now the thing is when I create a new blog from admin panel and then try to access it then it doesn’t work. I get the same error that browser shows when you enter a URL that doesn’t exist for e.g. https://www.ddfdjfdfdffhjdfhdjhjfg.com

THAT implies that the domain isn’t working at all. If you go to https://foobar.ipstenu.org you will see what you SHOULD get if WordPress is correctly receiving your wildcard subdomain info.

When you get https://www.ddfdjfdfdffhjdfhdjhjfg.com’s response, that means that the entire internet has NO idea what your site is, and it doesn’t exist at all.

So basically, it’s not set up right, go ask your host.

For the most part, even if your host does support nested subdomains, they probably won’t support wildcard nested subdomains.

Try manually creating a sub-subdomain in your DNS/Hosting control panel for testing purposes (blog.beta, for instance) and see if that works.

Ok I created a nested subdomain in CPanel as follows:

test.beta.somewebsite.com

And it took me to WordPress page where it says it doesn’t exist and I need to register. Which means it is working fine!?

Yes BUT.

That means your host doesn’t support WILDCARD nested subdomains.

So you’ll need to make them manually (or bribe someone on your host to see if they can fix it for you). I suggest cookies and coffee.

I created nested.sub.domain.com and pointed it to the sub.domain.com IP address, but when I access nested.sub.domain.com it takes me to sub.domain.com.

I’ll say this one more time. Nested subdomains are a tricky thing.

If you’re new at the whole subdomain thing, don’t do this! It’s hard, it’s complicated, and it’s not always supported.

jtrost – Check with your host, though at a guess, you pointed the subdomain to the wrong place. With NORMAL subdomains, you point them at the public_html folder. For nested subdomains, I’d think you point them at public_html/sub but it depends on your host.

For nested subdomains, I’d think you point them at public_html/sub but it depends on your host.

Yep, possibly. At best, I woudl be doing this on at least a vps with ssh access to troubleshoot the httpd.conf if I needed to.

It’s working now. I didn’t do anything. I just sent an email to support asking to check why it’s happening. They said give us WP admin user and password so we can check WordPress. Then I found out today that nested subdomains are working.
May be it was DNS propagation issue!? But why other nested subdomains were working earlier? Anyway problem is solved now.

Change your WordPress password right away.

Never give it out to anyone, even your webhost. If they ask for it, tell them no. There is NO reason they should be mucking around in there. It’s not safe, it’s not secure, and they should damn well know better.

NEVER ever ever give out your password. Not even to your ISP. The only person, besides you, who should know your passwords is someone you trust with your life. End of story.

Actually I didn’t gave them password. After they asked for password I never replied back and when I checked then the nested subdomains issue was solved.
May be they did something at back end but didn’t tell me!?

That’s very likely. A lot of hosts like to hide the man behind the curtain :/

I’d still give them hell for even ASKING for your password. I love my host and the few times they’ve asked for it, I told them no, and asked to speak to a manager about improper internet security.

Then asking for your WP password is also bad, because nested subdomains is a server-side setting and absolutely nothing to do with the admin area of WP itself.

Yeah sure, wp uses it, but it has no way to control it…