Well what i can i say that direct admin is really pain in the ass, twice i asked in their forum but it was queued for moderation then not published. i'm having a problem setting up my domain 100% correctly.
let me explain more:
Before 1 or 2 weeks, i re-build the server and installed direct admin, but its really harder than other panels and i couldn't figure it 100% how to do, my website now is running but i have the following problems
1- domain name can not be solved by all people. when i try to ping it it says its not resolvable, while the domain opens for most of users except for very few which gives an error saying can not connect to server
2- i get this error when using intodns.com [url] while everything else is ok
3- some of users in some countries access home/admin/domains/sharedip/... while others access home/admin/domains/mydomain.com/... which is the correct one, this causes problems but i temporary solved the problem by uploading files into both folders
As in recent threads i have posted about getting a DA lifetime licence within the next month. I currently get my domains from 123-reg but i am just wondering if someone could help me or if they have an answer to my question!
If i bought a domain from 123-reg and then got a lifetime licence from DA and had it installed onto my server what happens to the nameservers? Like when DA install it onto my box would they sort out the nameservers for my domain aswell like ns1.mydomain.com, ns2.mydomain.com or would i have to pay extra for them?
Just been thinking and currently i host all my services with other hosting companies like my web hosting accounts etc...but was thinking of buying a DA licence and installing it onto one of my linux servers.
On DA's website it says one licence per IP or something along them lines...does this mean if i was to install a licence on say 99.99.99.999 and it was working ok etc but then if i changed my IP range to 99.99.99.998 would that mean the DA licence would no longer be valid?
I don't start a CPanel vs DA war, but need to get a "what might be different" list re a VPS.
When I got my present VPS (moved from shared hosting) I had it initially set up with DA. All my previous experience had been with CP on my shared hosting account, but I had read about CP being a bit of a resource hog.
When I tried to set up my VPS, I got it wrong. I ended up with 2 instances of "mymainsite.com" on the server. I got so confused talking with support and their UNIX lingo, that I had them switch to CPanel.
I'm probably going to move to another host and thinking of using DA to save RAM.
I'm not a reseller of hosting, just have 20+ small to very small sites. I have a number of mySQL databases that get a fair number of queries. I have 1 vBulletin app but the traffic on that site is VERY low.
So what will I need to learn differently in DA?
-cron jobs -parked domains -migrating sites -backing up sites
there seems to be some debate over which admin panel is the best.
I not looking for anything amaazing in sence of features and add on scrpts. I want it to put hardly any stran on the server and just provide and easy interface for setting up domains, emails databases and ftp accounts.
I've just had a quote for a VPS that seemed good value for money until the cost of a Direct Admin license was added ($15 extra).
Looking at DA's pricing the cheapest license you can buy is an internal license (in bulk) which is available to server providers only at 9$ a month.
If that is the case why is it that quite a few providers in the offers forum are providing DA for 5$ or 6$?
As these licenses are being offered on low end VPS with tight margins anyway, I can't understand how they can afford to make a loss on the control panel (if they are in fact).
Due to a typo at the comand line as Root, ive manages to change the owner ship of unknown mounts of files.
The command that was processed (Before it was complete)
chown -R reseller:reseller /
I managed to stop the process ctr+c and these were the last files to see fly past. The last one in the list is where it stopped at.
Code: chown: changing ownership of `/proc/11566/task/11566': Operation not permitted chown: changing ownership of `/proc/11566/task/11566/fd/0': No such device or address chown: changing ownership of `/proc/11566/fd/0': No such device or address chown: changing ownership of `/proc/11572': Operation not permitted chown: changing ownership of `/proc/11572/task/11572': Operation not permitted chown: changing ownership of `/proc/11572/task/11572/fd/4': No such file or directory chown: changing ownership of `/proc/11572/task/11572/cwd': Operation not permitted chown: changing ownership of `/proc/11572/fd/4': No such file or directory chown: changing ownership of `/proc/11572/cwd': Operation not permitted chown: changing ownership of `/etc/X11/X': No such file or directory chown: changing ownership of `/dev/core': Operation not permitted chown: changing ownership of `/usr/local/include/libpng/libpng12':
Too many levels of symbolic links
At the moment the server is still running and it seems only to be log in issues with Direct admin. All user / reseller / Admin accounts can no longer log in.
Error after logging in : Unable to determine Usertype user.conf needs to be repaired No images or nothing
i have a problem i have dedicated server with direct admin panel so i was trying to change the skin to see how it looked but what a surprise it kick me out and now its blank and i cant get in to the directadmin panel anymore with this error msg "Error: document not found"
I am currently setting up my server, and are experiencing some problems.
Some of the mails sendt with the php mail() func, ends up in the mail queue in DA, and I get the following error log in DA:
2009-06-04 20:36:02 Received from <> R=1MCHnG-0005uQ-9v U=mail P=local S=1344 T="Mail delivery failed: returning message to sender" 2009-06-04 20:36:02 routing failed for admin@vmnd001.local <admin@munnbind.net> F=<>: Unrouteable address 2009-06-04 20:36:02 routing failed for admin@vmnd001.local <admin@munnbind.net> F=<>: Unrouteable address *** Frozen (delivery error message)
This only happens with some email domains though. If I set the recipient to my yahoo mail, it works as a sharm, but when I set my other email (<<removed>>) as recipient, i get the error log above.
I've heard a internet bandwidth service from Equinix named Equinix direct, how about the quality of this service? Does there somebody have the experience of this service?
Does Level3 have a monthly minimum of some sort? I currently own a dialup internet service provider, buy through a dialup reseller that mainly uses the Level3 managed modem service, and would like to deal with them directly if possible. I am also interested in their collocation services and ip connections in the future.
I have a website which has a FLV player serving .flv files which are hosted in the server. I notice that some users are directly downloading the files using the direct URL and they seem to be using download managers for that which is opening several Apache connections and open slows down Apache. I want to prevent this. I thought of preventing it using a .htaccess file but did not help. This is what I used:
<Files *> order allow,deny allow from 127.0.0.1 allow from localhost deny from all </Files>
I thought this would work but it doesn't as it is blocking the FLV player from playing the file. Can anyone tell me the right way to do it?
I am currently coding a backend to my website where clients can login and view their webmail, stats, etc.
What I am after is a script that will link my clients directly through to awstats, without going through cpanel or having to re-enter their username/password through the htaccess popup.
Does anybody know if I can pass the un/pwd combo through in the url string to popup the stats in the correct manner?
I had a site with admo.net. To my surprise the name registration was done in their name and not mine so domain name cannot be taken with you. When your hosting date expires the domain was directed the day it expired to a porn site without a renewal notice or warning. It was not until after I requested the name only renewal that a renewal email arrived. The date on the renewal was marked due over 10 days after it had already expired. In the mean time all the visitors looking for me were directed to porn links.
One problem: All my old files and folders are owned by ROOT so that means my SU account named XXX cant edit/add/delete anything from my SFTP because of folder/file permission.
Is there anyway my SUDO(wheel) account can still edit these files own by ROOT?
I tried to disable direct root login but had to struggle to find step-by-step instructions and have written the steps one needs to follow to disable direct root login.
This is an additional security measure where we prevent direct root logins and instead create a user to login and then use a command ‘su –‘ to gain root privileges.
The only risk in this procedure is that you may prevent root login but forget to add the user to the wheel group - effectively locking yourself out of the system.
Follow the steps below and you will not face a problem.
STEP 1: Let us create a user and add it to the wheel group.
For e.g. we want to create a user neonix and give him root privileges.
SSH into your server as root and follow the below commands to create a user.
groupadd neonix
useradd neonix –gneonix
passwd neonix
enteryouruserpasswordhere
verifyyouruserpasswordhere
// Please note -g in the second line
// You can replace neonix with any username of your choice.
STEP 2: Add user to wheel group.
Use your browser to Login to your WHM panel and click on Manage Wheel Group Users.
You will see the user you just added (neonix). Select the user and click ‘Add to group’.
You will see that the user has been added – Users Currently in the wheel group root,neonix
You have successfully added a user to the 'wheel' group who will be able to 'su -' to root.
LOGOUT OF SSH
Before we disable root login, let us check if the user can login and su – to gain root privileges.
SSH into your server as 'neonix' Login as: neonix Password : enteryouruserpasswordhere su – password: enter root password here
You have successfully logged in and have root privileges. Now let us disable root login.
STEP 3: Disable Direct Root Login
(The below steps are from webhostgear.com)
1. Copy and paste this line to edit the file for SSH logins pico -w /etc/ssh/sshd_config
2. Find the line Protocol 2, 1
3. Uncomment it (Remove #) and change it to look like Protocol 2
4. Next, find the line PermitRootLogin yes
5. Uncomment it (Remove #) and make it look like PermitRootLogin no
6. Save the file Ctrl+X then Y then enter
7. Now you can restart SSH /etc/rc.d/init.d/sshd restart
Now, no one will be able to login to root with out first logging in as 'neonix' and 'su -' to root, and you will be forcing the use of a more secure protocol.
