I recently self-hosted Voyager and it was a very painless process, I’m very pleased!

I noticed some strange behavior: When I navigate to my Voyager instance from Chrome, everything works as expected. When I install the PWA from Chrome, the list of Lemmy instances doesn’t match my CUSTOM_LEMMY_SERVERS variable; it’s the same list as vger.app. Then, if I navigate from Chrome to my Voyager instance, the list is now also the same as vger.app. None of this happens if I install the PWA from Firefox (it seems that Firefox installs PWAs differently from Chrome though; it doesn’t show up on the app drawer, for example).

I suspect the PWA doesn’t actually come from my server when I install it from Chrome. Is this what’s happening? Or am I doing something wrong?

EDIT: this issue is now fixed, build the Docker image from the source code to try it out. Thank you @aeharding@lemmy.world!

  • elvith@feddit.deEnglish
    2·
    1 year ago

    Maybe it’s a bug with vger, maybe a cache/Chrome thing but it might also be a config issue.

    When a web app wants to be installable, it needs to serve a file that tells the browser some things about itself - the manifest. If you visit your own instance on your server and take a look at the HTML source code in the browser (or use the dev tools), you should see a line like this:

    <link rel="manifest" href="/manifest.json">

    This tell the browser where to find the manifest. If you open said file, it should contain a line with the start link that gets invoked when you start the PWA. In this file, you should see a line like this with the link:

      "start_url": "/?source=pwa",

    Make sure that this link points to your installation and not to vger.app

    As I don’t host vger myself, I don’t know if and how you can change the values there or what should be the correct link, but this might get you started to track down the error.