ssl - Nginx install intermediate certificate -


i'm trying install intermediate certificate on nginx ( laravel forge ). right certificate installed, intermediate missing.

i've seen need concatenate current certificate intermediate. best/safest way add intermediate certificate.

also, if install of intermediate failed, can roll previous certificate, , reboot nginx? ( website site live, can't have long downtime )

nginx expects server section certificates in file refer ssl_certificate. put vendor's intermediate certificates , domain's certificate in file. it'll this.

-----begin certificate----- mii... -----end certificate----- -----begin certificate----- mii... -----end certificate----- -----begin certificate----- mii... -----end certificate-----

to make sure okay , avoid downtime, suggest setup nginx locally, add 127.0.0.1 yourdomain.com /etc/hosts, , try open major browsers. when you've verified correct can replicate production server.

when you're done, idea use ssl checker tool verify (e.g. this one). because pre-installed ca certificates may vary depending on browser , platform, can overlook misconfiguration checking 1 os or limited set of browsers.

edit

as @martin pointed out, order of certificates in file important. rfc 4346 tls 1.1 states:

this sequence (chain) of x.509v3 certificates. sender's certificate must come first in list. each following certificate must directly certify 1 preceding it.

thus order is:

  • 1. domain's certificate
  • 2. vendor's intermediate certificate certifies (1)
  • 3. vendor's intermediate certificate certifies (2)
  • ...
  • n. vendor's root certificate certifies (n-1). optional, because should contained in client's ca store.

Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more