# Prosody testing installs sans config file and certs

**URL:** <https://forum.yunohost.org/t/prosody-testing-installs-sans-config-file-and-certs/35865>\
**Category:** Support apps\
**Tags:** \_others, xmpp, english\
**Created:** [March 11, 2025, 2:19am UTC](https://forum.yunohost.org/t/prosody-testing-installs-sans-config-file-and-certs/35865 "2025-03-11T02:19:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![wraidd](https://forum.yunohost.org/user_avatar/forum.yunohost.org/wraidd/32/7084_2.png) [@wraidd](https://forum.yunohost.org/u/wraidd)\
**Post date:** [March 11, 2025, 2:19am UTC](https://forum.yunohost.org/t/prosody-testing-installs-sans-config-file-and-certs/35865/1 "2025-03-11T02:19:13Z")

</div>

**What type of hardware are you using** : VPS bought online  
**What YunoHost version are you running** : 12.0.x  
**What app is this about** : Prosody testing

### Describe your issue

Attempted to install prosody from testing branch via `yunohost app install https://github.com/YunoHost-Apps/prosody_ynh/tree/testing --debug`. Install appears to have completed successfully, however there is no `/etc/prosody/prosody.cfg.lua` file so the service can’t actually start. There were also no certs generated. I opted “no” to importing the previous metronome config, if that matters.

Here’s the log of the install: [https://paste.yunohost.org/raw/leguvupibi](https://paste.yunohost.org/raw/leguvupibi)

I’m going to see about finding and using that sample config file to see if that sorts things out but a basic config file seems like the kind of thing the install script should provide, no? Are there other steps I should be taking here?

### Share relevant logs or error messages

```auto
× prosody.service - Prosody XMPP Server                                                                                                                                                     
     Loaded: loaded (/lib/systemd/system/prosody.service; disabled; preset: enabled)                                                                                                        
     Active: failed (Result: exit-code) since Tue 2025-03-11 01:59:17 UTC; 38s ago                                                                                                          
   Duration: 13ms                                                                                                                                                                           
       Docs: https://prosody.im/doc                                                                                                                                                         
    Process: 440193 ExecStart=/usr/bin/prosody -F (code=exited, status=1/FAILURE)                                                                                                           
   Main PID: 440193 (code=exited, status=1/FAILURE)                                                                                                                                         
        CPU: 10ms                                                                                                                                                                           
                                                                                                                                                                                            
Mar 11 01:59:17 domain.tld prosody[440193]: **************************                                                                                                                 
Mar 11 01:59:17 domain.tld prosody[440193]: Prosody was unable to find the configuration file.
Mar 11 01:59:17 domain.tld prosody[440193]: We looked for: /etc/prosody/prosody.cfg.lua
Mar 11 01:59:17 domain.tld prosody[440193]: A sample config file is included in the Prosody download called prosody.cfg.lua.dist
Mar 11 01:59:17 domain.tld prosody[440193]: Copy or rename it to prosody.cfg.lua and edit as necessary.
Mar 11 01:59:17 domain.tld prosody[440193]: More help on configuring Prosody can be found at https://prosody.im/doc/configure
Mar 11 01:59:17 domain.tld prosody[440193]: Good luck!
Mar 11 01:59:17 domain.tld prosody[440193]: **************************
Mar 11 01:59:17 domain.tld systemd[1]: prosody.service: Main process exited, code=exited, status=1/FAILURE
Mar 11 01:59:17 domain.tld systemd[1]: prosody.service: Failed with result 'exit-code'.

```

---

<div class="post-metadata">

**Author:** ![anubis](https://forum.yunohost.org/user_avatar/forum.yunohost.org/anubis/32/9218_2.png) [@anubis](https://forum.yunohost.org/u/anubis)\
**Post date:** [March 11, 2025, 1:14pm UTC](https://forum.yunohost.org/t/prosody-testing-installs-sans-config-file-and-certs/35865/2 "2025-03-11T13:14:25Z")

</div>

Thanks for your report! This bug is occurring _some_ times, we are working on it; in the meantime you will find the workaround here : [missing /etc/prosody/prosody.cfg.lua after installation · Issue #11 · anubister/prosody\_ynh · GitHub](https://github.com/anubister/prosody_ynh/issues/11#issuecomment-2508901928)

---

<div class="post-metadata">

**Author:** ![wraidd](https://forum.yunohost.org/user_avatar/forum.yunohost.org/wraidd/32/7084_2.png) [@wraidd](https://forum.yunohost.org/u/wraidd)\
**Post date:** [March 11, 2025, 7:17pm UTC](https://forum.yunohost.org/t/prosody-testing-installs-sans-config-file-and-certs/35865/3 "2025-03-11T19:17:18Z")

</div>

That did the trick, ta very much

---

<div class="post-metadata">

**Author:** ![system](https://forum.yunohost.org/uploads/default/original/2X/f/f59fe8e3ee6b100b4f574d30d6e30479c68b89f0.png) [@system](https://forum.yunohost.org/u/system)\
**Post date:** [March 26, 2025, 7:17pm UTC](https://forum.yunohost.org/t/prosody-testing-installs-sans-config-file-and-certs/35865/4 "2025-03-26T19:17:36Z")

</div>

Closed on March 26, 2025, 7:17pm UTC

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.