Si if I configure the IPTABLES to block certain ports on some of my IP Addresses, it should not interfere with anything, right?
Why is it possible to change the IP Address on the Service port page if it has no effect? It can be a little misleading.
Is there any link between the "Service ports" page, and the firewall of the system?
I see that, when looking at the system's iptables, the ports listed in the "Service ports" page are present.
When I change the listening IP address for a port, nothing changes though, the port stays open on all IP addresses
for on the server.
For security reasons, I need to close all ports except the https and http ones on all IP addresses but one.
Is there a way to do it directly from the IMSCP config panel or via IMSCP config - without the risk of a later conflict or of the configuration
getting reset, or do I have to tweak the iptables myself?
I have used the second listener, and it seems to be working.
The perfect solution.
Thanks for the reply.
But, I am not looking to set it up per client. I need the panel itself to use our relay servers.
It has been a long time since I've been here, and since I've started using IMSCP.
I have moved into another company a couple years ago, and I have moved away from the hosting needs for a long time.
Now, I am looking into setting up a hosting platform for my actual company, and after comparing different solutions my choice
has once again moved over to the latest version of IMSCP
Mostly everything is working the way I need it to:
- We have our own DNS servers, and I am able to use them for the websites we host.
- We have our own DB servers, and I am able to use them.
- We will be needing different PHP versions to be managed by the same hosting server, and I found the way to do it.
But, there is one issue I can't really grasp without changes to the code, which is the the possibility to use our external e-mail servers.
Basically, I need to set the postfix's relayhost to our own relay SMTP server, and enforce it for all my users/customers.
All the files where I can change the value say that I should not change them manually, so where am supposed to do it?
Yeah, I know.
The upgrade should go along fine, I just need the time to test it in testing environment.
Yes, I have a lot of data, and every upgrade just shuts down ALL services at once for the whole duration of the upgrade, from what I've seen (I have other servers, with different, recent, versions of i-MSCP, and even without any modifications on some of them the upgrade is simply taking too long... on some, the users have +1TB of e-mails alone, plus all data in webfolders).
The changes I've made are quite simple, and I'm looking into redoing them with plugin/hook files in some near future.
Problem solved. I have managed to recreate the databases and users thanks to Ninos' post.
I am planning to upgrade, yes, but last time I made an upgrade I ran into segfaults and a very long downtime because of (an unnecessary) chown of ALL e-mails on the server.
For a web-hosting platform, a long downtime because an upgrade locks down all of the services at once instead of doing it progressively, and stopping them only when really needed, is quite dangerous...
So, I'll have to find the time to do it that will not inconvenience my users (accessing different services from different timezones).
Also, I have some custom modifications (separate mail server but still managed by i-mscp, and several others) that I need to take into account before starting a "blilnd" upgrade. Add to that multiple separate hosting
servers, and you see what nightmare it can become...
It would be a welcomed change if the upgrade (and rebuild) process could be split down into several ones, without causing complete downtime of all services for the whole duration of the operation...
All mails and websites exist.
The server that got destroyed was a separate MySQL one.
I have all the customers' backups, and the main imscp database.
Using the imscp-setup --reconfigure sql script, the system is correctly configured for the new machine.
But, I'm missing dovecot, pma, vsftp, and mainly the correct mysql database (with users...).
So... if I go with imscp-setup -b, from scratch, it should work? Last time I tried, I have spend hours repairing several problems because it kept segfaulting...
I have a critical situation.
I'm running i-mscp 1.1.0-rc4.7.
The OS is Debian Wheezy.
My MySQL server has crashed (physical breakdown, data inaccessible).
I have the nightly backup of all users' databases, and the imscp main one.
But have lost everything else (mysql users, roundcube, etc...).
Can't recover them.
Is there a way to rebuild the database?