Prosody testing installs sans config file and certs

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

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

× 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'.

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

That did the trick, ta very much