Can't get support ticket help on this

See, now this is what bothers me. I have to expose my ip address and setup in a public forum to get assistance with this. This is a really insecure way to deal with support. I shouldn't have to share that stuff publicly to get help evaluating a product I am going to pay for. This is really frustrating!
 
Brent, I appreciate your help but please don't argue with me. The DirectAdmin support ticket system sent me here for support because they wouldn't give me any to evaluate their own product. Hope ya all get paid for that. Again, I appreciate you but please understand my frustration on this point.

Anyhow, I am just gonna grasp at straws here. in IP manager under device enp0s31f6 this is sort of what I see. should the 192.168.74.32 ip address be enabled? because the 104. address above it is my internet ip and I don't see how directadmin could answer a call if it keeps pointing back to the internet. I dunno... just a guess?

1646932641199.png
 
did setup.sh script ask your any interface ?

in old days, it asks. but now, setup.sh has revoke and change it to non-interaction mode,

try use cmd like this

./setup.sh <license_uid> <license_lid> <hostname> <ethernet_dev>
(maybe it should do it on clean OS)

ethernet_dev should be like "eth0" or your LAN NIC

maybe other member can help you about setup.sh script
 
I can't just go typing commands having come this far. So what do I need to show to get this figured out.
 
Ok, I looked over the DNS in godaddy. I did not have the subdomain setup right compared to others ones from the past. So I have fixed that. I get a response from the server now the only problem is I get the default "Apache is functioning normally" page as if I just went to the ip address it's self. So, it's not pointing to the virtual host for the subdomain.
 
Hope ya all get paid for that.
We dont.
understand my frustration on this point.
I do see you seem to be. Maybe just relax its just a computer..
should the 192.168.74.32 ip address be enabled?
Don't know. I don't use a LAN setup.

There are other aspects other than setting up the server. I am in gentle way I am trying to point them out.. I am not arguing with you I am dialoging with you. There is a big difference in Community based "support" vs real paid company support. The company posts you get community based support for certain licenses and other types have company support. Its because some of the Licenses are super cheap and its not worth it for them as a company to offer support. The thing is we don't work for them, we are just regular folks like you. We cant read your mind or see your screen. We also dont know much about you or your talents as a linux admin. I am sure others will help you and even me when can. Dont get me wrong it a great system once you learn it all. It has a high learning curve. Carry on reading and learning. Sorry if I made you more frustrated.
 
Ok, having gone thru that page. I have it resolving correctly. The problem seems to be in the LAN setup section. the httpd.conf file is using my internet ip address NOT the ip address on the inside the LAN. So, the question is how do I make this so it's using the right IP address? I just went in there manually and set it and it's working.
 
See, now this is what bothers me. I have to expose my ip address and setup in a public forum to get assistance with this. This is a really insecure way to deal with support. I shouldn't have to share that stuff publicly to get help evaluating a product I am going to pay for. This is really frustrating!

Most people do not want there domain hidden. They want people to find their website.
 
Why do you want to argue motives with me?
Not arguing a motive. Just trying to help you see reality. I forgot sarcasm does not translate to other countries sometimes.

Domains are public. IPs are public. Giving away your domain or ip does not make you less secure nor does hiding them make you more secure. Within minutes of your server being online its already being attacked.
 
evaluating a product I am going to pay for.
So you have a trial license then?

DA is for use on hosting servers. It's not intended to be used as a LAN. That this can be done is an extra service, but you can't expect support for that as so many home systems have so many different configurations.

Having that said...
What did you enter in Directadmin as nameservers in the admin section? Because if I'm not mistaken, you have to use local ip's for nameservers and the external nameserver ip's in the reseller section under nameservers. Again, if I'm not mistaken. Did not use a LAN yet, but will do this year for testing purposes.

I presume you have seen this and the links within?
 
Back
Top