the first issue I have on that instance:
I cannot access /etc/apache for doing Virtual Host settings, to redirect from http to https,
so I use .htaccess in the root directory.
Now, when I do an upgrade, It overwrites the file and my settings are lost.
So instead of getting more secure it get less secure after upgrade.
How can we fix this.
Another option I miss is to run this from inside the cloud, as this instance host doesn’t has ssh, instead over scan.php which I made like this:
Hehe you expect a lot On this instance its not there, the customer ordered a cheap one (before he went my customer). without cron. this package is “starter” and cron starts with “basic”
Regarding https:
I don’t have access to the apache config on my hoster as well, but there is an admin panel where such things (force https) can be configured. If your hoster does not support this, i suggest you look for another one. Messing with the .htaccess file all the time is not what you would like to do.