v1.649 How to create symlink private_html to public_html ?

mean

Verified User
Joined
Feb 14, 2007
Messages
108
Dear DA Team.

Directadmin Version 1.649
After you deprecate this feature https:// cannot point to public_html
I recommend rollback " private_html setup " feature better than remove this function

How to create a symlink private_html to public_html on Directadmin FileManager ?
Or now, it automatically ?

We can do, before create symlink private_html to public_html
You need to check if there are any files, folders in the "private_html" then move private_html to private_html.backup
and then create symlink private_html to public_html

Or check if the file exists in private_html , No action is taken.

What are you think ?

---------------

Removed domain private_html directory or symlink toggle evolution removed

The private_html selector, which allowed switching between two possible private_html modes (directory and symlink) when modifying a domain, has been removed from Evolution.

Accidentally switching between these two modes could result in the loss of important information. Users can still replicate this functionality with FileManager if desired.

 
Oh sorry i just saw
 
How to create a symlink private_html to public_html on Directadmin FileManager ?
Or now, it automatically ?
Yes automatically now, already for a longer time, which is why they removed the option.
But you found it already I see.
 
Dear @Richard G

Real word DA v1.649
After import a new SSL Certificate or checked "Force SSL with https redirect"

DA doesn't automatically create a symlink private_html to public_html
DA create only empty private_html folder.


default_private_html_link=1 or 0 both same a problem.

Do you have the same problem as me?
CJ.
 
default_private_html_link=1 or 0 both same a problem.

Do you have the same problem as me?
Due to the change, the default_private_html_link=1 (which was default before), became obsolete and is removed.

Symlink to public_html is automatically created on domain creation, not on SSL creation.

So if you have only a private_html directory on domain creation, something is wrong with your system.
I just tested with 1.649 on my system, and when creating a new domain, private_html symlink to public_html is created as should be.
 
For domains created before version 1.649,

how would private_html be managed
if the "private_html setup" has been removed?

Because existing any domains created a long time may have both private_html and public_html folders.

DA can implement after SSL updated then check and create a private_html symlink automatically?
exclude if already exists another files in private_html (without default) it possible.
 
Last edited:
Because existing any domains created a long time may have both private_html and public_html folders.
Ah yes, that's indeed a thingie.

DA can implement after SSL updated then check and create a private_html symlink automatically?
That would be a solution. However, some users still want the seperate private_html for whatever purpose.

I found a method for you, which requires you to create a custom template. But that way you can change it for the whole server that in case of SSL creation the public_html is used.
Check this post:
it's quite ancient (19 years old) but that template still exists and seems still usable as far as I can see.

However, use at your own risk.

Maybe there is also a command or script which searches for private_html directory's, deletes them and then symlinks them to public_html.
But I'm no scripter and not that good which these kind of commands in Linux.

Maybe @zEitEr can help you with that.
Because if you set all with a symlink then all directory's are "up to date" with how it's used nowadays again.
 
After the upgrade to version 1.649, I noticed that some of my older accounts still had Private_html folders that need to be updated to a symlink to the public_html folder.
How can I manually accomplish that for those old accounts that were never properly updated before the removal of that feature from the evolution skin?
 
@gerrybakker

The issue still persists with the older account.

# Solution
Check and remove folder /domains/{DOMAIN}/private_html by yourself.
Before deleting, please make sure that there are no website files inside the folder private_html.

Goto DA Dashboard / Domain Management / Click Your Domain / Click "Setup symlink for private_html"

1688822859168.png
 
Hi @Richard G

I checked just a moment ago. v1.650 , Evolution Skin
"Setup symlink for private_html" does not need to delete the private_html folder beforehand.

However, when click on that menu, the folder and all the data inside private_html will be permanently deleted.

Why doesn't DirectAdmin check if there are any files in private_html?
If not empty, rename it to private_html.DATE or to a different name before creating the symlink.

I think it's safer.
 
Last edited:
I have v1.650 , Evolution Skin

but I don't see this option/choice
"Setup symlink for private_html"

What am I missing?
 
@gerrybakker

The issue still persists with the older account.

# Solution
Check and remove folder /domains/{DOMAIN}/private_html by yourself.
Before deleting, please make sure that there are no website files inside the folder private_html.

Goto DA Dashboard / Domain Management / Click Your Domain / Click "Setup symlink for private_html"

View attachment 6993
I don't see any "Useful Links" in my user account dashboard using the Evolution 1.650 skin - How do I activate that feature so that I can find the "Setup symlink for private_html" link?
 
I don't see any "Useful Links" in my user account dashboard using the Evolution 1.650 skin - How do I activate that feature so that I can find the "Setup symlink for private_html" link?
Seems they dropped this feature completely in Evo Skin

https://docs.directadmin.com/change...main-private-html-directory-or-symlink-toggle

 
the folder and all the data inside private_html will be permanently deleted.
Yes that is correct. I remember that there was a warning when clicking the link, that all contant would be deleted. However, that was in Enhanced skin. The warning should still be present. Is the warning gone or is the warning still in place?

However, they indeed dropped the option very recently.
 
In the end, I returned to the "Enhanced" skin to get this done for those few old accounts missing the symlink.
Now I am using the new Evolution skin again, and everything works as it should,
 
Back
Top