Install scripts for applications

3 posts / 0 new
Last post
#1 Sun, 11/18/2007 - 15:08

Install scripts for applications

Joe, I gave up on the FreeBSD because I couldn't get past a error in the setup. Spent all day building Centos5, got it running and have hit the same error. I must be overlooking something simple, but I cannot figure it our.

I installed a fresh CENTOS5. Ran the install script for the pro version with wget as directed on the license page. Created a test domain. Tried to install wordpress, clicked on install script option, selected wordpress from list of available scripts, click on the "Show Install Options" button and the right panel disappears and will not come back. I have to log out of webmin and log back in to see anything in the right panel.

"Show Install Options" does not work for me, and I cannot see any way to actually make the script available to the virtual domain. Cn you point out what I'm missing?

I canned my FreeBSD install because of the same problem. Maybe I did the freebsd install right after all but just need someone to point out what I'm missing?

thanks<br><br>Post edited by: SteveAcup, at: 2007/11/18 15:46

Mon, 11/19/2007 - 11:36

Let me propose an answer to my own question:

make sure your server has a FQDN and that the DNS/reverse DNS for your domain is current. If DNS cannot resolve your server's IP address to the FQDN, then the install script function will not work.

Is this approximately the right answer?

I added the server name to my DNS record, and suddenly the install scripts function works fine. I'll have to dig out the hard drive with my attempted FreeBSD install and see if the same fix takes care of it.

Amazing what you can come up with when sleeping on a problem.

Mon, 11/19/2007 - 15:09 (Reply to #2)
Joe's picture

Hey Steve,

You're definitely onto something. Many, many, many, many functions in Virtualmin need for name resolution to work. The will be quite angry and refuse to install if it doesn't detect a FQDN, but it doesn't do a lot of checking beyond seeing that the name looks FQDN. I plan to make it more angry in the future, because it does lead to so many potential problems to not have a FQDN (and if it has a FQDN but that name actually resolves somewhere else or not at all, the problems are sometimes subtle).

Thanks for the update.


Check out the forum guidelines!

Topic locked