[RELEASE] Installatron (DirectAdmin auto script installer)

My main server login is not admin but instead it is a variant of that name. Maybe that is part of the problem. I have tried with the server login (yes I do have a domain with that account) but no joy so far.

As well all the other accounts I have on that server myself are either as the server admin or resellers. I tested on 2 different reseller accounts and still got the "No usable domains can be found..." error.

Will get some sleep and try again tomorrow. Love to get this running as I think it is a feature set once in place that will make DA a even more popular and attractive choice for web hosts all over.
 
Eagle1 said:
Since version .6, I haven't had to do that. I just use the admin username i use to delegate the server and it works fine.
Click to expand...
Yes, that was fixed with .6.

And Installation definitely needs an administrative user entered into installatron.sh to function properly :)

On the FreeBSD installation problems, I've updated installatron.sh with the fix for that. Simply re-run installatron.sh if you're on freebsd and having troubles.

Good luck :D
 
iTec said:
My main server login is not admin but instead it is a variant of that name. Maybe that is part of the problem. I have tried with the server login (yes I do have a domain with that account) but no joy so far.
Click to expand...
That setup should work fine. Try re-running installatron.sh as my above post indicates. Good luck. :)

Oh and [I reiterate], rm -fr /usr/local/directadmin/xserv/mod_installatron will get rid of .5.1 if it's still tagging along on your system.
 
Last edited:
?????

I've removed all installatron files, reinstalled over and over and I still get no usable domains. I am using admin which is the admin user of directadmin for my server.

Suggestions ???
 
I'm not sure what to suggest in the way of fixing that error. The login details you specified have to be correct, and you do have at least one domain on your administrative account, right? (You must have at least one domain on the account you're bringing the /HTM_XSERV page up on.)

If you would feel comfortable lending me your root password, along with creating a temporary administrative account in DA for me, I could take a look at what's causing that error for you tomorrow some time. Feel free to PM me.
 
l0rdphi1 said:
I'm not sure what to suggest in the way of fixing that error. The login details you specified have to be correct, and you do have at least one domain on your administrative account, right? (You must have at least one domain on the account you're bringing the /HTM_XSERV page up on.)
Click to expand...
OK Maybe that's it. I don't have any domains on my administrative account. Should I give it one? I don't understand how that would help though. But maybe you can make sense of it. I wouldn't have a problem with letting you in my server. But maybe we wont need to if we can figure out this domain thing.

So the admin account NEEDS to have a domain? Then is that the only account that you can use installatron on? or ??

I'd be happy to contribute a HOW-TO once we get these issues ironed out.

Thx,
Brandt
 
You must have at least one domain on the account you're bringing the /HTM_XSERV page up on.
Click to expand...
What I meant (kudos to Sumaleth): Installatron installs the scripts into domains on the current account, so if you have no domains in your administrative account that isn't a place where you would use Installatron -- it has nowhere to install the scripts. You really want to load iTron when you're logged into an account that has domains created.
 
l0rdphi1 said:
What I meant (kudos to Sumaleth): Installatron installs the scripts into domains on the current account, so if you have no domains in your administrative account that isn't a place where you would use Installatron -- it has nowhere to install the scripts. You really want to load iTron when you're logged into an account that has domains created.
Click to expand...
OK so why do I keep hearing that when you install Itron that you must use an Admin account. I wrote that "When you run installatron.sh enter the name of a user(3) and that users password. Then log into installatron with that user and you will get the option to install under that domain." and Eagle said that it must be done under an Admin account. He seems to know what he's talking about.

So, to clarify... do I need to install installatron for each User (the admin of the domain) ?

thx,
brandt
 
While running *installatron.sh* as root, you MUST enter an administrative account (when prompted).

You may *use* Installatron on ANY user, reseller, or administrative account.

You may *use* Installatron ONLY on accounts that have one or more domains created.
 
Last edited:
AtomicRax said:
Does anyone have an image I could use to link to Installatron in the default skin.
Click to expand...
This probably won't be the final icon we make available, but as a short term stopgap it should work ok:

installatronicon.gif
 
Did you update DA? Any modifications to the default skins are going to be overwritten when DA is updated.

That's another reason why this will be worth it :)

John: ;)
 
No, there have been no updates to DA since this was installed, but I DID update MySQL to 4.0.18.

OpenSSL and grep were updated as part of up2dates maintenance.

I tried removing itron, and re-installing it - no joy.
 
Looking at the error, I'd guess that your skin mods got messed up somehow (overwritten).

I'll take a look, if you like:
l0rdphi1 said:
If you would feel comfortable lending me your root password, along with creating a temporary administrative account in DA for me, I could take a look at what's causing that error for you tomorrow some time. Feel free to PM me.
Click to expand...
 
The 'root/' directory was specifically designed that way - so your public_html/* doesn't get rm -fr'ed when the script is removed :)

However, don't worry, there is a .htaccess file created @ public_html/.htaccess which forces Apache to look inside 'root/' for any unfound documents. This effectively mirrors '/' to 'root/'.

This isn't the best solution, no, but for now it's what I chose. Later on I'd like to keep track of each and every file extracted, and when a script is removed only rm -f those files. We'll see.
 
You must log in or register to reply here.
Back
Top