We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on Vesta 2.0 and expect to release it by the end of 2024. Read more about it: https://vestacp.com/docs/vesta-2-development
force-https not working
force-https not working
Hi Community
I followed the instructions here https://vestacp.com/docs/#how-to-force-https to force all domains to SSL but it is not working. I have assigned force-ssl to the default template and the user is using the default template. I have even rebooted the server to no avail.
TIA
I followed the instructions here https://vestacp.com/docs/#how-to-force-https to force all domains to SSL but it is not working. I have assigned force-ssl to the default template and the user is using the default template. I have even rebooted the server to no avail.
TIA
Re: force-https not working
Please add a little more info.
> Operating System (OS/VERSION):
Type here, e.g. CentOS 6
> VestaCP Version:
Type here, e.g. 0.9.8-17
> Installed Software (what you got with the installer):
Type here, e.g. php-fpm, apache, nginx, mysql
> Steps to Reproduce:
Type here, e.g. install vesta and type cat /etc/issue
> Related Issues/Forum Threads:
Found anything that might be related to this? It might help us find the cause.
> Other Notes:
Anything else? May be logs?
> Operating System (OS/VERSION):
Type here, e.g. CentOS 6
> VestaCP Version:
Type here, e.g. 0.9.8-17
> Installed Software (what you got with the installer):
Type here, e.g. php-fpm, apache, nginx, mysql
> Steps to Reproduce:
Type here, e.g. install vesta and type cat /etc/issue
> Related Issues/Forum Threads:
Found anything that might be related to this? It might help us find the cause.
> Other Notes:
Anything else? May be logs?
Re: force-https not working
The fix was to create a new user and move the domain over.
-
- Posts: 139
- Joined: Thu Jan 07, 2016 12:01 am
Re: force-https not working
The other way to fix would've been (if using apache) to create a .htaccess file or use one that's already there and create a rewrite rule to do the same thing.arktex54 wrote:The fix was to create a new user and move the domain over.