the IPv6 is now updated with 2a02:4780:e:ef07::1
What did they say about that previous IPv6 address?
And, the IPv6 is still not providing the same response as the IPv4?
curl -Iik6 http://woodlandbiz.net/
HTTP/1.1 200 OK
Date: Sat, 17 Jun 2023 07:27:35 GMT
Server: Apache
Last-Modified: Thu, 18 May 2023 01:41:18 GMT
Accept-Ranges: bytes
Content-Length: 163
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0
Content-Type: text/html
curl -Iik4 http://woodlandbiz.net/
HTTP/1.1 301 Moved Permanently
Date: Sat, 17 Jun 2023 07:27:40 GMT
Server: Apache
Location: https://woodlandbiz.net/
Content-Type: text/html; charset=iso-8859-1
2 Likes
i'm trying to access my website -> but in the certificate it shows login.woodlandbiz.net
I have no idea what is going on within WHM.
I can only speak on what I can see from where I'm typing.
2 Likes
What shows?:
sudo apachectl -t -D DUMP_VHOSTS
certbot certificates
2 Likes
sorry what does this do and what i need to do ?
Do you have SSH access to the server?
If not, what does this "yes" mean?:
If you do have SSH access, then type in these commands and show their outputs:
sudo apachectl -t -D DUMP_VHOSTS
certbot certificates
2 Likes
[it's almost 4am here - taking a much needed break - I'm sure someone else will pickup where we part]
Cheers from Miami 
2 Likes
Tq for your help
1 Like
For some reason, the IPv4 and IPv6 webserver configurations are completely different still.
The IPv4 configuration seems to be redirecting from HTTP to HTTPS and then some other stuff to /logout and has a valid wildcard certificate configured.
The IPV6 configuration currently has a self signed cert installed for login.woodlandbiz.net and does not redirect from HTTP to HTTPS at all.
This is kinda weird to me, because usually the IPv4 and IPv6 configurations do not differ for a webserver: usually they are exactly the same.
So why there are so many differences with your IPv4 and IPv6? I don't know. Are those IP addresses actually pointing to the same server at the moment?
3 Likes
@adrian26 If the discrepancies that @rg305 and @Osiris have found are actually created by the hosting provider, then the errors that you're seeing are probably the hosting provider's responsibility, even though they seem not to want to admit it or investigate it in detail so far. There's probably nothing that you can do on your own to fix the problem, other than getting the hosting company to investigate further.
This is not necessarily true (like if you didn't follow their documentation or instructions properly when configuring your DNS settings) but it's looking likely to me.
4 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.