Posts by kess

Für dieses Problem ich habe ein hook geschrieben. Du findest dieses hook im Forum

@Nuxwin
I know you already converted the old DB passwords, and I also know that if you run the conversion script multiple times it will break things. My last post was meant in the way of providing some temporary kind of script that could convert (only once) the wrong FTP passwords that @Dylan has at present. Just to resolve the specific present problem.

My last post was not something negative on your work, instead I just have to tell you THANK YOU for the work you do for free for us. Because of that, I just wanted to help out someone with a problemt (with all my personal limits).
I really like i-MSCP and if I can be helpful for someone I do it with pleasure.

Once again @Nuxwin thank you very much for your work

@Nuxwin
I just posted how I did my migration procedure and how it worked for me.
I started with version 1.1.1 because at that time it was the last available version.
I don't have at present a new server to test directly with version 1.1.11, but for the password problem, I think that it could be resolved with some scripting that converts old style passwords in the new style...

Sent from my iPad using Tapatalk HD

I've also migrated one of my old servers from ispcp to i-mscp, but not to the last version.
Procedure:
1. Migrate from ispcp 1.0.7 to i-mscp 1.1.1
2. Upgrade to i-mscp 1.1.3
3. Upgrade to i-mscp 1.1.5
4. Upgrade to i-mscp 1.1.9
5. Upgrade to i-mscp 1.1.11

When you migrate to i-mscp 1.1.1 you'll have a problem with the customers rebuild, you'll find the fast solution here:
Migration from ispCP to i-MSCP - Failure

After all the steps are performed in the correct way, you'll have a fully functional migrated system. Before migrating ispcp, I also migrated squeeze to wheezy...

Hope it helps,
bye Kess.

Same for me...
But if I use my encrypted key and I provide my password everything seems to work in the correct way.

Perhaps if you post your log: /var/log/imscp/SSLcertificate_module_sub.log .........

Nuxwin replied to that issue in the past.
You can find the solution to your/my problem here: Override FQHN check

Bye Kess.

Sorry for my fast reply, it was done with my mobile.

If you invoke the command "perl imscp-autoinstall -d" your installation will be upgraded, nothing will be lost

To return to your problem, you have problems in sending e-mails because you try to identify yourself with the HELO/EHLO command that says for example "I am imscp.myhostserver.com" and I'm contacting you from IP address 1.2.3.4, but the RDNS of IP 1.2.3.4 resolves to someting different from "imscp.myhostserver.com". that's why you have to ask to configure your RDNS record.

Hope it was useful for you and for Others.
Bye Kess.

The RDNS record is provided by your datacenter provider. You don't have to configure it for every domain hosted in your server, but only for your server itself.
Server Fqhn resolves to IP
IP resolves to Fqhn hostname
Server FQHN is equal to Helo/Ehlo

Error corrected, it was not Plugin related.
Just disabled the Monitorix builtin httpd_builtin Server, restarted Monitorix service and now everything is OK.

I hope that this could help someone else.

bye Kess.