Karim

The problem is that `url_base` **should be empty** if you're using a subdomain like `jfa.example.com`. Just update your `config.ini`: ``` [ui] url_base = ``` Then restart jfa-go, and it should...

> you can whitelist the telegram accounts which can use log-in to your teldrive instance by adding usernames in config.toml under jwt-allowed-users. just figured out it's already in my config.toml,...

> Whitelist or not, if your instance is public facing, it is **strongly recommended** to put it behind a reverse proxy regardless. > > Caddy + [basic_auth](https://caddyserver.com/docs/caddyfile/directives/basic_auth) with a random...

> I don't understand what you're saying. Your instance is already behind a reverse proxy and won't be accessible to anyone other than your docker host and the container itself....

> Well, you must be doing something wrong, because the whole point of a reverse proxy IS _exactly_ that; to **not** expose the instance directly. You do that by **NOT**...

@devanteweary The integration we’re talking about isn’t just about creating a Jellyseerr account through Jellyfin. It’s about deeper customization and role-based control. In jfa-go, users can be grouped into "Profiles,"...

@hrfee Thanks for the clarification! If the daemon part already handles importing emails and contact methods from jfa-go into Jellyseerr, that’s great. But from what I can see, the current...