Posts by theemstra

Hi,

I checked your certificate file, this seems OK.
The domain is given out for the .de domain, you're trying to load the .eu domain, so that's the problem.

So you can use the .de domain instead or request a new SSL cert for the .eu domain

You can test it yourself, paste your cert (NOT KEY) in here: https://www.sslshopper.com/certificate-decoder.html

Please check what certificate is being served, if you use chrome, click on the green lock, then Details.
You should see the reason it doesn't validate.
You then can click Show Certificate and please show the address + issuer.

Also please check the apache logfiles for your domain.

If this didn't work, post the certificate (not private key) here or in a PM so we can take a look.

Monitorix, Mailgraph, Spamassassin tested with positive result, no errors.
PMARecaptcha tested with errors, reported: http://youtrack.i-mscp.net/issue/IP-1551 (now fully tested and functional)
PanelRedirect, ServerDefaultPage tested positive but with warning on reinstall: http://youtrack.i-mscp.net/issue/IP-1550
PHPSwitcher tested with possible error: http://youtrack.i-mscp.net/issue/IP-1552 Fix en route

Tested with i-MSCP Git 1.3.x on Debian Jessie on XenServer VM
Used Git version of plugins

If you read this part of the error:
Modules::Domain::_loadData: Domain with ID 1 has not been found or is in an inconsistent state
You can start by checking the domain data in the database, is everything where it should be?

It might be wise to hold the upgrade till imscp 1.3.0 is released, because it's more stable, a lot of issues have been resolved since 1.2.17, maybe issues that might affect the migration behaviour as well.

You could clone your old VM to try and upgrade to git 1.3.x and try moving that installation.

There have been 10 posts about this problem already, I try to answer the others and point to the answer, but people, please, use the search function of this forum before posting.

@sport80

What @Nuxwin is trying to say is you can wait for the release of 1.3.0 or you can fix it manually. Your changes will be overwritten on your next upgrade.

This is a known problem, you can wait for the release of 1.3.0 and upgrade to it (it's fixed there), or find the solution I posted on the forums last week.

Hi @Levitas

Please check this link:
http://unix.stackexchange.com/…g-to-add-a-gpg-public-key

There are multiple ways to attack this.

At this moment it's not possible to disable this, but if you submit a ticket I'm sure @Nuxwin or @Ninos will take a look at it for future versions.

Your suggestion would also mean that the email field will no longer be required.

Thanks!