[feat] rclone auth token expiry – any way to refresh without constant manual updates?

[paul19920801]

Hi,

I’ve been testing Teldrive with rclone across several VPS machines (7 in total), and I keep running into a recurring issue:

I authenticate by extracting the access_token from the browser cookie and pasting it into my rclone.conf for the teldrive backend.

After some time, the token expires. When I run a simple rclone ls, I get an EOF error, which indicates the rclone auth has expired.

This is manageable on one machine, but across 7 servers it becomes a real pain to constantly update the cookie manually.

Since I rely on Teldrive+rclone for serving media (TV playout), having the auth expire suddenly is very disruptive.

Questions:

Is there currently any way to generate a long-lived rclone auth token for Teldrive?

Can Teldrive support an auto-refresh mechanism (similar to OAuth refresh tokens) so rclone doesn’t break when the cookie expires?

Are there recommended best practices for multi-machine setups to avoid downtime when the token inevitably dies?

Even a short guide or a pointer would be really helpful, as I imagine other users who run Teldrive with rclone across multiple servers are hitting the same problem.

Alternately - does this just expire when rclone has gone idle ie no logging into/uploading files.

Thanks for the great project!

[icumessi]

How long until it expires? There should be a jwt token

[aniel300]

i experienced this recently. any way to automate it?

[icumessi]

i experienced this recently. any way to automate it?

Try to modify ur config.toml file:

[jwt] session-time = "250d" allowed-users = [""] secret = "*****"

[aniel300]

i need to try this. what would happen after 250d?

[icumessi]

i need to try this. what would happen after 250d?

it would reset i suppose

[aniel300]

does this work with the rclone mounts?