In general when using a certificate chain you put the certs one after another in the text file.
So it looks like --- begin cert --- --- end cert --- --- begin cert --- --- end cert --- Then you point the server to the file. Not sure if this is your issue or not? I've always done SSL termination via nginx or apache. On Tue, Nov 25, 2014 at 11:22 AM, James Vann <[email protected]> wrote: > Hi! I have successfully deployed my Django app using uWSGI. I really > like useing it so far, just wish the documentation was better :) > Perhaps I will be able to make my own contributions to this area in > the future :) > > Anyway, i am trying to secure my site with a HTTPS. I found the > documentation on this, got my certificate signed, and tried to install > it. However, my certificate is a chained certificate- and the docs > don't seem to mention this use case at all. > > I tried: > https = :4443,intermediate.crt,temple.crt,temple.key,HIGH > and: > https = :4443,temple.crt,temple.key,HIGH > and: > https = :4443,temple.crt,intermediate.crt,temple.key,HIGH > > and with every variation, i got: > > [uwsgi-ssl] unable to assign certificate intermediate.crt for context > "http-:4443" > or: > [uwsgi-ssl] unable to assign certificate temple.crt for context > "http-:4443" > > Further details: > Ubuntu 14.04.1 > Intel i5 64bit CPU > uwsgi is my webserver > uwsgi version 2.07 > > Let me know if you need anything else :) Thanks so much! > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
