View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006434 | unreal | ircd | public | 2024-07-17 21:08 | 2024-08-26 08:16 |
| Reporter | srhuston | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | Linux | OS | Alpine | OS Version | 3.20 |
| Product Version | 6.1.7 | ||||
| Summary | 0006434: Central API fails to find server | ||||
| Description | I've tried numerous times to register with the API server to be able to use the blocklist and contribute to it, however it never succeeds. Previously I would get a connection, but then the webpage would timeout and fail after that without moving to whatever the next step is. Today I tried it and was told that an IRC connection was made but the response was wrong so maybe I had the wrong key in place; however, not only is the key in place and I rehashed the server, it showed no connection attempt during the time (previously when the webpage would eventually time out, I would see the connection come in and the API key request, but not today). Sorry if this is the wrong place to file it, but I can't see any other contact information or place to file a bug. | ||||
| Additional Information | irc.srhuston.net 6697 | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I will have a look at this tomorrow, sorry for the trouble. |
|
|
Had a random idiot join and spam again last night, so came back to try this again; still takes all the information and says it's connecting, then reports that it failed because it connected but couldn't verify anything. Meanwhile my server never saw the connection at all. |
|
|
Not sure why I didn't get back to you in July, pretty sure I checked. Sorry for that. I know we had someone sign up successfully two days ago so I know it is not like a total failure at least. Looked at the error of today, it is: "FAILED: Connected to IRC server but no valid response. Check the request-key in your config (see 'Previous')! Did you copy-paste correctly and REHASH?" Was this error not displayed in the browser? I'm pretty sure the error is correct and that this is the problem. Of course, if you did not see this error in the browser then that would be problematic as you would have no idea what is wrong. I also see the same error on August 6. Can't look back beyond that, logs are deleted after a while. |
|
|
Yes, that's what I see. But I don't understand how that's possible - for one, the server doesn't report any connection of any kind, and I have other users successfully connecting currently. I also have the request-key configured as written and rehashed. And yes, it's the same error I've seen since I first reported. I'll try it again after lunch with a packet sniffer watching to see if I can find anything else that might be amiss. |
|
|
You won't ever see a "user connecting" message, as it never goes past the handshake. That's totally normal. But yeah it is convinced the key is wrong. Anything special you are doing different than other people? You don't accidentally have the request key twice in the configuration file or something? You are copy-pasting and not typing it manually (as that would lead to mixing up l/1/I/etc)? No weird whitespace left anywhere? Editing the right file on the right server? Really rehashing the server. That sort of fun! |
|
|
Ugh.. I had done all these things before, but a problem with the container configuration meant when I was editing the config outside docker the changes weren't going to the inside this time. I'll work on that part later, meanwhile I was able to get it to actually connect this time so I think my issue is resolved. Sorry for the trouble! |
|
|
No problem it happens :D The request was received correctly, someone of the team will look at it.. probably later today. I myself am off to work now though :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-07-17 21:08 | srhuston | New Issue | |
| 2024-07-18 00:47 | syzop | Note Added: 0023270 | |
| 2024-08-25 17:07 | srhuston | Note Added: 0023308 | |
| 2024-08-25 17:19 | syzop | Note Added: 0023309 | |
| 2024-08-25 17:22 | syzop | Note Edited: 0023309 | |
| 2024-08-25 18:58 | srhuston | Note Added: 0023310 | |
| 2024-08-25 19:31 | syzop | Note Added: 0023311 | |
| 2024-08-25 20:14 | srhuston | Note Added: 0023312 | |
| 2024-08-26 08:16 | syzop | Assigned To | => syzop |
| 2024-08-26 08:16 | syzop | Status | new => closed |
| 2024-08-26 08:16 | syzop | Resolution | open => no change required |
| 2024-08-26 08:16 | syzop | Note Added: 0023313 |
