External IP different than DA server IP

A

aphict

New member
Joined
Mar 16, 2021
Messages
3
Hello,

We own a block of IP addresses and I want to use one that is not our default outgoing address. The outgoing IP, which is also the license IP and thus server IP for directadmin, is .132, but because this IP has ports 80 and 443 already in use for a different service, I need to use .134.
Good to know: we're selfhosting on LAN IP, which is listed as the eth0 interface on the server.

What I have done so far:
  • Add the .134 IP as eth0:1 in interfaces config (with gateway .132)
  • Add the .134 IP in Directadmin panel and assigned it to my user (.132 is listed as server, .134 is now listed as owned)
  • Setup DNS for my domain name to resolve to .134, which nslookup confirmed
  • Setup our network firewall to portforward the external IP .134 to the internal IP on both ports 80 and 443
The situation now is that the domain name and external IP .134 correctly forward and display the website when I am doing this on the local network, but outside of the network it does not resolve or forward at all. I've tried flushing my DNS, but it does not seem to make a difference.

What am I missing? Do I need to configure the webserver differently, do I need to change something through Directadmin panel or did I miss something in our firewall settings?

Thank you very much in advance for any replies and help

Edit: some additional info that might help: running on Debian 10.8 with Apache. I installed Directadmin with the standard script by following the official guide.
 
bdacus01 said:
I assume you want to change the da server license to this above IP.

Check here you did all of this


Did you check dns propagation?
flush/restart firewall?
Did you change the ip at the Registrar?

I may think of more but that will get you started.
Click to expand...
Hi Brent,

Thanks for the swift reply.
No, I'm not interested in changing the license IP address from .132 to .134, unless this is necessary? Before using .132 I tried installing Diirectadmin with .134, but it would immediately give me an error that I was not authorized to install from this server. During install the script let's you know your external IP, which in my case is xxx.xxx.xxx.132. I then changed my license IP from .134 to .132, but I want to host my websites on .134.

I hope you understand, but basically it's okay to run the server on .132, but the websites need to be available from .134. It is propagating correctly on the local network (where webserver is hosted), but not on the outside.

No changes were made to the IP, we've owned this block of IP addresses for a few years now.
 
bdacus01 said:
Ah ok


DirectAdmin

DirectAdmin Web Control Panel Site-Helper. Helping you get the most out of DirectAdmin and your web site!
www.site-helper.com

You might read thought these pages. You will need to add whatever IPs you plan to use on the server and in DA. Then assign them to the clients or users
Click to expand...

Thank you. I had already done as described here, so it seems I'm good on that department.
On local network the assigned IP correctly forwards to the user's homepage, so this setup seems to be correct.
But I am not able to reach the websites from outside the network, despite having both network firewall and csf open port 80 and 443.

I'm just lost at how to pinpoint where the problem currently lies, is it my network firewall (this has been tested with a different IP and service and the portforwarding works correctly, so this should be good), the apache config, csf config or something else? Anyone have any experience with this?
 
You must log in or register to reply here.
Back
Top