Beeblebrox-BSD

Thanks for the answer,

Add this to your htaccess:

Since most non-Apache servers (Lighttpd, Nginx) don’t support .htaccess settings, are you saying that php-fpm actually processes settings in that file? I cannot find any meaningful discussion on that, and it doesn’t make much sense to me that php-fpm would process .htaccess independently from the HTTP server.

Also, Lighttpd does not have or make use of mod_authz_core.c

Would appreciate if you could clarify. Thanks.

• This reply was modified 4 years, 2 months ago by Beeblebrox-BSD.
• This reply was modified 4 years, 2 months ago by Beeblebrox-BSD.

Hi, Thanks for trying to help.

I’m pretty sure my service blocks outbound port 25. Wordfence “Send a test email from this WordPress server to an email address” returns false as well. So, I’m unable to directly send the email to you.

I generated a report from the link “Click to view your system’s configuration in a new window”, and sent that as an HTML single-page.

Regards.

Hi & thanks for the answer.

Diagnostic report emailed. I had to expand the report and copy/paste the contents. I hope this is adequate.

Regards.

Hi Steven, thanks for the answer.

just noticed you’re on localhost

The instance is on public facing Cloud and I have full O/S root control – so I do need to lock down. Sorry if I placed the Q in the wrong forum.

If you change the ownership of the wordpress tree on your server to the user under which PHP is running, then WP will be able to update itself without needing FTP.

1. I only recursive-changed the wp-content folder ownership (all other folders still owned by root) and this partial change solved the problem for now.
2. Re PHP: I think php-cgi runs as nobody:nogroup (which are the folder permissions that seem to work for PHP sessions folders). This did not work for me though.

Active UNIX domain sockets (only servers)
/var/run/lighttpd/php.socket-0

• This reply was modified 4 years, 4 months ago by Beeblebrox-BSD.

Solved RULE-1. This means RULE-1 no longer breaks when I enable RULE-2.

On to issue of “*.domain.com (except www) to be served by folder domain.com/wordpress”

wpemy: Unless you have a better explanation, the problem has nothing to do with a *.domain.com DNS record.
* MultiSite is not enabled yet. I posted in this sub-forum because I want this issue tracked in a single thread.
* Records for rs.domain.com URL are obviously working, otherwise the browser would not reach the WP front page at all. sub-folders to the URL (like rs.domain.com/wp-admin/) have no relation to DNS (subdomain) records or http’s document_root.

I now simplify the original question:
WP Codex states two important steps for WP located in subfolder
1. Modify index.php
2. Modify .htaccess to subfolder path.

Assuming all “*.domain.com” URL’s safely get passed to the domain.com/wordpress folder, how must the above 2 files be modified to get WP working properly? Single subdomain case first, and wildcard (all subdomains) case separately if possible please.

Regards.

Did you check the Wildcard in cpanel ?

Do you mean DNS records? If there were problems with that, rs.domain.com would not be able to resolve (which as stated it does)

If you mean the site-url in the WordPress panel, the first step should be to get the simplified case of single sub-domain to work before the subsequnet steps of MultiSite?

Well a bit stupid of me, but I found this WP codex after my posting:
https://codex.www.ads-software.com/Multilingual_WordPress
While the multisite options look very interesting, I think maybe multisite is not the right solution for this issue, when I consider the amount of traffic expected for the site. It looks like multisite plugins may be ideal on a news-site for example?

After our conversation I filed a support ticket with the hosting co. They informed me that the plan I have does not support wildcard domain entry. A ticket I had opened previously had advised that wildcard domain was not a problem. I guess things change on a daily basis ??

I then created a single record for the rs.mydomain.com sub-domain and everything is working. Sorry for the noise and thanks for your help.

You previously mentioned the folder /www/mydomain/ All your subdomains should be using that folder.

They are – although unclear, that’s what I meant by the “hosting” bit in

DNS records and hosting has been setup for wildcard (*) dns & is resolving

IP and folder path for mydomain.com and *.mydomain.com are identical.

What about the setup for Sites in WP?
WORKING_SITE
https://mydomain.com has “Path /” and under Settings:
Siteurl https://mydomain.com/wordpress
Home https://mydomain.com

NOT_WORKING_SITE – What is the correct setting here?
https://rs.mydomain.com has “Path /” and under Settings:
Siteurl https://rs.mydomain.com
Home https://rs.mydomain.com
Changing Siteurl to https://mydomain.com/wordpress makes no difference.

Hello. Yes correct; the first link works while the second one does not.

For the .htaccess modification I tried all four of the combinations below, but none work. This was placed before the “WordPress Settings” section of the file.

DocumentRoot /wordpress OR /mydomain.com/wordpress

https://rs.mydomain.com/wp-login.php OR
https://rs.mydomian.com/wordpress/wp-login.php

EDIT: The ServerAlias setting is breaking the server. It now gives “500 Internal Server Error” when I visit the previously working main site at https://mydomain.com

Hi. When I go to https://rs.mydomain.com, I get the server’s 404 page:

Not Found
The requested URL / was not found on this server.
Apache/1.3.33 Server at rs.mydomain.com Port 80

The hosting plan does not allow for me to look through server logs, so I cannot examine what the error exactly is.

Sorry, my friend, but I am way ahead of what you are explaining for me. As stated in first post:

* WP was installed into wordpress folder. Primary site working.
* Nothing was moved or migrated. This is a fresh setup.
* WP Network (multisite) was activated for sub-domain setting.
* .htaccess and wp-config.php was modified as stated in post #1
* DNS records and hosting has been setup for wildcard (*) dns & is resolving

I don’t know what else I can tell you. All setup has been completed according to codex, but sub-domian is not being served by WP. It’s probably a simple issue, but it’s either in .htaccess or in the WP setup IMHO. I have tried several modifications but no luck.

Regards.

jkhongusc: I had already studied ALL of those codex pages before I started the thread.

You havent even installed WP correctly

My site was/is installed correctly. In my first post I had stated that WP was installed under www/mydomain/wordpress (as described in the Giving_WordPress_Its_Own_Directory codex article).

I had apparently overlooked placing and modifying an index.php file under www/mydomain. Once that was done, https://mydomain started working normally and problem for site #1 is thus solved.

Site #2 is still not working; giving 404 error. My assumption is that the request comes to the server (because all dns records are correct), but does not either
A. Get passed to WordPress engine or
B. WordPress setting for for this site is worng.

multisite-WP must be in domain’s folder (www/mydomain) and not in a sub-folder (www/mydomain/wordpress). This probably is not the case for 3.8.1?

I was referring to https://codex.www.ads-software.com/Before_You_Create_A_Network#Server_Requirements when I asked this. It states:

You cannot choose Sub-domain Install (for a domain-based network) in the following cases:
* The WordPress URL contains a path, not just a domain. (That is, WordPress is not installed in a document root, or you are not using the URL of that document root.)

If this is still valid, it means that multi-sites will not work if WordPress is given its own sub-folder?

I’m on the eastern side of the Atlantic, and it had gotten pretty late by the last post. When I woke up this morning, I realized what a dunce I had been, since all of WordPress code is located under www folder and can be uploaded. Upgraded to 3.8.1 as of this morning, before I read your post. Thanks, Mika.

Back to the problems at hand (all issues persist, btw). Let me reiterate some of the implied questions:
* Some sources state that multisite-WP must be in domain’s folder (www/mydomain) and not in a sub-folder (www/mydomain/wordpress). This probably is not the case for 3.8.1?
* I created a folder under wordpress/wp-content/rs.mydomain for that particular site. Several sources state that folder location is not per-site but that all sub-domain networks go into one folder (blog or whatever). This is also pre-3.8 I presume?
* I have the mu-domain-mapping plugin installed, however I am not using it as yet because I would prefer to make sure I have all the fundamentals correctly in place before I go mucking with ifs and maybes.
* I didn’t see how an upgrade would fix erroneous redirect/rewrite code in my htaccess/WordPress configuration – and it has not corrected the issue. The hosting firm’s banner is displayed when I direct the browser to https://mydomain. It’s only when I go to https://mydomain/wordpress that I see the site I designed. To me, this means that the htaccess setup is incorrect.
* The http/rs.mydomain site is not resolving on the host at all. After WP upgrade, I tried to run “Upgrade Network” as instructed and got this:
Warning! Problem updating https://rs.mydomain. Your server may not be able to connect to sites running on it. Error message: Couldn't resolve host 'rs.mydomain'
* Should I be placing a copy of wp-config.php in folder www/mydomain (above wordpress folder)?

You need to decide on sub-directory or sub-domain

I’m using sub-domain.

Did you follow the standard WP installation …
I recommend just re-installing WP. You will have to dump your database beforehand.

* Nothing in the DB worth saving.
* I previously had a test site up and running. I nuked everything and setup from scratch a Networked Site. The problem is not zero-install; its how to configure. I guarantee that I’ll run into the same issues when I re-install, because I will be doing the setup tha same way I did this one!