Jump to content

eva2000

Members
  • Posts

    23
  • Joined

  • Last visited

Posts posted by eva2000

  1. Right now I am Blesta local testing server with GoGetSL sandbox api in place and started creating package group and packages from GoGetSSL sandbox api.

     

    Once this is all setup I eventually plan to backup database and restore on a live server instance. But all those package products are pulled from the GoGetSSL sandbox api. Is it as simple as just change the api token from GoGetSSL sandbox to non-sandbox GoGetSSL api tokens for live usage ? Or are all those existing and restored package products tied to just the sandbox api ?

     

    cheers

     

    George

  2. cheers Mike - should of read this thread before venturing off into package creations..

     

    seems GoGetSSL module has a bug, GGSSL Wildcard is not selectable and not available from dropdown menu

     

     

    hmmm GoGetSSL says the problem is at Blesta module end and not GoGetSSL and that they don't control the actual GoGetSSL module for Blesta !

     

    so don't know which end it is.. is there an extended debug verbose mode / logs that I can check ?

  3. I'm on 30 day Blesta trial license and even after first few hours of using Blesta I am liking it :)

     

    I setup the trial on my local virtualbox guest server instance right now. But decided to do the latter part of testing on real live server online. So is moving the Blesta install during trial license period the same as normal full license ? I have different domains though ?

    • Virtualbox local instance uses /etc/hosts made up name = newdomain.com
    • Live instance will use a proper domain = orders.mydomainname.com or something and use https/TLS

    Or is trial tied to that newdomain.com name now ?

     

    thanks

     

    George

  4. For my situation for SSL and renewal notifications, say if a client's email becomes invalid over the 12 months before renewal. Then when blesta system sends a renewal notification to that clients invalid email and it bounces back. How does Blesta handle that ? 

     

    Invalid emails to department emails which require a client will get an email saying:

    Our system received your email, but was unable to process it for one of the following reasons..
    
    1. The email address you sent the message from does not belong to any of our clients and this department only allows existing clients to open tickets.
    
    2. You replied to a ticket notice, and we are unable to determine what ticket number you are responding to.
    
    3. The department you emailed no longer exists.
    
    Please open a ticket at: http://blesta-hostname.com/customers/plugin/support_manager/client_tickets/departments/
    

    Is that what you asked for mate?

    Wouldn't sending an email to an invalid bouncing email have no effect ?

     

    Is there any notice on front end client log in area that notifies the client his email is invalid and needs updating ?

  5. Does Blesta do anything with regards to bounced email handling ? invalid client emails etc ? How to verify or check client emails are valid and working over time and not just at registration/order time ?

     

    thanks

     

    George

     

     

  6. I just setup a package group (retail ssl) and associated packages for SSL with retail prices which was quite a bit of manual work.

     

    Now I want to setup a 2nd package group (discounted ssl) with exact same packages as retail ssl group but with discounted prices. Is that the correct way ? Is there any option to just clone the package group and packages under a new package group name and then edit the prices for discounted ssl group ?

     

    thanks

     

    George

  7. Not sure if Blesta has such features, but would be great if we can create preset welcome email templates and preset defaults (year vs month, preset package member groups) which can be selected at time of package creation/setup. Saves alot of typing/copy/paste :)

  8. cheers Mike - should of read this thread before venturing off into package creations..

     

    seems GoGetSSL module has a bug, GGSSL Wildcard is not selectable and not available from dropdown menu

     

    post-11219-0-83246900-1432554685_thumb.p

     

     

  9. Hi I am using Blesta 30 day trial on a local virtualbox test server instance for GoGetSSL module.

     

    Once I have all package groups, packages and order forms setup on my local virtualbox install, can I export and import those into a live licensed Blesta install on a live server ? Any tools for that ?

     

    Or is it just treated live an entire Blesta instance server move ? Even if the domain name for Blesta instance is different ?

     

    thanks

     

    George

  10. Sadly there's only the documentation here, there will be some here: http://docs.blesta.com/display/user/Modules soon can I help you with anything mate?

     

    I guess it's double the confusion being new to both Blesta ( only used for a few hours today) + new to using GoGetSSL blesta module. Don't know where to begin for setting up the SSL products within Blesta admin area :o

     

    Only setup my sandbox GoGetSSL and sandbox Paypal APIs and Amazon SES for smtp emails. Was hoping there's some documentation for setting up GoGetSSL products - especially mass imports or setups as opposed to having to add each product manually one by one :)

  11. thanks Serge.. I got it working and it was something you reminded me to do, I forgot to restart php-fpm service after making the changes ! :lol: LOL I was only restarting Nginx !

     

    it works now with backend admin nav links with friendly urls :)

     

    There seems to be a few Centmin Mod LEMP stack users on this forum using Blesta, so here's the nginx vhost I have for my Centmin Mod LEMP stack's Nginx vhost

    # Centmin Mod Getting Started Guide
    # must read http://centminmod.com/getstarted.html
    
    # redirect from non-www to www 
    # uncomment, save file and restart Nginx to enable
    # if unsure use return 302 before using return 301
    #server {
    #            listen   80;
    #            server_name newdomain.com;
    #            return 301 $scheme://www.newdomain.com$request_uri;
    #       }
    
    server {
      server_name newdomain.com www.newdomain.com;
    
    # ngx_pagespeed & ngx_pagespeed handler
    #include /usr/local/nginx/conf/pagespeed.conf;
    #include /usr/local/nginx/conf/pagespeedhandler.conf;
    #include /usr/local/nginx/conf/pagespeedstatslog.conf;
    
      # limit_conn limit_per_ip 16;
      # ssi  on;
    
      access_log /home/nginx/domains/newdomain.com/log/access.log combined buffer=256k flush=60m;
      error_log /home/nginx/domains/newdomain.com/log/error.log;
    
      root /home/nginx/domains/newdomain.com/public;
    
    location ~ (\.pdt) {
    return 403;
    }
    
    location / {
            try_files $uri $uri/ /index.php?$args;
    }
    
      include /usr/local/nginx/conf/staticfiles_blesta.conf;
      include /usr/local/nginx/conf/php.conf;
      include /usr/local/nginx/conf/drop.conf;
    }
    

    for /usr/local/nginx/conf/staticfiles_blesta.conf include file it's just created from default /usr/local/nginx/conf/staticfiles.conf with a css and html context locations commented out

    cp -a /usr/local/nginx/conf/staticfiles.conf /usr/local/nginx/conf/staticfiles_blesta.conf
    
        location ~* \.(3gp|gif|jpg|jpeg|png|ico|wmv|avi|asf|asx|mpg|mpeg|mp4|pls|mp3|mid|wav|swf|flv|exe|zip|tar|rar|gz|tgz|bz2|uha|7z|doc|docx|xls|xlsx|pdf|iso)$ {
            gzip_static off;
            #add_header Pragma public;
            add_header Cache-Control "public, must-revalidate, proxy-revalidate";
            access_log off;
            expires 30d;
            break;
            }
    
        location ~* \.(js)$ {
            #add_header Pragma public;
            add_header Cache-Control "public, must-revalidate, proxy-revalidate";
            access_log off;
            expires 30d;
            break;
            }
    
    #    location ~* \.(css)$ {
    #       #add_header Pragma public;
    #       add_header Cache-Control "public, must-revalidate, proxy-revalidate";
    #       access_log off;
    #       expires 30d;
    #       break;
    #        }
    
    #    location ~* \.(html|htm|txt)$ {
    #       #add_header Pragma public;
    #       add_header Cache-Control "public, must-revalidate, proxy-revalidate";
    #       access_log off;
    #       expires 1d;
    #       break;
    #        }
    
        location ~* \.(eot|svg|ttf|woff|woff2)$ {
            #add_header Pragma public;
            add_header Cache-Control "public, must-revalidate, proxy-revalidate";
            access_log off;
            expires 30d;
            break;
            }
    

    Guess next step is SPDY/3.1 SSL http://centminmod.com/nginx_configure_https_ssl_spdy.html :)

  12. Hi I just started a 30 day trial for Blesta 3.4.3 to see if it's suited for my use on my Centmin Mod LEMP stack based Nginx/PHP-FPM/MariaDB setup.

     

    Installation went fine but with friendly nginx rewritten urls came across an oddity that from forum search, I don't think I've come across.

     

    friendly urls is enabled by setting lib/init.php

     
    // define("HTACCESS", file_exists(ROOTWEBDIR . ".htaccess"));
    define("HTACCESS", true);
    
    
     
    And then i've tried everyone of this forums nginx rewrite formats populated throughout this forum via search and all result in the same.
     
    Front end client side links work as friendly urls when clicked direct to right place
     
    i.e.
    However, backend admin urls within ONLY the nav links are NOT friendly urls and when clicked redirect to front page at http://newdomain.com
     
    i.e.

    these all redirect to front page at http://newdomain.com when clicked when define("HTACCESS", true); is set. If I unset define("HTACCESS", true);, then those links in nav area work
     
    Backend admin urls NOT within nav links work as friendly urls though
     
    i.e. these work
     
    So is it something to do with the template or links coded in nav links ? As I tried every version of nginx rewrite rules found on this forum and the same odd symptoms outlined above occur in all instances ?
     
     
    Some screenshots on localhost install
     
    post-11219-0-43705200-1432535004_thumb.p
     
    post-11219-0-45482700-1432535005_thumb.p
     
    post-11219-0-34977400-1432535006_thumb.p
     
    System config
    • CentOS 7.1 64bit
    • Virtualbox 4 with Centmin Mod LEMP stack
    • Nginx 1.9.0
    • PHP-FPM 5.4.41
    • MariaDB 10.0.19
    • CSF Firewall

    Nginx config

     

     

    nginx -V

    nginx version: nginx/1.9.0
    built by gcc 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) 
    built with OpenSSL 1.0.2a 19 Mar 2015
    TLS SNI support enabled
    configure arguments: --with-ld-opt=-Wl,-rpath,/usr/local/lib --sbin-path=/usr/local/sbin/nginx --conf-path=/usr/local/nginx/conf/nginx.conf --with-http_ssl_module --with-http_gzip_static_module --with-http_stub_status_module --with-http_sub_module --with-http_addition_module --with-http_image_filter_module --with-http_secure_link_module --with-http_flv_module --with-http_realip_module --with-http_geoip_module --with-openssl-opt=enable-tlsext --add-module=../ngx-fancyindex-ngx-fancyindex --add-module=../ngx_cache_purge-2.3 --add-module=../headers-more-nginx-module-0.25 --add-module=../nginx-accesskey-2.0.3 --add-module=../nginx-http-concat-master --with-http_dav_module --add-module=../nginx-dav-ext-module-0.0.3 --add-module=../openresty-memc-nginx-module-1518da4 --add-module=../openresty-srcache-nginx-module-ffa9ab7 --add-module=../ngx_devel_kit-0.2.19 --add-module=../set-misc-nginx-module-0.28 --add-module=../echo-nginx-module-0.57 --add-module=../lua-nginx-module-0.9.16rc1 --add-module=../lua-upstream-nginx-module-0.02 --add-module=../lua-upstream-cache-nginx-module-0.1.1 --add-module=../nginx_upstream_check_module-0.3.0 --with-openssl=../openssl-1.0.2a --with-libatomic --with-threads --with-stream --with-stream_ssl_module --with-pcre=../pcre-8.37 --with-pcre-jit --with-http_spdy_module --add-module=../ngx_pagespeed-release-1.9.32.3-beta
×
×
  • Create New...