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
Unable to add www as server alias
-
ByProgrammer
- Posts: 2
- Joined: Sat Apr 07, 2018 9:38 pm
- Os: CentOS 6x
- Web: apache + nginx
Re: Unable to add www as server alias
So thanks a lot for the solution. I have done it and now I'm waiting the DNS update to view if it works or not, but for the moment I could add the alias with also the SSL Encryption.
But just another question: I have the last version of VESTA CP (0.9.8 rel 21), why it isn't fixed??
Thanks.
But just another question: I have the last version of VESTA CP (0.9.8 rel 21), why it isn't fixed??
Thanks.
Re: Unable to add www as server alias
Worked for me, thanks!
Re: Unable to add www as server alias
This issue seems to have been re-introduced in the current version of Vesta (9.8.23). I've logged a bug in Github.
Meanwhile, the fix is to edit func/main.sh, line 936 and change
aliases=$(echo "$aliases" |grep -v www.$domain |sed -e "/^$/d")
to
aliases=$(echo "$aliases" |sed -e "/^$/d")
Meanwhile, the fix is to edit func/main.sh, line 936 and change
aliases=$(echo "$aliases" |grep -v www.$domain |sed -e "/^$/d")
to
aliases=$(echo "$aliases" |sed -e "/^$/d")
-
jacksrhymingego
- Posts: 2
- Joined: Fri Nov 16, 2018 5:23 pm
- Os: Ubuntu 16x
- Web: apache
Re: Unable to add www as server alias
Jumping on this issue - is there any SEO or speed benefit to adding a www alias? I'm using the non-www version as the default on my domain but should I add a www version in there as well?
Re: Unable to add www as server alias
Its a personal choice. See https://www.yes-www.org/ and https://dropwww.com/why
My personal feeling is that you should probably have both, but pick one and redirect all traffic from the one you don't want, to the one you do want.
In terms of speed. No difference, except maybe the shorter one is faster to type.
In terms of SEO, some people say you get penalised for having the same content on two separate domains.
My personal feeling is that you should probably have both, but pick one and redirect all traffic from the one you don't want, to the one you do want.
In terms of speed. No difference, except maybe the shorter one is faster to type.
In terms of SEO, some people say you get penalised for having the same content on two separate domains.