[tokens] fetching token failed on OpenBSD

[hnhx]

I'm running the latest version of nitter on OpenBSD 7.2-beta (amd64).

When I start nitter I get this error:

[tokens] fetching token failed: No error reported. [tokens] fetching tokens paused, resuming in 30 minutes

I tried decreasing the tokenCount in the config however it didn't really help, same issue.

When I open the nitter instance, the index page works fine, however whenever I try to search for something it just says the instance has been rate limited, I'm pretty sure its not actually a rate limit issue, I think its because it cant fetch the token for some reason.

[zedeus]

Could be that Nitter doesn't run on OpenBSD 7.2, hard to tell from just "No error reported."

[hmsmart]

Experiencing the same on OpenBSD 7.1. Are there any debugging flags that can be used to get more information out of the nitter app than just no error reported?

[hnhx]

I couldn't find any way to fix it on OpenBSD, and it doesn't help that I'm not familiar with the nim language. I have migrated my homeserver to FreeBSD 13.1, Nitter works fine there, it seems to be an OpenBSD only issue.

[jackyzy823]

I think that is a bug of asynchttpclient in nim under OpenBSD.

Even the sample code from nim httpclient module do not work and raise the same error and however the sync http client works normally.

import std/[asyncdispatch, httpclient]

proc asyncProc(): Future[string] {.async.} =
   var client = newAsyncHttpClient()
   return await client.getContent("https://www.example.com")

echo waitFor asyncProc()

[hmsmart]

@jackyzy823 thanks for the additional information. Maybe the issue might be with LibreSSL, since asynchttp seems to work with http requests.

[jackyzy823]

Maybe the issue might be with LibreSSL

Yes.

More detail , the issue might be cause by nim interoperating with LibreSSL in usage of TLS1.3 and non-blocking mode .Thus It would be quite hard to find where the bug is.

I reported a issue to nim. https://github.com/nim-lang/Nim/issues/20144 Hope that some one could help out.

[BitWire]

I also have this issue running nitter:latest in docker on ubuntu 22.04 server. Is there something i can do to help fix this issue? My docker compose file looks like this:

version: "3"

services:

  nitter:
    image: zedeus/nitter:latest
    container_name: nitter
    ports:
      - "127.0.0.1:8082:8080"
    volumes:
      - ./nitter.conf:/src/nitter.conf:ro
    depends_on:
      - nitter-redis
    restart: unless-stopped
    healthcheck:
      test: wget -nv --tries=1 --spider http://127.0.0.1:8080/Jack/status/20 || exit 1
      interval: 30s
      timeout: 5s
      retries: 2

  nitter-redis:
    image: redis:6-alpine
    container_name: nitter-redis
    command: redis-server --save 60 1 --loglevel warning
    volumes:
      - nitter-redis:/data
    restart: unless-stopped
    healthcheck:
      test: redis-cli ping
      interval: 30s
      timeout: 5s
      retries: 2

volumes:
  nitter-redis:

[zedeus]

This was fixed upstream, but you might have to build using unstable/nightly Nim (easy using the choosenim tool).