Posts by rgabor73

    Hello,


    I have purchased the plugin PHPSwitcher yesterday. While I was able to install it and see it under Administration area, I am not able to compile any of the PHP version.


    I tested the following commands:

    Code
    1. perl php_compiler.pl all
    Code
    1. perl php_compiler.pl --auto-setup 7.1


    Both command return the following error:


    Code
    1. checking for icu-config... no
    2. checking for location of ICU headers and libraries... not found
    3. /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/Makefile:368: recipe for target 'configure-7.1-stamp' failed
    4. [ERROR] main: An unexpected error occurred: An error occurred while executing the install MAKE(1) target for php-7.1.11: aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
    5. ../configure: line 5383: test: too many arguments
    6. configure: error: Unable to detect ICU prefix or no failed. Please verify ICU install prefix and make sure icu-config works.
    7. make: *** [configure-7.1-stamp] Error 1


    I am not sure what is ICU for, but as far I can tell, it is installed.



    I have tested the solution in the following article but did not solve the issue:


    Error Compiling PHP Versions for PHP Switcher


    Can someone guide me on how to fix this please?


    Thank you.

    Hello FloRet88,


    I am not sure if you are right or not.


    I have followed exactly what was wrote by I_MSCP admin:


    --------

    I. Usage of i-MSCP DNS server (You've choosen bind9 for DNS server during i-MSCP setup)


    Here, I assume that the domain abc.com has been already created in the i-MSCP panel.


    • Your customer must register a glue record through the namecheap.com registrar interface: ns1.abc.com -> <ip>. Note that this can be take a bit time to be recorded.
    • Once that the glue record is ok, your customer must change the DNS server through the namecheap.com registrar interface. Here, he must use ns1.abc.com

    Note that the <ip> tag must be replaced by the IP that you assigned to the customer when you have created the domain through the i-MSCP panel


    Note also that here, I've described the usual procedure. Some registrars make the procedure more simpler. E.g, when you change the nameserver, they also register the glue record into the Registry.


    For namecheap, see:


    --------


    If bind9 was selected during I_MSCP setup, then I presume I_MSCP should manage the issue. I do not see anything in I-MSCP documentation saying that I will have to manually go to my ubuntu settings to make my nameserver working.


    I have another domain registered via Namecheap, and I also followed exactly what mentioned above, and still, I am able to ping the nameserver I have created, but unable to ping the main domain.

    Hello All,


    First of all, Happy new year to you all.


    I am not a DNS guru at all, and since 3 weeks now I am trying to create my own Name Server to be used with my domain, however I am always failing to accomplish that.


    Can someone help me and point me to the right direction?


    This is how my setup looks like now. Let say my domain is domain.com


    Domain name is registered via Godaddy. I am using http://freedns.afraid.org/ where I can create all record needed to point domain to my server. So at this stage, Name Servers for the domain.com is setup to use the one from afraid.org


    Al working with this setup.


    However, I would like to set this up to look more professional, so I want to have a name server like NS1.DOMAIN.COM


    I have found similar articles related to I_MSCP, but for some reason did not work for me: How to configure DNS for a target Domain


    This is what I tested with.


    Under Godaddy, manage DNS for the domain.com, I have created two hostname. NS1 and NS2, which pointed to my server.


    After a while, I was able to ping NS1.DOMAIN.COM and the correct IP was displayed.


    Once this hostname was confirmed to work, I have changed the DNS of domain.com, and pointed to use my own CUSTOM nameservers, the NS1.DOMAIN.COM and NS2.DOMAIN.COM


    I waited 48 hours for the change to take affect, but then nothing worked anymore.


    I was still able to ping NS1DOMAIN.COM or NS2.DOMAIN.COM


    However I was unable to ping DOMAIN.COM. ping was not able to resolve the domain.com


    On my server, DOMAIN.COM is correctly added. I also tested and created DNS ressource record such as A, MX records for this domain, but did not fixed the issue.


    So based on above link: Usage of i-MSCP DNS server (You've choosen bind9 for DNS server during i-MSCP setup) -> This is how my setup looks like, but still not working.


    Can someone help me out and let me know what I am doing wrong?


    Thank you.


    Regards,

    Gabor

    For future reference, it's nice to post what you did to resolve the issue.

    Would you be able to let us know how you resolved the issue for future reference?

    I have done what was suggested


    "No, that will not fix the issue... You should stop to do things without thinking..."


    It was a really helpful support, so I posted my solution the same way.

    Well, i have done what was suggested. run installer with reconfig option.


    This has not fixed the issue, but created a new one.


    All working but having this message : unable to get update info from github


    I do not see any info about this in the forum, so not sure what should I think.


    However, based on eror message, the issue is:


    Failed to execute git clone --mirror '[email protected]:roundcube/Net_Sieve.git'


    Will look into that

    I have an error popup as well when I log into the dashboard:


    unable to get update info from github


    Looks like all working, but the plugin cannot be activated, uninstalled or anything


    I have already run the following, but issue remain.

    Code
    1. perl imscp-autoinstall -d


    I think I will switch back to Currier, then remove all dovecot I installed manually as that might cause these issues. Then I run the installer with reconfig again to see if that fix it or not