What type of hardware are you using: VPS bought online What YunoHost version are you running: 12.1.39 How are you able to access your server: SSH Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: Joplin install
Describe your issue
During the installation of Joplin, the Yunohost console stopped responding, and SSH access was also interrupted. After restarting the server, it turned out that Nginx does not start due to:
Nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
The web console for the domain name also did not respond after the restart, and I saw “Welcome to Angie” at the ip address.
I don’t know if I did the right thing, but I managed to solve the problem by disabling the Angie service and restarting Nginx.
What was that? Up to this point, no applications, including Joplin, have ever had such consequences if the installation failed.
This looks like Joplin’s installation process pulled in Angie (an Nginx fork) as a dependency, which then conflicted with YunoHost’s existing Nginx service — both trying to bind to port 80 at the same time. Disabling Angie and restarting Nginx was actually the right call to restore your server.
To make sure your system is fully clean, it’s worth running the command suggested above to check if Angie left behind any APT sources: grep -r angie /etc/apt/sources.list.d/
If any Angie entries show up, remove them to prevent future conflicts during system updates. Also, as jarod5001 mentioned, sharing the full Joplin install log from Tools > Logs in the YunoHost admin panel would help confirm whether the installation actually completed before the server was restarted, or if it needs to be run again cleanly. Joplin is resource-heavy during install, so giving it more time on future attempts before restarting the server would be advisable. Hope that helps get everything sorted!