Possible to connect while outside network with auth?

[ekallevig]

I have ollama and open-webui on my local network and it works well with reins. It would be nice to be able to connect to the ollama instance when outside the network, but I'm not seeing any ways to pass in auth params to the server url. I tried with basic auth (e.g. :@ollama.mydomain.com) but it didnt work. Even better would be to be able to set an auth header so that you could reverse proxy requests through something like open-webui to use their api key functionality.

[rocaltair]

@ekallevig I think you need a socks5 server with auth in your local network, and a socks5 client such as shadowrocket on your mobile.

[networkoctopus]

I'm using wireguard to get home, and also can't add the server at all. Is this intended?

[networkoctopus]

I'm using wireguard to get home, and also can't add the server at all. Is this intended?

ignore this.. I was studidly using openwebuis port instead of ollama. Apologies for adding noise to the thread. Cool app!

[davidstevens37]

+1 a setting to include a bearer token with the ollama request would be a welcomed enhancement.

[davidstevens37]

@ekallevig i've got a similar setup as your by proxying my publicly available domain to my ollama server. It's working great with other ollama client apps, but I like Reins a little more. Until it's updated to include an authorization header or custom headers, i've set it up to access via tailscale and it works well for now. So, in the mean time, you can use tailscale or wireguard to access your ollama server on a private ip while your client is connected. You'll just need to ensure you change ollama server host value, by default, it only listens on 127.0.0.1.

[tristan-k]

+1 Bearer Token.

[u6054623-johnipson]

I was playing around with Basic Auth with a Traefik Reverse proxy. The logs in Traefik are showing auth failure. I tried a different app on iOS that worked with my basic auth url, so i know my server is working, but it seems like Reins is altering the url before trying to connect. A bearer token would be the best option for sure, but in the mean time can we figure out what is happening with the basic auth failure?

[ivaigult]

Is this issue same as #18? I might have resolved that in #43.