Closed VillarosaKeebs closed 1 year ago
I have the same issue, even when I compile it from the source.
All the docker compose logs show
OpenBooks | 2022/12/30 21:42:36 SERVER: Base Path: /
OpenBooks | 2022/12/30 21:42:36 SERVER: OpenBooks is listening on port 80
OpenBooks | 2022/12/30 21:42:36 SERVER: Download Directory: /books
OpenBooks | 2022/12/30 21:42:36 SERVER: Open http://localhost:80/ in your browser.
OpenBooks | 2022/12/30 21:44:02 SERVER: Client connected from 172.21.0.1:56946
OpenBooks | 2022/12/30 21:44:02 CLIENT (thin_development_1): New client created.
OpenBooks | 2022/12/30 21:44:02 CLIENT (thin_development_1): CONNECT Message Received
OpenBooks | 2022/12/30 21:44:19 CLIENT (thin_development_1): SEARCH Message Received
OpenBooks | 2022/12/30 21:46:17 CLIENT (thin_development_1): SEARCH Message Received
OpenBooks | 2022/12/30 22:31:24 CLIENT (thin_development_1): Connection Closed: websocket: close 1001 (going away)
OpenBooks | 2022/12/30 22:31:24 SERVER: Client connected from 172.21.0.1:38012
Slight update, I did some digging and it seems that the Bot that returns search results via @search doesn't return anything. If anyone could confirm this for me as well it would be appreciated.
See #70. I think they've recently decided to ban any usernames / user agents in the format OpenBooks uses.
Connecting directly to the IRC server via HexChat, I'm able to search using @search
That's what I thought, but I can't even search using IRC directly, I tested using Pidgin on Pop OS. I'll have to dig into a possible work around, thanks for the response.
Happy new years!
Sorry to bring this backup but, is there any suggested fix for this? That also stays compliant with irchighway?
lazylibrarian can use our own email and so works. maybe it blocks the email openbooks is using or something?
Latest release requires manually setting an IRC --name
and optionally specifying a --useragent
string. These flags will reduce the chance OpenBooks clients can easily be identified and blocked. See changelog.
Any updates here? Tried —useragent but will not connect.
Installed today using docker-compose and Portainer, but when I open the Web UI and look for a book, I just get a never-ending buffering/loading circle and no books show up. I get an OpenBooks Server Connected on the side so I am unsure as to why this is happening.