It was easy enough to do it with self hosted mastodon, cant seem to login to any of the Lemmy apps with my selfhosted website? Lemmy.rip
UPDATE: I had to renew through a setting in yunohost, not automatic, porkbun was showing it as valid and I I’m used to them grabbing it automatically or having me paste it in during setup.
I had/have no trouble here
Can you access the instance from your phone web browser?
yes https://lemmy.rip/ works fine
https://lemmy.rip/ doesn’t have a valid SSL which might be a problem.
Firefox has thrown a certificate error for me so maybe the app doesn’t trust your certificate?
https://www.ssllabs.com/ssltest/analyze.html?d=lemmy.rip&hideResults=on
After thought edit: try dropping in a Let’s Encrypt cert and see how it goes.
Yeah, I had to renew through a setting in yunohost, got used to panels/managers doing it automatically or letting me paste it in
Mobile apps should allow you to log into any instance. My Lemmy client won’t connect to lemmy.rip either, and fails with the following error:
The certificate for this server is invalid. You might be connecting to a server that is pretending to be “lemmy.rip”, which could put your confidential information at risk.
This is also what I see when I try to connect to lemmy.rip in the browser:
I am able to bypass this warning and see the site in the browser.
Yes you can use lemmy apps to access a self hosted instance, but you will need a real certificate for that to work.
A quick check of Lemmy.rip show it has a self signed certificate, thats not going to allow you to access it easily and my even stop federation from working.
You should be able to get a lets encrypt certificate very easily.
forsure I thought it had one through porkbun but yunohost might be messing with that
It’s 2025. Not having “real certificates” is something admins intentionally do. Since there is Let’s Encrypt available, all other solutions for non-paid certificates are obsolete.
With let’s encrypt and DNS APIs, theres no excuse not to have a real certificate!
More so if you want to have that service interacte with other systems not your own
Exactly. With directly using certbot handling all and everything fully automatically I ran my old setup with a free dyndns subdomain for quite some time without any issues.
Since Let’s encrypt nowadays is basically implemented in every reverse proxy: certificates are an absolute no-brainer.
If someone manages to buy and configure a domain to serve selfhosted content, this person will also be able to either set up certbot or use the built-in functionality of their reverse proxy.
Mine worke just fine, what errors do you get? Does it work from web access?
Is your instance accessible from outside your self host? Does it federate?
