You forgot to tell us what subdomain doesn’t work…
You did mention the subdomain answered with a default PHP page which makes me wonder if the host server you did reach provided a default server page or was that a default WordPress page for your root domain or possibly the subdomain you created.
These are things I could have checked if I would have been given the subdomain name.
I’m happy to report the URL you did provide worked after stripping off the redundant ‘WWW’ well-known service name. Please don’t tell me you were trying to use the ‘WWW’ subdomain as the subdomain without fixing the htaccess file.
I tried to look at your webserver but Hostinger was a bit ‘tight-lipped’ on the info provided… I do hope you are on an Apache-based Xnix box!
Anyway, let us know what else you might need from us.
Greetings, the sub domain with problems is live.ninoskabermudez.com, it responds perfectly from the browser showing default.php, but when trying to enter the desktop of the sub domain, the error 404 appears. Do you require other information?, thanks.
-
This reply was modified 5 years, 9 months ago by
jguzmanve.
Okay, that ‘error page’ is coming from your server which doesn’t know about that subdomain so it doesn’t know to pass that to WordPress.
Does Your web host, Hostinger (I think) offer a hosting control panel?
If so you need to set up the subdomain in the CP to point to the directory containing your WordPress install.
You’ll need to also ensure your subdomain is properly mapped to the proper site but since you did a subdomain install that probably is right already. Once the CP knows what to do then it should work in that case.
Hostinger support may be able to help you through this.
The ‘star’ or ‘@’ character in DNS will save you some DNS work when setting the subdomains but control panels choke on WildCard sub domains as they deal in specific names.
So let us know what else you need if you can’t get it working still.
Hi, my answers in your comments
Okay, that ‘error page’ is coming from your server which doesn’t know about that subdomain so it doesn’t know to pass that to WordPress.
Does Your web host, Hostinger (I think) offer a hosting control panel? Yes
If so you need to set up the subdomain in the CP to point to the directory containing your WordPress install. yes, this is the subdomain path
/home/u428654322/domains/ninoskabermudez.com/public_html/life
You’ll need to also ensure your subdomain is properly mapped to the proper site but since you did a subdomain install that probably is right already. Once the CP knows what to do then it should work in that case.
Hostinger support may be able to help you through this.
The ‘star’ or ‘@’ character in DNS will save you some DNS work when setting the subdomains but control panels choke on WildCard sub domains as they deal in specific names.
Yes, In hostinger’s DNS editor appears “*”, “@”, even “life”, the provider validated this configuration saying that the problem should not continue, but it is not.
So let us know what else you need if you can’t get it working still.
Do you think it is a problem that the hosting provider? What else should I check?
Only a guess as I can’t see your CP but the path should probably be…
public_html
instead of
public_html/life
Thanks for your answer, consulting with hostinger support, they tell me that I must do a WP installation in the subdomain, in all the tutorials that I have read, none says that, in fact it is a virtue of activating WP multi-site, not have the need to install the product again. I feel at a dead end. What should I do?
It would be a quick fix to install WP again in the subdirectory but you really wanted a multisite so that’s an option for you but if you can edit that path to point to the root ‘public_html’ I think you’ll be better off long term… if that then starts to work.
Your hosting support probably doesn’t understand things past a single WordPress install so multisite isn’t their strong point. I can certainly understand that!
What I’d have you do was spend some time working with that path to fix it. If you can’t get it working you could then wait till tomorrow and ask your web host for help ‘after the shift changes there’. You might find that support guru there who knows what to do.
If you really need to get that second site running then you could install WordPress there tonight and hopefully get that working until you can revisit the multisite when you have time. Just keep the multisite as is since it does answer the root domain name. Won’t hurt a thing to keep that for now.
Let us know what else you need.
Ok thanks for your suggestions, a few more questions, it tells me that I should point to the root of the site, to understand well, the subsite should not be created like this: /home/u428654322/domains/ninoskabermudez.com/public_html/life
How should the route be? thanks
That should be…
/home/u428654322/domains/ninoskabermudez.com/public_html
The control panel adds a new subdirectory when you add the subdomain through it but to use the WordPress the Apache webserver needs to be pointed to the directory where the multisite is installed… This can be confusing when you think about subdomains/subdirectories and multisite.
Just remember a subdirectory on the server actually exists while a subdirectory WordPress install is a method of initially addressing a new site under a multisite. Subdirectories for sites don’t actually exist on a multisite.
Some of the above is some of the biggest stumbling blocks for many multisite users. Me included.
-
This reply was modified 5 years, 9 months ago by
JNashHawkins.
Ok, thanks for your answer, now how do I make the server point to the correct path?
Probably best to ask Hostinger but if they can’t help you or point you in the right direction update this topic and tell me what Control Panel they use.
Here’s a control panel demo that supposedly covers the 6 different control panels they offer.
https://www.hostinger.com/tutorials/hosting-control-panels/
I might check that out myself this evening as there are two CPs I’ve never seen before and one that looks to be a private label derivative of another.
Hi, Hostinger uses hPanel. Continue with Hostinger’s support, two different engineers indicated that I should install WP in the created subdomain, despite having indicated that no totorial said it, and part of the benefits of the multisite would be lost, they insisted. I installed it and it worked perfectly.
Right! But that’s not a multisite which is what you seemed to want to use…
But for now it works as I agreed with back in this post! https://ww.wp.xz.cn/support/topic/problems-with-subdomains/#post-13374172
I do recommend in the future you might still find a way to use the H-panel to adjust the subdomain’s path to point to the multisite on the root path and to then migrate that subdomain site to the multisite.
Hello again, Hostinger support staff contacted me and indicated for WP multisite to work properly a subdomain “*” must be created
, but at the moment that functionality is not supported, to solve WP must be installed in each subdomain created. Case closed.
The problem was resolved, thanks.
