• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Question IPv6 unreachable

Sailorhost

New Pleskian

My server is Ubuntu : Ubuntu 18.04.6 LTS
MY PLesk : Plesk Obsidian Versão 18.0.39

IPv6 validation for http:// agenciasailorweb.com.br​

This tool lets you test the IPv6 configuration and connectivity of a web server.
ipv6-test.com


Result is :
AAAA DNS record - 2804:e6c:4000:11::1 - OK - Working
IPv6 web server : web server is unreachable : Permission denied

Buy AAAA is Apointment and valid
Webserver hosting config is ipv6 add

I've already performed the procedure ; How to enable IPv6 addresses on a Plesk server

And yet I can't get IPv6 to be correct.

MY IPTABLES LIST is:


-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -m state --state NEW -j REJECT --reject-with tcp-reset
-A INPUT -m state --state INVALID -j DROP
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m tcp --dport 10050:10051 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 35500:36000 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 60000:65534 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 49152:65535 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 12443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 11443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 11444 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8447 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8880 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 21 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 587 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 25 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 465 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 110 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 995 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 143 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 993 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 106 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 3306 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 5432 -j ACCEPT
-A INPUT -p udp -m udp --dport 137 -j ACCEPT
-A INPUT -p udp -m udp --dport 138 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 139 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 445 -j ACCEPT
-A INPUT -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -p ipv6-icmp -m icmp6 --icmpv6-type 134/0 -j ACCEPT
-A INPUT -p ipv6-icmp -m icmp6 --icmpv6-type 135/0 -j ACCEPT
-A INPUT -p ipv6-icmp -m icmp6 --icmpv6-type 136/0 -j ACCEPT
-A INPUT -p ipv6-icmp -m icmp6 --icmpv6-type 137/0 -j ACCEPT
-A INPUT -p ipv6-icmp -m icmp6 --icmpv6-type 128/0 -j ACCEPT
-A INPUT -p ipv6-icmp -m icmp6 --icmpv6-type 129/0 -j ACCEPT
-A INPUT -j DROP
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -m state --state NEW -j REJECT --reject-with tcp-reset
-A FORWARD -m state --state INVALID -j DROP
-A FORWARD -i lo -o lo -j ACCEPT
-A FORWARD -j DROP
-A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -m state --state NEW -j REJECT --reject-with tcp-reset
-A OUTPUT -m state --state INVALID -j DROP
-A OUTPUT -o lo -j ACCEPT
-A OUTPUT -j ACCEPT

Please I need help
 
I try :
The response for 'agenciasailorweb.com.br' using IPv4 is:pING agenciasailorweb.com.br (186.226.58.67) 56(84) bytes of data.
64 bytes from vps.sailorwebcloud.com.br (186.226.58.67): icmp_seq=1 ttl=50 time=186 ms
64 bytes from vps.sailorwebcloud.com.br (186.226.58.67): icmp_seq=2 ttl=50 time=186 ms
64 bytes from vps.sailorwebcloud.com.br (186.226.58.67): icmp_seq=3 ttl=50 time=186 ms
64 bytes from vps.sailorwebcloud.com.br (186.226.58.67): icmp_seq=4 ttl=50 time=186 ms
64 bytes from vps.sailorwebcloud.com.br (186.226.58.67): icmp_seq=5 ttl=50 time=186 ms

--- agenciasailorweb.com.br ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 186.148/186.283/186.538/0.491 ms


The response for 'agenciasailorweb.com.br' using IPv6 is:pING agenciasailorweb.com.br(2804:e6c:4000:11::1) 56 data bytes
64 bytes from 2804:e6c:4000:11::1: icmp_seq=1 ttl=52 time=191 ms
64 bytes from 2804:e6c:4000:11::1: icmp_seq=2 ttl=52 time=167 ms
64 bytes from 2804:e6c:4000:11::1: icmp_seq=3 ttl=52 time=168 ms
64 bytes from 2804:e6c:4000:11::1: icmp_seq=4 ttl=52 time=167 ms
64 bytes from 2804:e6c:4000:11::1: icmp_seq=5 ttl=52 time=167 ms

--- agenciasailorweb.com.br ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 167.929/172.776/191.924/9.581 ms

But error in IPV6 in IPV6 Validator CONTINUE
 

Is your site IPv6 ready?​


Test results for: .: Agência Sailorweb :. – Just another WordPress site

Test
Result
Detail
DNS (IPv6 NS) PASS

Hostname agenciasailorweb.com.br does have IPv6-addressed nameservers defined.
DNS (IPv6 TLD NS) PASS

Hostname top-level domain (br.) does have IPv6-addressed nameservers defined.
DNS (IPv4 A Record) PASS

Hostname agenciasailorweb.com.br does have an IPv4 A record (186.226.58.67).
DNS (IPv6 AAAA Record) PASS

Hostname agenciasailorweb.com.br does have an IPv6 AAAA record (2804:e6c:4000:11::1).
DNS (MX Record) PASS

Top-level domain (br.) does not appear to provide IPv6-accessible nameservers.
IPv4 Connectivity PASS
Successfully connected to agenciasailorweb.com.br on port 80 over IPv4.

IPv6 Connectivity FAIL
Could not connect to agenciasailorweb.com.br on port 80 over IPv6.
IPv4 Literals
WARN
Could not establish connection to URL .: Agência Sailorweb :. – Just another WordPress site.
 
Back
Top