Directadmin doesn't work via internet

S

schelte

New member
Joined
Oct 28, 2021
Messages
5
Hi y'all

I have a question, I just started working with DirectAdmin so maybe its a dumb fault but I couldn't find it anywhere

I've installed DirectAdmin on my Ubuntu 20.04.3 LTS server

I can acces my control panel via my local ip (192.168.2.10)
but I can't acces my panel via external ip (86.84.xx.xxx)

the installation completes successful without any errors as far as I can see
at DirectAdmin.com I can see 1 connection

I can acces my server via ssh remotely (ssh [email protected])

but I just can't connect to my hostname:2222 or my external ip:2222


Does anyone know how I can solve this?

Kind regards
Schelte
 
IPv4 address for enp3s4f0: 192.168.2.10
IPv4 address for enp3s4f0: 86.84.xx.xxx

at startup I get this message I don't know if it can be a problem that there are 2 ip's on 1 interface but it might be worth mentioning
 
You might have to search the forums. There are several topics about using Directadmin on a LAN.

Check if you did this correctly:

DirectAdmin Web Control Panel LAN Install Guide

directadmin.com directadmin.com

Next to that, you do need to create port-forwards or set the DA ip as a DMZ ip in the firewall.
Also, to be able to reach your server from your home network, your modem/router needs to support nat_loopback. Most do, but there are still some ISP's out there which do not support that.
In such case you need to test from a friends or family's pc on another location and if that works, change the hostsfile on your local lan pc.
 
Richard G said:
You might have to search the forums. There are several topics about using Directadmin on a LAN.

Check if you did this correctly:

DirectAdmin Web Control Panel LAN Install Guide

directadmin.com directadmin.com

Next to that, you do need to create port-forwards or set the DA ip as a DMZ ip in the firewall.
Also, to be able to reach your server from your home network, your modem/router needs to support nat_loopback. Most do, but there are still some ISP's out there which do not support that.
In such case you need to test from a friends or family's pc on another location and if that works, change the hostsfile on your local lan pc.
Click to expand...
HI richard, Thx for your fast reply!

according to the article you've sent me
DirectAdmin can now run on a LAN without any extra steps.
It previously requierd some non-standard steps to get it running, but now it's automatic

It also says:
  • When it asks for which ethernet device, make sure you pick the device that holds the LAN IP (often eth0, ens192, venet0, etc).
  • Enter the external license IP, and not the LAN ip when asked.
But it didn't ask those 2 questions

I did port forward both ports (22 for ssh and this does work)
but I can't find the problem why 2222 doesn't work, I've tried via 4g that also didn't work
 
schelte said:
HI richard, Thx for your fast reply!
Click to expand...
You're welcome.
Please don't quote full posts, we know what we have written, don't need to read it again. :)

Indeed nowadays DA can run on a LAN without a lot of extra steps which are done automatically now, when the correct install procedure with /auto is used.

I don't work on a LAN, still have to test this yet. Be sure to have the correct external (internet) ip present in your account at the customer portal. The /auto switch will use that as external license ip.

I presume you are able to open DA on port 2222 via the local ip? Or not?
I've found a site where you can check things, including if the correct ethernet device is used by directadmin.

DirectAdmin port 2222 not working - How we fix it!

The main reason for the DirectAdmin port 2222 not working due to the firewall issue, invalid license, incorrect ethernet_dev settings, so on
bobcares.com
 
i'm sorry..

I've followed all steps in that blog but that doesn't solve the problem too?

Yes, I can acces the panel via my local network
 
Phew, that makes it harder.

Oke what about if you disable all firewall so if you do an iptables -L command you only see 3 lines (input, output and forward) with ACCEPTED. Still the same issue?

If yes, then i don't know and we have to wait until somebody who uses DA on a LAN maybe has a clue.
 
Richard G said:
Phew, that makes it harder.

Oke what about if you disable all firewall so if you do an iptables -L command you only see 3 lines (input, output and forward) with ACCEPTED. Still the same issue?

If yes, then i don't know and we have to wait until somebody who uses DA on a LAN maybe has a clue.
Click to expand...
I found the problem!

sometimes you just do stupid things and that's what I did...

I totally forgot I used an extra router in my network to connect my server to and I totally forgot to portforward that router...

Thank you for your help and have a nice day!
 
You must log in or register to reply here.
Back
Top