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
Vestacp can change ipv4 to ipv6 ?
Vestacp can change ipv4 to ipv6 ?
Hello Vestacp , can i need use ipv6 on vestacp more ipv4 . so , vestacp can change ipv4 to ipv6 ?
Re: Vestacp can change ipv4 to ipv6 ?
ipv6->ipv4 method works fine
you can add in /etc/nginx/conf.d/your-ip.conf
you can add in /etc/nginx/conf.d/your-ip.conf
Code: Select all
listen your-ipv6:80;
Re: Vestacp can change ipv4 to ipv6 ?
I added this rule, however I still receive information that the server is not ready for ipv6
AAAA DNS record - OK - Found
IPv6 web server - Error - web server is unreachable: Connection refused
AAAA DNS record - OK - Found
IPv6 web server - Error - web server is unreachable: Connection refused
Re: Vestacp can change ipv4 to ipv6 ?
And you added ipv6 configuration to network config in your OS?
Re: Vestacp can change ipv4 to ipv6 ?
In Ubuntu 16.04 x64:
##############################################################
nano /etc/nginx/conf.d/45.76.163.249.conf
# Replace From:
server {
listen 45.76.163.249:80 default;
server_name _;
#access_log /var/log/nginx/45.76.163.249.log main;
location / {
proxy_pass http://45.76.163.249:8080;
}
}
# Replace To:
server {
listen [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:80 default;
server_name _;
#access_log /var/log/nginx/45.76.163.249.log main;
location / {
proxy_pass http://[2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8080;
}
}
##############################################################
nano /etc/apache2/conf.d/45.76.163.249.conf
# Replace From:
Listen 45.76.163.249:8080
Listen 45.76.163.249:8443
# Replace To:
Listen [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8080
Listen [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8443
##############################################################
nano /home/admin/conf/web/apache2.conf
# Replace From:
<VirtualHost 45.76.163.249:8080>
# Replace To:
<VirtualHost [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8080>
##############################################################
nano /etc/network/interfaces
# Replace From:
auto lo
iface lo inet loopback
auto ens3
iface ens3 inet dhcp
iface ens3 inet6 auto
# Replace To:
auto lo
iface lo inet loopback
iface lo inet6 loopback
auto ens3
iface ens3 inet static
address 45.76.163.249
netmask 255.255.254.0
gateway 45.76.162.1
dns-nameservers 8.8.4.4 8.8.8.8
iface ens3 inet6 static
address 2001:19f0:4400:44e1:5400:00ff:fe4e:1dea
netmask 64
gateway 2001:19f0:4400:44e1::
dns-nameservers 2001:4860:4860::8844 2001:4860:4860::8888
##############################################################
In Vesta GUI, I added AAAA entries for ftp, pop, www, mail, @
##############################################################
But I still receive Error 500. What else do I need to adjust, please? :(
##############################################################
nano /etc/nginx/conf.d/45.76.163.249.conf
# Replace From:
server {
listen 45.76.163.249:80 default;
server_name _;
#access_log /var/log/nginx/45.76.163.249.log main;
location / {
proxy_pass http://45.76.163.249:8080;
}
}
# Replace To:
server {
listen [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:80 default;
server_name _;
#access_log /var/log/nginx/45.76.163.249.log main;
location / {
proxy_pass http://[2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8080;
}
}
##############################################################
nano /etc/apache2/conf.d/45.76.163.249.conf
# Replace From:
Listen 45.76.163.249:8080
Listen 45.76.163.249:8443
# Replace To:
Listen [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8080
Listen [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8443
##############################################################
nano /home/admin/conf/web/apache2.conf
# Replace From:
<VirtualHost 45.76.163.249:8080>
# Replace To:
<VirtualHost [2001:19f0:4400:44e1:5400:00ff:fe4e:1dea]:8080>
##############################################################
nano /etc/network/interfaces
# Replace From:
auto lo
iface lo inet loopback
auto ens3
iface ens3 inet dhcp
iface ens3 inet6 auto
# Replace To:
auto lo
iface lo inet loopback
iface lo inet6 loopback
auto ens3
iface ens3 inet static
address 45.76.163.249
netmask 255.255.254.0
gateway 45.76.162.1
dns-nameservers 8.8.4.4 8.8.8.8
iface ens3 inet6 static
address 2001:19f0:4400:44e1:5400:00ff:fe4e:1dea
netmask 64
gateway 2001:19f0:4400:44e1::
dns-nameservers 2001:4860:4860::8844 2001:4860:4860::8888
##############################################################
In Vesta GUI, I added AAAA entries for ftp, pop, www, mail, @
##############################################################
But I still receive Error 500. What else do I need to adjust, please? :(
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Vestacp can change ipv4 to ipv6 ?
Check your error log. The configs looks fine.
-
- Posts: 13
- Joined: Sat Feb 13, 2016 11:03 am
Re: Vestacp can change ipv4 to ipv6 ?
Hiskurudo wrote:ipv6->ipv4 method works fine
you can add in /etc/nginx/conf.d/your-ip.confCode: Select all
listen your-ipv6:80;
I have tried to add
/etc/nginx/conf.d/2400:6180:0:d0::261e:9001.conf
and in the file
server {
listen 2400:6180:0:d0::261e:9001:80;
}
but it still failed to validate at http://ipv6-test.com/validate.php
Tested on Sat, 11 Feb 2017 01:59:01 GMT
AAAA DNS record 2400:6180::d0:0:0:261e:9001
IPv6 web server web server is unreachable : Connection refused
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Vestacp can change ipv4 to ipv6 ?
You need to add [] around your ipv6 in your Nginx and httpd configs.
server {
listen [2400:6180:0:d0::261e:9001]:80;
}
server {
listen [2400:6180:0:d0::261e:9001]:80;
}
-
- Posts: 13
- Joined: Sat Feb 13, 2016 11:03 am
Re: Vestacp can change ipv4 to ipv6 ?
I would like to change the template file so that we do not need to add these line every time creating a new domain
however there are so many template file, which is the correct one? we are using nginx + php-fpm
[root@minato ~]# cat /usr/local/vesta/data/templates/web/nginx/
caching.sh caching.tpl default.tpl hosting.stpl php-fpm/
caching.stpl default.stpl hosting.sh hosting.tpl proxy_ip.tpl
[root@minato ~]# cat /usr/local/vesta/data/templates/web/nginx/php-fpm/
cms_made_simple.stpl dokuwiki.stpl piwik.stpl
cms_made_simple.tpl dokuwiki.tpl piwik.tpl
codeigniter2.stpl drupal.stpl pyrocms.stpl
codeigniter2.tpl drupal.tpl pyrocms.tpl
codeigniter3.stpl joomla.stpl wordpress2.stpl
codeigniter3.tpl joomla.tpl wordpress2.tpl
datalife_engine.stpl no-php.stpl wordpress.stpl
datalife_engine.tpl no-php.tpl wordpress.tpl
default.stpl owncloud.stpl
default.tpl owncloud.tpl
however there are so many template file, which is the correct one? we are using nginx + php-fpm
[root@minato ~]# cat /usr/local/vesta/data/templates/web/nginx/
caching.sh caching.tpl default.tpl hosting.stpl php-fpm/
caching.stpl default.stpl hosting.sh hosting.tpl proxy_ip.tpl
[root@minato ~]# cat /usr/local/vesta/data/templates/web/nginx/php-fpm/
cms_made_simple.stpl dokuwiki.stpl piwik.stpl
cms_made_simple.tpl dokuwiki.tpl piwik.tpl
codeigniter2.stpl drupal.stpl pyrocms.stpl
codeigniter2.tpl drupal.tpl pyrocms.tpl
codeigniter3.stpl joomla.stpl wordpress2.stpl
codeigniter3.tpl joomla.tpl wordpress2.tpl
datalife_engine.stpl no-php.stpl wordpress.stpl
datalife_engine.tpl no-php.tpl wordpress.tpl
default.stpl owncloud.stpl
default.tpl owncloud.tpl
-
- Collaborator
- Posts: 783
- Joined: Mon May 11, 2015 8:43 am
- Contact:
- Os: CentOS 6x
- Web: apache + nginx
Re: Vestacp can change ipv4 to ipv6 ?
The name of the template is the same as the what you choose when you add the domain.