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: The webadmin
SSH
Direct access via physical keyboard/screen Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no
Describe your issue
Got this error this morning and went to run diagnosis in the webmin portal. Got the same result as the email but when I went to the terminal and logged in to SSH -p 3535, it logged me right in. I also ran ncat domain.tld 443 and got a succeeded message. So, I am not sure what is going on with diagnosis. It seems this is a false positive report. Can someone help me with understanding why this is happening as there does not seem to be a misconfiguration here. But, certbot is failing as a result of this incorrect diagnosis which then requires manual intervention.
Tip: Try again after rebooting the server. I recently had a similar problem and spent two days and three nights on it before I found the solution:
For some reason (I don’t know what it was), the YunoHost system’s in-memory database became inconsistent. After the reboot, it was naturally reinitialised and everything ran normally again.
So… just give a reboot a go (if you haven’t already). If it works again, it was probably down to the DB. If not, there are other reasons in your case.
I also double checked Firewall rules to ensure necessary ports were open and doubled checked and verifed sshd_config configuration and configuration is okay wiht correct syntax
Rebooting was one of my first troubleshooting step. Diagnosis is still red lighted for ports (specifically SSH port) and https port. I verified both are working correctly and even tested locally using ncat and externally with a port checker tool as well as just visiting a https site directly.
Weird thing is cert bot threw a red flag for sub1.domain.tld and sub2.domain.tld. When I investigated it shows that sub1.domain.tld was still renewed and when I checked the cert in the browser it shows it was issued today and expires August 11, 2026. However, cert for sub2.domain.tld did not renew and continues to be red lit due tot he diagnosis issue. I am trying to figure out how to fix the diagnosis issue or how to force cert renewal until the issue can be resolved
Yes, that was my mistake… it was my last resort (after I’d realised it must be down to the database). In the past, that might have been my first thought, but somehow I’d got out of the habit of rebooting.
I’m new to server admin space and still learning a lot of valuable lessons here. And Yunohost is a personalized project and the way some of their systems work are custom integrations and doesn’t always follow the same conventions as other systems. So, I am trying to learn as much I can in how they work so I can understand how to integrate things more seamlessly on my own without much assistance. To learn is to grow
Yes, that was my mistake… it was my last resort (after I’d realised it must be down to the database). In the past, that might have been my first thought, but somehow I’d got out of the habit of rebooting.