-
-
Notifications
You must be signed in to change notification settings - Fork 120
IDA hangs when attempting to connect #181
Copy link
Copy link
Open
Description
I'm on Arch Linux x86_64, using IDA 9.1.250266.
Attempting any connection to the server results in IDA hanging.
I have been able to run a local lumen server which worked fine and the server was functional.
I have tried running a proxy like that:
socat -s -dd tcp4-listen:1234,fork,reuseaddr openssl:lumen.abda.nl:1235,cafile=hexrays.crt
And like that:
socat -s -dd tcp4-listen:1234,fork,reuseaddr openssl:lumen.abda.nl:1235,verify=0
Both ways timed out after around 16 minutes, with the socat's output being:
2025/09/25 19:16:24 socat[91325] N listening on AF=2 0.0.0.0:1234
2025/09/25 19:16:39 socat[91325] N accepting connection from AF=2 127.0.0.1:34496 on AF=2 127.0.0.1:1234
2025/09/25 19:16:39 socat[91325] N forked off child process 91449
2025/09/25 19:16:39 socat[91325] N listening on AF=2 0.0.0.0:1234
2025/09/25 19:16:39 socat[91449] W OpenSSL: Warning: this implementation does not check CRLs
2025/09/25 19:16:39 socat[91449] N opening OpenSSL connection to lumen.abda.nl:1235
2025/09/25 19:16:39 socat[91449] N opening connection to server lumen.abda.nl:1235
2025/09/25 19:16:39 socat[91449] N opening connection to AF=2 129.159.136.126:1235
2025/09/25 19:16:41 socat[91449] N successfully connected from local address AF=2 192.168.1.107:58444
2025/09/25 19:32:36 socat[91449] W SSL_connect(): Connection timed out
2025/09/25 19:32:36 socat[91449] N exiting with status -1
2025/09/25 19:32:36 socat[91325] N childdied(): handling signal 17
It seems like the server is down?
If I missed anything here, or have done something wrong, please to point that out.
I understand the public server may have limitations; any tips or updates would be great.
Thanks for your help in advance!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels