#1556 Autostart issue with encrypted private key

Reporter Anon Ymus
Owner Nobody
Created
Updated
Stars ★ (1)
Tags
  • Priority-Medium
  • Status-NeedInfo
  • Type-Defect
  1. Anon Ymus on

    What steps will reproduce the problem? 1. Put password protected private key and the corresponding certificate in place (certs folder) 2. Create vhost and add ssl definition to it including the password 3. Power the server off and on again What is the expected output? Prosody should find and load the ssl certificate What do you see instead? "No certificate/key found for <vhost>" What version of the product are you using? On what operating system? 0.11.5 Please provide any additional information below. Starting prosody manually with "prosodyctl start" is working.

  2. Anon Ymus on

    Defining ssl in the global section helped me with this one. Issue can be closed. Thanks

  3. Zash on

    Hey. What exactly did you put in your config? Per-host `ssl` sections are supposed to work.

  4. Zash on

    Hey. What exactly did you put in your config? Per-vhost `ssl` sections are supposed to work.

    Changes
    • tags Status-NeedInfo
  5. Anon Ymus on

    Hello, I put it like this: ssl = { key = "/path/to/key.pem"; certificate = "/path/to/cert.pem"; password = "passwordforkey"; }

  6. Anon Ymus on

    Update: it seems my issue is not resolved different to what I stated earlier. Any ideas what could be wrong? I am not sure anymore about the cause of the problem (Prosody does not autostart on Debian although installed through repository like so https://prosody.im/download/package_repository).

New comment

Not published. Used for spam prevention and optional update notifications.