What type of hardware are you using: VPS bought online
What YunoHost version are you running: Latest, what curl https://install.yunohost.org | bash installs. I can’t find a specific version.
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 ?: No. Vanilla AWS Lightsail Debian 12.8, 2gb memory, 2 vCPUs
Describe your issue
Installation goes just fine. But I get no useable response from YunoHost. It just hangs. Here are my steps:
- Setup AWS Lightsail instance (Debian 12.8 / 2gb memory, 2 vCPUs)
- ssh to instance
- sudo -i
- curl https://install.yunohost.org | bash
- override SSH = Y (I also tried “N”. Same result)
Installation works (note LDAP errors in log section, but nothing reported from the installer. I get this:
│ You can perform this step, either: │
│ • from the command line, by running 'yunohost tools postinstall' as root │
│ • or from your web browser, by accessing : │
│ - https://172.26.8.202/ (local IP, if self-hosting at home) │
│ - https://44.242.220.217/ (global IP, if you're on a VPS) │
When I point my browser at https://44.242.220.217/ it just hangs. If I point my brower to 44.242.220.217 without the https:// it redirects to https://44.242.220.217/yunohost/admin but then still hangs.
I get responses curling it from inside the VPS:
root@ip-172-26-8-202:~# curl localhost
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
root@ip-172-26-8-202:~# curl localhost/yunohost/admin
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
root@ip-172-26-8-202:~#
I’ve blown away the VPS and reinstalled several times. Just for grins, I installed apache2 instead of YunoHost & it worked fine.
Any help would be greatly appreciated! Thank you. This project is amazing!
Share relevant logs or error messages
Interesting bits in the installation log include:
Job for slapd.service failed because the control process exited with error code.
See "systemctl status slapd.service" and "journalctl -xeu slapd.service" for details.
invoke-rc.d: initscript slapd, action "start" failed.
× slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)
Loaded: loaded (/etc/init.d/slapd; generated)
Drop-In: /usr/lib/systemd/system/slapd.service.d
└─slapd-remain-after-exit.conf
Active: failed (Result: exit-code) since Mon 2025-01-20 21:14:07 UTC; 22ms ago
Docs: man:systemd-sysv-generator(8)
Process: 47098 ExecStart=/etc/init.d/slapd start (code=exited, status=1/FAILURE)
CPU: 9ms
Jan 20 21:14:07 ip-172-26-8-202 systemd[1]: Starting slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)...
Jan 20 21:14:07 ip-172-26-8-202 slapd[47098]: No configuration file was found for slapd at /etc/ldap/slapd.conf. ... (warning).
Jan 20 21:14:07 ip-172-26-8-202 systemd[1]: slapd.service: Control process exited, code=exited, status=1/FAILURE
Jan 20 21:14:07 ip-172-26-8-202 systemd[1]: slapd.service: Failed with result 'exit-code'.
Jan 20 21:14:07 ip-172-26-8-202 systemd[1]: Failed to start slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
