Posts by Nuxwin

    It's with great pleasure that we announce the immediate availablity of i-MSCP 1.1.0-rc1.3, which is a Fast bugfix release.


    This release addresses the following issues:


    Setup

    • Fixed: Any hook function should return 1 on failure
    • Fixed: Do not install suexec module when using ITK
    • Fixed: Make fcgid as default FastCGI module
    • Fixed: Self-signed SSL certificate for i-MSCP must be a wildcard SSL certificate
    • Fixed: Self-signed SSL certificate for i-MSCP must use 2048-bit RSA Keys (Minimum recommended)
    • Fixed: Suppress warning for self-signed certificate generation (still in log file)
    • Fixed: Use of uninitialized value in bitwise or (|) errors


    Furthermore, all languages files were synchronized with the last available versions on Transifex.


    We would like to remind you that this version should not be used in a production environment, and that any bugs found should be reported on our issues tracker.
    Feel free to test this new version and get in touch with us about any improvement that you would like see integrated.


    See http://forum.i-mscp.net/Thread…released?pid=9084#pid9084 for more information about new features and fixes integrated in the 1.1.0-rc1 release.


    Download:
    https://sourceforge.net/projec…les/i-MSCP%201.1.0-rc1.3/


    Thanks you for using i-MSCP.

    Re ;


    Ok so now, I'll be able to close the related ticket #547 and begin the release process of the 1.1.0-rc1.3 (fast bugfix release).


    BTW: Step 2 is only valid in case you are using external DNS server.


    Thanks to you Hase for time spend with me. I can now continue my job in peace.


    Thanks you for using i-MSCP


    Hmm, ok.
    Could you get this in the Wiki for Other Namecheap Users? Because the DNS Settings i use, are Standard for this Provider. (allready talked to their Support) Also the Standard Settings worked on Plesk ans cpannel


    Edit: Ok, im waiting :)


    Could you install teamviewer on your desktop and then, I can check your server directly ? Normally, with the records you already have, this should work without problem even if in roundcube the hostname for imap is set as imap.control.myinterface.info.


    I'm really curious to investigate on your server to get answer about the things that are causing this resolution problem.


    BTW: You can see all what I do via teamviewer.

    You already added these entries as A record:


    Code
    1. root@imscp:/var/cache/bind# dig smtp.control.myinterface.info @192.168.5.100; <<>> DiG 9.7.3 <<>> smtp.control.myinterface.info @192.168.5.100;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47939;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 0;; QUESTION SECTION:;smtp.control.myinterface.info. IN A;; ANSWER SECTION:smtp.control.myinterface.info. 248 IN A 62.141.46.188;; AUTHORITY SECTION:myinterface.info. 993 IN NS dns2.registrar-servers.com.myinterface.info. 993 IN NS dns1.registrar-servers.com.myinterface.info. 993 IN NS dns4.registrar-servers.com.myinterface.info. 993 IN NS dns3.registrar-servers.com.myinterface.info. 993 IN NS dns5.registrar-servers.com.;; Query time: 20 msec;; SERVER: 192.168.5.100#53(192.168.5.100);; WHEN: Fri Dec 14 07:34:11 2012;; MSG SIZE rcvd: 179



    So, that should normally work without problem.

    Ok, it's not really a bug. You are using exotic configuration and you should configure your DNS server correctly. can you do that:


    On your registrar interface (dns management), try to add the following CNAME records:


    smtp.control.myinterface.info. IN CNAME smtp.myinterface.info.
    imap.control.myinterface.info. IN CNAME imap.myinterface.info.


    Save changes. Ensure you see the new records:


    dig smtp.control.myinterface.info
    ...


    Rerun i-MSCP installer to get roundcube imap and smtp hostname values as set by us.


    Try to connect and send/receive mail via roundcube.


    Edit WAIT