Your browser doesnt like your certificate. You setup the networking correctly because its able to get the certificate.
this post was submitted on 13 Sep 2023
16 points (90.0% liked)
Selfhosted
38789 readers
339 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Did you try doing any searching on the error message before posting here? That's an SSL error. Most likely due to you using a dns name that doesn't match the cert being provided by the server.
Yes, I did. It appears that the server is not even providing any cert at all to the browser, which is why this fails.
This looks to be a problem within the Yunohost software that generates the self-signed cert, so nothing I can do about it from the outside. I have posted an error report to the Yunohost forum.
I think if there was no cert at all, the server would fail to start in the first place.
Also I would consider trying to use openssl to see what's actually happening since the browser can sometimes obfuscate things in it's attempts to be helpful.
openssl s_client -connect :443
I'm with @[email protected] in that the server should fail to start if there was no certificate to load. It's more likely that the server is providing an invalid cert. Using the openssl command above would help you identify that.
That's odd. Do you not get the advanced option to proceed anyway and load the page?
If you add an exception for the cert what happens?
The browser does not offer the option of excepting this error. It straight up refuses because the host does not provide a certificate.
You could point the DynDNS to your first server, generate a valid SSL certificate with letsencrypt, then move DynDNS and the certificate to the new server.
As per your update, the problem with the server is generating certificates, right?
Yeah, the problem is that the server is down supposed to do it all on its own and when that doesn't work there's no good way to hack it without confusing the clever system.... It would then be forever a manual process.
Better to let the Yunohost Dec's sort it out internally.