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

  • @Falcon
    link
    English
    910 months ago

    Is there a way to join a self hosted instance that isn’t federated?

    My friends and I have a small Lemmy at my place with WireGuard. No ssl though.

    • @MimicJar
      link
      English
      610 months ago

      I’m just guessing, but I don’t see why not.

      The current UI allows you to enter any server, and not every server federates with everyone else.

      I sort of assume SSL as part of the bare minimum, but you can test today and find out, no need to wait for this release.

      • @Falcon
        link
        English
        110 months ago

        Oh no I’ve tried quite a few apps. Both mastodon and Lemmy.

        I tried a reverse proxy, no dice. A self signed ssl is the next step.

        Any help is appreciated!

        • @kernelle
          link
          English
          310 months ago

          Use certbot, able to register and auto renew certificates. For easy mode you could use cloudflare, though I’ve learned the Lemmy back-end struggles with cloudflare sometimes, but there are workarounds as well, try it out!

    • @aehardingOPM
      link
      English
      210 months ago

      Https is required, but custom servers are otherwise allowed.

      • @Falcon
        link
        English
        2
        edit-2
        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:

        1. Install bind-utils for dig/nslookup for debugging
        2. On the server install dnsmasq and add address=/john/192.168.1.200
        3. Add the tls internal directive to the caddyfile:
          http://lemmy.john {
              reverse_proxy :1236
              }
           https://lemmys.john {
              tls internal
              reverse_proxy :1236
               }
          
        4. Restart the container
        5. Set the DNS in the WireGuard config on iOS
        6. Use a http server to make the .crt files accessible on the iOS device python3 -m http.server
        7. Install the intermediate profile on the ios device (I installed root, intermediate and lemmys just to be sure)
        8. Open https://lemmys.john in Safari and ensure it loads normally, as a typical site would.
        9. 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 🤔