Additional IPs give error 403 forbidden acces

supdude

Verified User
Joined
Jul 20, 2023
Messages
8
Hello,

I've installed DirectAdmin and trying to setup additional IPv4 and IPv6. Everything works fine with the servers primary IPv4, but whenever I try to add domains using the additional IPs I just receive error 403 forbidden access. I have added the IP addresses in Server Manager -> IP Management. As far as I can read that should be it, but is there more I need to do?

Hope for some help, thanks!
 
Have you checked the procedure to assign the ip's?
Yes, I've added a IPv6. Linked that IPv6 to the server's main IP. I've tried to make the IP global and/or assign it to certain resellers to see if they can create a domain with it. I've gone to Admin/reseller level -> user -> modify and assigned IPv6 from there. So far everything I've done gives any additional IP a 403 error.

I am using LiteSpeed webserver. Can it be something that needs to be configured within that?
 
Last edited:
Linked that IPv6 to the server's main IP. I've tried to make the IP global and/or assign it to certain resellers
I'm not 100% as I'm just starting with ipv6, but if you link an ipv6 to the servers main ip(v4) then it gets a shared ip if I'm not mistaken.

I'm reading here in the docs:
and there it says:
Ensure the Creator of the User has an IP available. Go to Reseller Level -> IP Management.
A linked ip is not a free ip.

If you want it as global shared ip in addition to your ipv4 then you link it like you did, also this is important then.

I was struggling with this too very recently and managed to share an ipv6 finally, you can see my solution here. However, the screenshot is from the Enhanced skin, but I'm sure you can find something similar in Evo.
Maybe you forgot the same thing I was forgetting. You can also read the complete thread.

As for litespeed, I don't use that so can't help you if something is needed there but I don't think so.
 
I'm not 100% as I'm just starting with ipv6, but if you link an ipv6 to the servers main ip(v4) then it gets a shared ip if I'm not mistaken.

I'm reading here in the docs:
and there it says:

A linked ip is not a free ip.

If you want it as global shared ip in addition to your ipv4 then you link it like you did, also this is important then.

I was struggling with this too very recently and managed to share an ipv6 finally, you can see my solution here. However, the screenshot is from the Enhanced skin, but I'm sure you can find something similar in Evo.
Maybe you forgot the same thing I was forgetting. You can also read the complete thread.

As for litespeed, I don't use that so can't help you if something is needed there but I don't think so.
Thanks! I got it to work. Really do not think it is that intuitive how it works.

Do I or the user really manually have to enable IPv6 for every account? Right now for me to get it to work if I create a user with the servers IPv4 address I have to manually assign the IPv6 to the user and the user has to manually assign the IPv6 to his domain. Is this how it is or am I missing something?
 
Is this how it is or am I missing something?
No this would only be like this if all the users would get a seperate ipv6 ip address.

On the server that I have, I linked the ipv6 to the ipv4 and defined it as shared ip. I had to click the ip and then could define that it could be shared amongst resellers.

Once done, then on creating a user, that user automatically gets the A records of the ipv4 and the AAA records of the ipv6.
You linked the ipv6 to the ipv4, not the other way around right?

Seems somewhere something is missing, but as said, I very recently did my first one so I might be missing something too.

Maybe @zEitEr can shed some light on this how to fix?
 
No this would only be like this if all the users would get a seperate ipv6 ip address.

On the server that I have, I linked the ipv6 to the ipv4 and defined it as shared ip. I had to click the ip and then could define that it could be shared amongst resellers.

Once done, then on creating a user, that user automatically gets the A records of the ipv4 and the AAA records of the ipv6.
You linked the ipv6 to the ipv4, not the other way around right?

Seems somewhere something is missing, but as said, I very recently did my first one so I might be missing something too.

Maybe @zEitEr can shed some light on this how to fix?
I think it works now. Truly appreciate your help. I didn't consider how IP-linking worked but thought it was most logical to link the IPv4 from the IPv6, but apparently I had to go into the IPv4 and link the IPv6. I don't see why it is a one-way thing.

Must admit it is not the most logical setup, or that well described in the documentation. Nonetheless, it works now. Thanks!
 
Back
Top