teldrive: Bug:cant login

image It keeps loading when I am useing qrcode login(and phone login)

device: raspberry pi 4b log:

2024/12/27 18:58:38 goose: no migrations to run. current version: 20241213121739
27/12/2024 06:58 PM     INFO    Started server http://localhost:8080
27/12/2024 06:59 PM     INFO    /       {"status": 200, "method": "GET", "path": "/", "query": "", "ip": "10.0.0.212", "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36", "latency": 0.02276598, "time": "2024-12-27T10:59:00Z"}
27/12/2024 06:59 PM     INFO    /api/auth/session       {"status": 200, "method": "GET", "path": "/api/auth/session", "query": "", "ip": "10.0.0.212", "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36", "latency": 0.000419903, "time": "2024-12-27T10:59:00Z"}
27/12/2024 06:59 PM     INFO    /login  {"status": 200, "method": "GET", "path": "/login", "query": "redirect=%2F", "ip": "10.0.0.212", "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36", "latency": 0.000210942, "time": "2024-12-27T10:59:20Z"}
27/12/2024 06:59 PM     INFO    /api/auth/session       {"status": 200, "method": "GET", "path": "/api/auth/session", "query": "", "ip": "10.0.0.212", "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36", "latency": 0.000209683, "time": "2024-12-27T10:59:20Z"}

config:

[db]
data-source = "postgres://teldrive:xxx@127.0.0.1:5432/postgres"


[jwt]
allowed-users = ["xxx"]
secret = "xxx"

[tg]
app-id = "xxx"
app-hash = "xxx"

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

I don’t think so as call to database is made after login is successful i.e whenever telegram client returns session auth key.

image It turns out the issue was my mistake—I initially downloaded the ARM version instead of the ARM64 version. The problem occurs when using the ARM version, but my Raspberry Pi runs a 64-bit OS. After switching to the correct ARM64 version, everything works as expected. I apologize for that.

Ntp clock support will be added in next build days I have to write some integration tests after adding openapi support which will fix this problem.