We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
new subdomains not resolving and letsencrypt 400
new subdomains not resolving and letsencrypt 400
I'm on Centos:
CentOS Linux release 7.9.2009
I moved from a Centos 6 Box, everything moved fine, including subdomains, everything works as it should. However when creating new subdomains they do not resolve correctly nor will letsencrypt cooperate (400 or 429 codes returned).
The newly created subdomains either resolve to other subdomains (https) or resolve correctly but serve content from another subdomains directory (http).
https://test.example.com --> https://older.example.com
http://test.example.com --> http://test.example.com but serves files out of another subdomains directory
I did create A records and CNAME records for newly created subdomains.
A new public_html directory is created for the created subdomain as are httpd and nginx conf files.
CentOS Linux release 7.9.2009
I moved from a Centos 6 Box, everything moved fine, including subdomains, everything works as it should. However when creating new subdomains they do not resolve correctly nor will letsencrypt cooperate (400 or 429 codes returned).
The newly created subdomains either resolve to other subdomains (https) or resolve correctly but serve content from another subdomains directory (http).
https://test.example.com --> https://older.example.com
http://test.example.com --> http://test.example.com but serves files out of another subdomains directory
I did create A records and CNAME records for newly created subdomains.
A new public_html directory is created for the created subdomain as are httpd and nginx conf files.
-
- Support team
- Posts: 1111
- Joined: Tue Jul 30, 2013 10:18 pm
- Contact:
- Os: CentOS 6x
- Web: nginx + php-fpm
Re: new subdomains not resolving and letsencrypt 400
Did you create also A or CNAME records for aliases?johnking wrote: ↑Sun Jan 17, 2021 8:32 pmI'm on Centos:
CentOS Linux release 7.9.2009
I moved from a Centos 6 Box, everything moved fine, including subdomains, everything works as it should. However when creating new subdomains they do not resolve correctly nor will letsencrypt cooperate (400 or 429 codes returned).
The newly created subdomains either resolve to other subdomains (https) or resolve correctly but serve content from another subdomains directory (http).
https://test.example.com --> https://older.example.com
http://test.example.com --> http://test.example.com but serves files out of another subdomains directory
I did create A records and CNAME records for newly created subdomains.
A new public_html directory is created for the created subdomain as are httpd and nginx conf files.
Re: new subdomains not resolving and letsencrypt 400
Yes, in DNS panel
I can't create an alias under the domain as it is already existing domain.
DNS is working fine but the subdomain is being served from the wrong directory.Error: Web domain
test.example.com exist