-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No search results returned #120
Comments
Do you see a "Search Accepted Into Queue" notification in the browser? If not, it's possible you're temporarily banned in the IRC channel. If you enable logs with the |
I don't get the search accepted notification. Logs seem to show that I am connected with some welcome messages, then a list of books followed by:
Then a few PRIVMSG with some ebooks before I stopped the container which showed:
I couldn't see any notification of the search I submitted in the logs. |
Can confirm. I really don't see any error in the logs:
And that's it. Logs:
|
I'm also seeing exactly the same thing since updating to the latest version. Logs have the same as what daedric7 is seeing - Docker log shows the search message received, but the detailed irc log has nothing relating to the search in it. |
It seems to work for me without passing the useragent command. |
can confirm here too. no results are shown and no search query is sent to the irc client according to logs. |
I can confirm the issue is somewhere with Openbooks. I joined the IRC and searches work, Search is answering via Notices, and sending search results via DCC. |
After you posted that I tried again without the useragent string but got the same result. |
not seeing any results or the "Search Accepted into Queue" in browser with following conf
|
The IRC related changes between the latest version and the previous version are minimal. Not really sure of the cause of these issues 🤔. Keep in mind that the IRC channel started to ban OpenBooks clients. This release provides ways to make OpenBooks look like any other IRC client. I know they are able to block specific clients by name pattern. That's the reason for the required It's also possible that they are blocking any clients with "OpenBooks" in their user agent, so do try to use the Lastly, if you've been banned it may take a day or two for the IP blacklist to be removed. Try connecting via a standard IRC client or another device. |
I think you're right that its an IP blacklist issue. I reconfigured to run through a Gluetun VPN container and its working again. |
I would concur with the IP blacklist observation. Even using Colloquy doesn't work unless I go through a VPN. |
trying from multiple remote and local ip's, but no result... |
The command CMD: they will probably fix search once they notice. after the change everything worked in openbooks |
This worked. Thank you!! |
I can confirm search is actively banning the client via IP somehow, even when using a custom useragent. |
I can also confirm, using a different tool (but this issue hit via google search), that the searchbot is blocking IPs. Regardless of client I cannot @search anymore but when I use webchat on mobile/LTE I can search fine. |
Running the latest version 4.5.0 and added both --name "randomuser123" and --useragent "HexChat 2.9.1" to my docker-compose. Docker logs show that client is connected and "CONNECT Message Received". Then I enter a search and see "SEARCH Message Received" but the results are blank. I tried a few popular books so I'd expect to see some results at least. My compose...
Any ideas?
The text was updated successfully, but these errors were encountered: