Hi there,

Yes, I'm online although at work so not always possible to react at once. I'm not familiar with CentOS, so I might be mistaking. If I am then I'm sure someone will correct me.

The following file contains the hostname on my RHEL
IP configuration is set up in
If you set up the network using the NetworkManager on the GUI, then it's a different story and I don't have experience with that.

Kind regards,

Eric

Only change that will cause error to ISPConfig becuase some configuration of ISConfig is point to the previous hostname and IP. If we only change that and reboot, ISPConfig won't be able to join to the system.

I don't have access to an ISPConfig install right now but you could check the config files of ISPConfig or rerun the install script to change the hostname and such.

Kind regards,

Eric

I know you are busy. You already help me a lot. So just follow up this issue if you have time. I can wait.

Ok, thanks for the understanding and patience. I'll have a look at it when I'm home since I still have the CentOS installed.

Kind regards,

Eric

Hello,

I completed the install yesterday following the same manual and doing exactly the same, that is using the same hostname. Then after stalling ISPConfig I wanted to change the hostname and IP. I just deleted the temporary folder I created to extract ISPConfig, changed the hostname and IP configuration and performed the install of ISPConfig from scratch an it worked.

So you can change hostname and IP but you'll just have to run the ISPConfig script again.

Kind regards,

Eric

Will it destroy the old configuration and web hosting?

Hello,

It's of course always a good idea to backup everything you have already configured. I haven't tested that since I didn't configure any clients or websites on it. But copy the config files from ISPConfig and make a dump of the MySQL database before you run the install again. If things get overwritten then it's easy to recover from the backup.

Kind regards,

Eric

I remember that it take 15 minutes to 30 minutes to install ISPConfig2 from installation script. It would be easier to make small change of configuration file. The owner of ISPConfig might be able to answer this question. I have to look for them, I think.

One more question. Many websites host in the same ip address. They point to the same ip address. But why they can go to different website? What is the unique identity? Is it port number?

You could change the ISPConfig files manually also as far as I know to reflect the changes you made to your system. Also using phpmyadmin or another tool you can change the references in the MySQL database.

There are different ways to set up multiple websites behind one IP, for example using virtual hosts in Apache, a reverse proxy using Squid, etc...

Kind regards,

Eric

Hmm, not sure. Let discuss about my current ISPConfig Web Server.

I have one more urgent problem. Now my web server is working well. I created some website and they work well. Now I want it to work in public(internet). I ready bought a domain. But I'm not sure how to make it work. My local network and internet is separate by a firewall(SmoothWall Express 3.0). We have a public ip that already forward to a Web Server(another web server) through port 80. I'm not sure if I can use that public ip address for 2 web servers by using some kind forwarding in the firewall. Hope you understand what I was saying and to find a solution as soon as possible.

Hello k_oudom,

Great you got it working. You'll need the domain to point to your WAN IP. If you want it to automatically connect to the new webserver, you'll have to either connect to a different port (8080 for example) or you could also put a reverse proxy between the firewall and your LAN so you can use your one IP for multiple sites/applications.

Kind regards,

Eric

I'm glad to hear that it is possible for 2 web servers to use 1 WAN IP address. But I don't know how to do it with reverse proxy. I don't understand reverse proxy. Anyways, I know some about forwarding port. The 1st web server is already use WAN IP to forward http port 80. So the default port can not be used for the 2nd web server(my new web server). If I use port 8080 for http. Then I will have to use http://mydomain.com:8080 to access my web site. It doesn't look good.

I know that doesn't look good but if you don't have another option...

But the reverse proxy with Squid isn't that difficult, there are great examples on the internet and I have set it up couple of weeks ago and is running smoothly in a production environment. You could install Squid for example on the same server you're using as webserver, although then you'll have to change your webserver to listen to another port but nobody will notice that. It's of course easier to have another machine on which you can install Squid and put it in the DMZ of your firewall.

Kind regards,

Eric