Does it expect TLS, so https:// by any chance?
Jerboa
Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Built With
Features
- Open source, AGPL License.
Installation / Releases
Support / Donate
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
Crypto
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK
- ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01
- monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV
- cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
Yeah, I was a bit worried about that. Currently it doesn't have TLS enabled. I might have to have a valid certificate and everything, which would be annoying. If I don't get a silver bullet other than this, I'll probably see about going that route.
Edit: Yeah, looks like this is probably the case. It seems Jerboa only wants to connect to port 443, no matter what I put in the instance box and openssl s_server
on 443 with just any old random certificate gives SSL alert number 46
which basically means Jerboa won't trust the certificate. So, I think my path forward is to make my server do the whole TLS thing with a valid certificate. Thanks everyone for the input!
self signed is an option if strict checking is not enforced by the client... or perhaps certbot to the rescue? if you run a public facing DNS server, certbot-dns-rfc2136 requests would allow you to create certs for any host you want (even internal ones)
If it's all in docker, you probably need the docker container name as the target host. Assuming your docker network isn't in host mode.
I've got Docker forwarding the ports to my host system, though. And I'm trying to connect Jerboa from a separate device that wouldn't know Docker is even involved. That connection works fine from a browser, so it doesn't seem to me like the hostname could possibly be the problem.