Author Topic: ipv6 errors while setting up  (Read 2568 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
ipv6 errors while setting up
« on: March 04, 2016, 12:31:18 AM »
Hi, i've been told that CWP supports ipv6. i have gone to the effort to configure my server with several ipv6 addresses. However, when i go to create an account for a customer in CWP only my one default ipv4 address is shown and none of the ipv6 ones.

Please could someone assist? any help is greatly appreciated, thank you.
Josh

Offline
***
Re: ipv6 errors while setting up
« Reply #1 on: July 19, 2016, 02:47:23 PM »
I would like to know the answer to this question also.  I have tried almost everything I could find on the net and I still cant ping ip6

Offline
***
Re: ipv6 errors while setting up
« Reply #2 on: July 19, 2016, 03:09:27 PM »
HERES HOW I MADE IT WORK

IN VHOST CONFIGRUATION FILE I ADDED A SEPARATE WEBSITE FOR IP6.  JUST COPY EACH WEBSITE IN VHOST, PASTE RIGHT BELOW AND THEN CHANGE THE IP4 ADDRESS TO THE IP6 ADDRESS.  DONT FORGET IP6 IS IN  BRACKETS  [   ]

Offline
**
Re: ipv6 errors while setting up
« Reply #3 on: March 10, 2017, 02:36:29 PM »
HERES HOW I MADE IT WORK

IN VHOST CONFIGRUATION FILE I ADDED A SEPARATE WEBSITE FOR IP6.  JUST COPY EACH WEBSITE IN VHOST, PASTE RIGHT BELOW AND THEN CHANGE THE IP4 ADDRESS TO THE IP6 ADDRESS.  DONT FORGET IP6 IS IN  BRACKETS  [   ]

You can combine like this: (replace your IP6 address)


Quote
Listen [2a01:4f8:140:54e4::3]:80
 
<VirtualHost xx.xx.xx.xx:80 [2a01:4f8:140:54e4::3]:80>
  ServerName mydomain.com
  ...
</VirtualHost>


Offline
*
Re: ipv6 errors while setting up
« Reply #4 on: March 10, 2017, 05:25:21 PM »
IPv6 functionality should be included in CWP otherwise is pointless for every new domain to do manual setups  :)
“Would you tell me, please, which way I ought to go from here?”
“That depends a good deal on where you want to get to,” said the Cat.
“I don’t much care where–” said Alice.
“Then it doesn’t matter which way you go,” said the Cat.
Neo2SHYAlien's Blog

Offline
*
Re: ipv6 errors while setting up
« Reply #5 on: September 21, 2017, 08:31:43 PM »
There's no need to edit each one of your vhosts. You can edit the apache vhost template and then rebuild virtual hosts.

Here's what I did:

Apache Domain Virtual Host tpl:
Code: [Select]
# vhost_start %domain_name%
<VirtualHost %domain_ip%:%domain_port%>
ServerName %domain_name%
ServerAlias www.%domain_name%
ServerAdmin %admin_email%
DocumentRoot "%homedir%/%username%/public_html"
ScriptAlias /cgi-bin/ "%homedir%/%username%/public_html/cgi-bin/
#
# Custom settings are loaded below this line (if any exist)
# Include "/usr/local/apache/conf/userdata/%username%/%domain_name%/*.conf

<IfModule mod_suexec.c>
        SuexecUserGroup %username% %username%
</IfModule>

<IfModule mod_suphp.c>
        suPHP_UserGroup %username% %username%
        suPHP_ConfigPath /home/%username%
</IfModule>

<Directory "%homedir%/%username%/public_html">
        AllowOverride All
</Directory>

</VirtualHost>
# vhost_end %domain_name%

# vhost_start IPv6 %domain_name%
<VirtualHost [xxxx:xxxx:xxxx:xxxx::]:%domain_port%>
ServerName %domain_name%
ServerAlias www.%domain_name%
ServerAdmin %admin_email%
DocumentRoot "%homedir%/%username%/public_html"
ScriptAlias /cgi-bin/ "%homedir%/%username%/public_html/cgi-bin/
#
# Custom settings are loaded below this line (if any exist)
# Include "/usr/local/apache/conf/userdata/%username%/%domain_name%/*.conf

<IfModule mod_suexec.c>
        SuexecUserGroup %username% %username%
</IfModule>

<IfModule mod_suphp.c>
        suPHP_UserGroup %username% %username%
        suPHP_ConfigPath /home/%username%
</IfModule>

<Directory "%homedir%/%username%/public_html">
        AllowOverride All
</Directory>

</VirtualHost>
# vhost_end IPv6 %domain_name%

Apache SubDomain Virtual Host tpl:
Code: [Select]
# vhost_start %domain_name%
<VirtualHost %domain_ip%:%domain_port%>
ServerName %domain_name%
ServerAlias www.%domain_name%
ServerAdmin %admin_email%
DocumentRoot "%path%"
ScriptAlias /cgi-bin/ %path%/cgi-bin/
#
# Custom settings are loaded below this line (if any exist)
# Include "/usr/local/apache/conf/userdata/%username%/%domain_name%/*.conf

<IfModule mod_suexec.c>
        SuexecUserGroup %username% %username%
</IfModule>

<IfModule mod_suphp.c>
        suPHP_UserGroup %username% %username%
</IfModule>

<Directory "%path%">
        AllowOverride All
</Directory>

</VirtualHost>
# vhost_end %domain_name%

# vhost_start IPv6 %domain_name%
<VirtualHost [xxxx:xxxx:xxxx:xxxx::]:%domain_port%>
ServerName %domain_name%
ServerAlias www.%domain_name%
ServerAdmin %admin_email%
DocumentRoot "%path%"
ScriptAlias /cgi-bin/ %path%/cgi-bin/
#
# Custom settings are loaded below this line (if any exist)
# Include "/usr/local/apache/conf/userdata/%username%/%domain_name%/*.conf

<IfModule mod_suexec.c>
        SuexecUserGroup %username% %username%
</IfModule>

<IfModule mod_suphp.c>
        suPHP_UserGroup %username% %username%
</IfModule>

<Directory "%path%">
        AllowOverride All
</Directory>

</VirtualHost>
# vhost_end IPv6 %domain_name%

You have to chenge "xxxx:xxxx:xxxx:xxxx::" with your ip address.

Offline
***
Re: ipv6 errors while setting up
« Reply #6 on: October 07, 2017, 06:44:04 AM »
As much as I know CWP still don`t support IPv6. May be in future releases will be added. For the moment it`s pointless. You can count on the fingers of your both hands the people here asking about and using IPv6. For most of the people (mostly the people who just started to use Linux) it`s hard to figure out with 1-2 IPs v4 settings, not to talk to give them 18 trillion IPs v6. The people who wants and uses IPv6 already have basic skills how to add it to the system and to enable it for web server. May be more skills ... :D
Current uptime:
UNIX is a very simple OS, but you have to be a GENIUS to understand it ...

Offline
*
Re: ipv6 errors while setting up
« Reply #7 on: October 10, 2017, 04:26:05 PM »
As @darkness said, CWP still doesn't support IPv6. I tried to use IPv6 with CWP but many problems occurred. For example, sites with AJAX couldn't respond right, FTP couldn't connect even after successful authentication and many other problems...