So I was able to install everything correctly, but I don’t know what I’m supposed to do in order for people that don’t have my same IP to see my files. I’d like to share my Jellyfin server with some friends so they can see movies there. I’ve already open the ports, but they can’t still access them, I’m using elementaryOS Hera which is built on Ubuntu 18.04.4 LTS.

    • ghost_laptopOP
      link
      fedilink
      arrow-up
      1
      ·
      4 years ago

      Instead of 127.0.0.1:8096 I should input my public IP, right?

      • xe8
        link
        fedilink
        arrow-up
        1
        ·
        4 years ago

        No, leave that as 127.0.0.1:8096 as long as you haven’t changed the port from 8096.

        • ghost_laptopOP
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          4 years ago

          (base) user@user-MS-7A15:~$ caddy reverse-proxy --from http://example.duckdns.org --to 127.0.0.1:8096 2021/03/12 22:18:21.149 WARN admin admin endpoint disabled 2021/03/12 22:18:21.149 INFO http server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server {"server_name": "proxy", "http_port": 80} 2021/03/12 22:18:21.149 INFO tls.cache.maintenance started background certificate maintenance {"cache": "0xc00043f0a0"} 2021/03/12 22:18:21.149 INFO tls cleaned up storage units reverse-proxy: loading new config: http app module: start: tcp: listening on :80: listen tcp :80: bind: permission denied

          Should I run that as sudo, right?

              • xe8
                link
                fedilink
                arrow-up
                1
                ·
                4 years ago

                Hmmm on your router you may need to add another rule for port 80. Do exactly what you did before for port 443. Add a rule for the IP your jellyfin server is running on, then enter port 80 in both of the port fields.

                • ghost_laptopOP
                  link
                  fedilink
                  arrow-up
                  1
                  ·
                  edit-2
                  4 years ago

                  I didn’t create any type of .json file or something like that for Caddy like that forum post or the documentation says, could that be doing something? Also I realized I didn’t save the router config for port 443, I just saved it and ran it but it still gives me the same error, maybe it takes a bit to update.

                  I’m going to do that now, though.

                  Edit: Just opened port 80, still the same error. U_U

                  Edit 2: Thanks for being so patient and helping me.

                  • xe8
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    edit-2
                    4 years ago

                    I’m not sure…

                    Actually when you run the caddy command remove the https:// at the start. Just input example.duckdns.org (but with your actual url).

                    I struggled a bit with my setup too. I think I ended up manually editing the Caddy config file at some point.

                    Edit: No worries. Hopefully someone more knowledgable than me will chime in to help us! :-)