Search results

  1. shanti

    letsencrypt.sh dns verification on external dns server before proceeding with acme challenge.

    i actually set "MAXTRIES=60" and "DIG_SECONDS=15" but i think i was missing "named_rndc 1" so enabled it and recreated the zone to start clean. now ns-slave sync happens much faster .. resulting in a functional challenge .. i will test if it will work without tweaking the script
  2. shanti

    letsencrypt.sh dns verification on external dns server before proceeding with acme challenge.

    actually it trail&error with $MAXTRIES and $DIG_SECONDS in /usr/local/directadmin/scripts/letsencrypt.sh to no avail yet
  3. shanti

    letsencrypt issues within skin

    the issue took a twist .. this thread is dead - @smtalk : thanks for support
  4. shanti

    letsencrypt.sh dns verification on external dns server before proceeding with acme challenge.

    IMHO validation simply happens too fast .. pre-check starts immediatly - that is ok , but it takes up to 20 secs for the challenge record to appear in local-dns-master-config .. while then the validation-check on 8.8.8.8 is already happening .. not even the nsslaves may have recieved the updates...
  5. shanti

    letsencrypt issues within skin

    please lets resum the letsencrypt=1 option: e.g.: www.onedomain.at points to an ip 1.1.1.2 (serves /home/what/domains/onedomain.at) , the server's main ip is 1.1.1.1 (serves like /var/www) .. please explain: how would a wildcard pointing to 1.1.1.2 find its way into /var/www(/.well-known).. ? or...
  6. shanti

    Login-page enhancement

    hi, the demand would have been to be able to display additional custom contents like an info blog widget next to the login mask. - we will stick with custom login.html page thank you
  7. shanti

    letsencrypt issues within skin

    can you please point us to more details .on "is not recommended to use" . or a hint towards "misconfiguration"... we dont use DA's dns - if that me be important to know
  8. shanti

    Login-page enhancement

    thank you , but since we use a dump of evolutions own login-page as template and the critical part is done locally by js - the options here are limited to none - thats why we call dev
  9. shanti

    letsencrypt issues within skin

    i beg to differ .. letsencrypt=2 is documented as a legit option ( https://www.directadmin.com/features.php?id=1828 ) since 1.50.* .. and it has a reason that this option was choosen due to a complex setup .. since we use SNI for Vhosts over several domains and ips - how can a default ip-address...
  10. shanti

    Login-page enhancement

    i would love to see an option for additional info on the login page: e.g. a js that grabs the last 5 items from a rss-feed into a div siding next to div.login-form like described in https://css-tricks.com/how-to-fetch-and-parse-rss-feeds-in-javascript/ br -c-
  11. shanti

    letsencrypt issues within skin

    hello, i accidently opened a ticket instead of reporting here: ( https://tickets.directadmin.com/ticket.php?hash=kdDMkaSFyrr1IuOwUPaXbNs9MnvCaFON ) in evolutionskin i cannot use wildcard-letsencrypt when letcencrypt is set to "2" in directadmin.conf it may work with with letsencrypt=1 but...
  12. shanti

    issues with symantec-smtp-blocking

    similiar non-DA-responds to this issue: https://www.symantec.com/connect/forums/554-571-ip-symantecs-global-bad-senders-list
  13. shanti

    issues with symantec-smtp-blocking

    IMO it started with a chinese-isp (chinanet.cn.net) who moved our X-ARF-report to spam-folder because they dont care . since they also use symantec services we think that was the reason we got caught by razor .. we since then disabled all X-ARF-reports. ( which cannot not be the final solution)
  14. shanti

    issues with symantec-smtp-blocking

    it only happens on domains protected by this symantec-product. we normally have a clean score on spam-blocklists and actually smtp still only runs at ipv4 on our side. the thread i mentioned is https://www.symantec.com/connect/forums/troubles-ip-reputation both posters on this thread had the...
  15. shanti

    issues with symantec-smtp-blocking

    Hi, Our customers repeatedly have issues sending mails to domains being protected by symantec.cloud. Albeit its always a temporary issue, its such an annoying behavior, giving our customers impressions of bad service. we implemented monitoring for this behavior e.g.: +2020-02-10 14:03:20...
  16. shanti

    [Solved] php.ini locations/load order/best practice.

    with php-fpm: is there a way to address webapp's php.ini only (shared service like roundcube ) without inflicting any other pools ?
  17. shanti

    error building exim-4.93.0.4

    building exim on debian (stretch) actually breaks with: tls.c:23:3: error: #error One of USE_OPENSSL or USE_GNUTLS must be defined for a TLS build though it builds using export USE_OPENSSL=yes any ideas how to fix it ? br -c-
  18. shanti

    OpenSSL 1.0.2u - fixes CVE-2019-1551

    what exactly are the impacts ? what are the bonds relating php5.9 to openssl 1.0 (or any other version like 1.1 )? br
  19. shanti

    roundcube custombuild & composer

    Hello please implement composer-action in roundcubes-custombuild: therefore custombuild should consider templates from custom/roundcube/composer.json furthermore a postbuild command like '$composer update --no-dev -o --apcu-autoloader' should be run postbuild in '/var/www/html/roundcube'...
Top