WordPress.org

1. TechMan
   Member
   Posted 1 year ago #

   Hi,

   I just installed WP MS 3.0.4 on a subdomain as follows:

   http://beta.somewebsite.com

   So now when a new blog is created then it will have following URL:

   http://blog.beta.somewebsite.com
   http://test.beta.somewebsite.com
   http://mysite.beta.somewebsite.com

   I have given wild card entry in CPanel as *.beta.somewebsite.com

   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. www.ddfdjfdfdffhjdfhdjhjfg.com

   This is only happening for those URLs, blog of which I have created. If you try to access a blog which doesn't exist for e.g. notexists.beta.somewebsite.com then it doesn't show any error and instead takes you to page where WordPress says that this blog doesn't exist and that you should sign up.

   The .htaccess file is in "beta" folder and also that code which WordPress asked to write in "wp-config.php" file.

   What am I doing wrong?

   Thanks

2. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

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

3. TechMan
   Member
   Posted 1 year ago #

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

4. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   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. http://www.ddfdjfdfdffhjdfhdjhjfg.com

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

   When you get http://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.

5. Curtiss Grymala
   Member
   Posted 1 year ago #

   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.

6. TechMan
   Member
   Posted 1 year ago #

   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!?

7. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   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.

8. jtrost
   Member
   Posted 1 year ago #

   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.

9. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   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.

10. Andrea_r
    team pirate
    Posted 1 year ago #

    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.

11. TechMan
    Member
    Posted 1 year ago #

    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.

12. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    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.

13. TechMan
    Member
    Posted 1 year ago #

    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!?

14. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    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.

15. Andrea_r
    team pirate
    Posted 1 year ago #

    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...

Topic Closed

This topic has been closed to new replies.