157

Voyager 1.35.0: New login, pick a server, and signup UI (lemmy.world)

submitted 10 months ago by aeharding@lemmy.world to c/voyagerapp@lemmy.world

9 comments fedilink hide all child comments

Voyager v1.35.0 brings a complete rewrite of the login flow, and adds picking a server and signing up! Check it out! (If it seems familiar, that's because it's inspired from the Mastodon app.)

NOTE: For now, this release will only be available on web and iOS Test Flight. It needs more testing before rolling out to a wider audience. Thanks!

I would appreciate and feedback below in the comments. 😊

Welcome and about

Log in

✨ NEW: Pick server and sign up

you are viewing a single comment's thread
view the rest of the comments

[-] Falcon@lemmy.world 2 points 10 months ago* (last edited 10 months ago)

So I tried adding SSL and I still couldn't get Voyager to work with a self hosted instance.

If anybody has figured out how to get a self-hosted lemmy to work with an app I'd love to know how. For the moment I'm using NodeBB which is fine.

I have Caddy and Lemmy running in containers on an Alpine Box, for which the hostname is "john", it is configured to have a static IP at the router 192.168.1.200. Caddy is set to network_mode: "host".

Here were my steps:

Install bind-utils for dig/nslookup for debugging
On the server install dnsmasq and add address=/john/192.168.1.200

Add the tls internal directive to the caddyfile:

http://lemmy.john {
    reverse_proxy :1236
    }
 https://lemmys.john {
    tls internal
    reverse_proxy :1236
     }

Restart the container
Set the DNS in the WireGuard config on iOS
Use a http server to make the .crt files accessible on the iOS device python3 -m http.server
Install the intermediate profile on the ios device (I installed root, intermediate and lemmys just to be sure)
Open https://lemmys.john in Safari and ensure it loads normally, as a typical site would.
Copy the URL to the Voyager App login

When I try to open it from the account it says "Problem connecting to lemmys.john. Please try again”. It definitely loads fine in Safari, so there must be something particular to the app that I’m missing.

Edit: unless this is an issue with the nginx reverse proxy inside the container 🤔