A friend of mine on x11 wanted me to let x10 know that someway somehow after the DirectAdmin update was performed, first off kudos for keeping up to up to date more often than cPanel, that SSL and https features have become enabled again on server x11. He wanted me to let you guys know before others try to keep doing it and have issues when you guys shut it back off.
Server x11
- Thread starter mycoo368
- Start date
- Status
- Messages
- 11,750
- Reaction score
- 581
- Points
- 113
We actually are testing the impact on the server with it turned on (it actually doubles the data stored for each domain in the configs). If tests go well it may stay on, we're not going to go official with supporting it until we know though.
By “doubling the data stored in the configs” do you mean as when it goes to backing them up that more is stored in general?
Wow though. Though my friend also noticed after the update that he can no longer edit records. He actually has to delete them and add them back for an updated. Not sure if something else was changed there.
- Messages
- 11,750
- Reaction score
- 581
- Points
- 113
no, this does not affect backups or file storage.
It is the config file that gets two entries for each domain, one for http and one for https, with the information about what filepath to serve files from, mainly due to the ability to keep http and https separate with using private_html for the https content (you can set a symbolic link to use the public_html content for both). This is probably not a huge issue for most shared hosting setups but with free we are a bit above average with number of accounts per server (which is why it is a bit restricted compared to our paid plans).
As for issues editing records it could definitely be related to the double data in configs. Though when I just tested on my account that happens to be on x11, it went through rather quickly when I changed the IP of a subdomain.
It is the config file that gets two entries for each domain, one for http and one for https, with the information about what filepath to serve files from, mainly due to the ability to keep http and https separate with using private_html for the https content (you can set a symbolic link to use the public_html content for both). This is probably not a huge issue for most shared hosting setups but with free we are a bit above average with number of accounts per server (which is why it is a bit restricted compared to our paid plans).
As for issues editing records it could definitely be related to the double data in configs. Though when I just tested on my account that happens to be on x11, it went through rather quickly when I changed the IP of a subdomain.
If only x13 was on that test too.
- Status