Separate private_html folder

Most of us are having no problems.

I don't know why you are because I'm not logged in to your server, but I know the symlink works for all our clients who request it.

Sure, if you don't want to take the time to figure out why you're having problems that most of us aren't having, then move to another server isntead, one that uses the same folder.

And then when that one has a problem, move to another server. And when that one has a problem, yet another.

Each time losing clients who get tired of continuous switching.

I've got an old Cobalt RaQ I can let you have cheap :) .

Jeff
 
knoxhosting said:
Good luck. I'm having the same problems. No other control panel I know of requires a public and a private html folder, requiring the maintainenace of TWO copies of the site. STUPID STUPID STUPID.
Click to expand...
Beauty is in the eye of the beholder.

Plesk and DA both use separate folders.

H-Sphere and Cobalt RaQs both use the same folder.

I'm not sure of CPanel, but I believe it uses separate folders.

There have been several fixes posted on the many threads devoted to this topic (and yes, I'm going to try to find all of them and merge them together), and one of those fixes can be used to set it up automatically server wide for all new domains. We've had no problem setting it up for several of our clients, so we know it's quite doable.

Jeff
 
If this person is an admin, I don't really see the problem here. It is very easy to setup DA not to create a seperate https folder.
 
I agree. If DA made a single html folder for both secure and unsecure connections it would be an even bigger hassle requiring more modification than now to seperate them back into two directories.
Personally, I like the seperate directories as it forces my applications such as billing to run over a secure connection.
 
I've always written applications where the user sets the document root of their application in their config file. osCommerce, CubeCart, and many other applications that require secure access do to.

IMHO, It's advantageous because the only thing that needs to be changed for a connection to go secure is the http(s):// part. No new paths to mess with, which simplifies installation for the end-user.
 
In case people are still struggling, particularly because of the length of this thread, I achieved the result just by editing the httpd.conf file associated with the domain (/usr/local/directadmin/data/users/) and just changed the two references of public_html to private_html, restarted Apache and all is working perfectly in that https:// points to exactly the same folders as http://.

Keep a backup of the existing httpd.conf file just in case but I don't think I'm having any problems.

Hope this helps.

Jon
 
I have noticed all these templates

virtual_host2_sub.conf
virtual_host.conf virtual_host_secure.conf
virtual_host2.conf virtual_host_secure_sub.conf
virtual_host2_secure.conf virtual_host_sub.conf
virtual_host2_secure_sub.conf

does the change need to be made to all of them?
 
I could be wrong here but I think those files relate to new accounts should you want to change how all new accounts are set up. All I needed to do was change one particular account that had already been created so that the secure URL pointed to the public_html folder.

If anyone could confirm this that would be helpful.
 
yes I am referring to default for all accounts, in a previous post it was mentioned only 2 template files need to be changed but I have noticed there is half a dozen templates so am wondering if they all need to be changed.
 
Again I'm not 100% sure but I should think that any references to private_html should be changed to public_html however many files that would involve.

Hopefully someone with more knowledge on this could confirm what I've said?
 
You must log in or register to reply here.
Back
Top