[BUG?] Enable SSL with symbolic link and private html

[AudiAddict]

I have a user which has purchased a SSL certificate specifically for his domain name. This works perfectly when browsing to his https:// website instead of http.
The only challenge is that he has to maintain two different folders (wordpress) and he would like to have this merged to one folder.

I found the option in domain administration to " Use a symbolic link from private_html to public_html - allows for same data in http and https " which allows the user to have one folder but it is NOT using the https certificate then.

So in short:

- When using " Use a directory named private_html " --> SSL website works and the internet browser displays secured website with correct certificate but two folders have to be managed / updated each time he makes changes

- When using " Use a symbolic link from private_html to public_html - allows for same data in http and https " the user is then linked to the public html folder but it is not secured (so no lock item and or certificate is displayed in the browser. Also SSL check websites are unable to verify the certificate).

How to solve this issue? It might be considered to be bug in Directadmin, because it would seem strange that you create a symbolic link for https and have it actually link back to NON ssl based connection (when accessing a https URL)

 

[ditto]

- When using " Use a symbolic link from private_html to public_html - allows for same data in http and https " the user is then linked to the public html folder but it is not secured (so no lock item and or certificate is displayed in the browser. Also SSL check websites are unable to verify the certificate).

I am using this way for a customer wich is having wordpress, and it does work on my servers. It is correct that private_html links to public_html, this way the site should work both with and without https

However when you are using wordpress, you need to log into wordpress and make needed changes. One change you need to make is to go to setttings - general, there you should change both url fields to be https urls

Also you should do search/replace in the database to replace all links to images to start with https, because if this is a existing site, they may be hardcoded with only http