search

oxen-io / session-desktop

Session Desktop - Onion routing based messenger
https://getsession.org
GNU General Public License v3.0
1.56k stars 196 forks source link

IM - Session Mac desktop version cannot receive messages #2378

Closed OliviaC235 closed 2 years ago

OliviaC235 commented 2 years ago

IM - Session Mac desktop version cannot receive messages. But messages can be sent

product-think2049 commented 2 years ago

same problem. In mainland China cannot receive messages, cannot send messages in Mac (Android, iPhone is OK.)

product-think2049 commented 2 years ago

Here is the log session_debug_1656464228551.log

5fXs6G commented 2 years ago

Same here. Latest macOS, latest app version, can't connect or send/receive messages. Firewall is off. Default route table. Phone apps connect fine.

Bilb commented 2 years ago

IM - Session Mac desktop version cannot receive messages. But messages can be sent

Can you send me your logs? So I can see if anything matches other users?

Bilb commented 2 years ago

Same here. Latest macOS, latest app version, can't connect or send/receive messages. Firewall is off. Default route table. Phone apps connect fine.

Sam here, can you send me your logs?

Bilb commented 2 years ago

IM - Session Mac desktop version cannot receive messages. But messages can be sent Are you on macOS beta?

5fXs6G commented 2 years ago

I figured out my issue:

INFO {time} getSnodeListFromSeednode starting... INFO {time} fetchSnodePoolFromSeedNodeRetryable starting... INFO {time} getSnodesFromSeedUrl starting with [REDACTED] INFO {time} insecureNodeFetch => plaintext for getSnodesFromSeedUrl WARN {time} fetchSnodePoolFromSeedNodeRetryable attempt #2 failed. 2 retries left... Error: network timeout at: [REDACTED]

While my macOS and LuLu firewalls were off for debugging, I forgot my pfBlockerNG is set to allow only certain certain TLDs and IPs by region. Looking through my DNS resolver/pfBlockerNG DNSBL logs, I saw calls to resolve *.seed{1-3}.loki.network so I just had to make sure the .network TLD was allowed and it now works for me.

5fXs6G commented 2 years ago

Here is the log session_debug_1656464228551.log

Looks like you might have the same issue as my previous comment^:

WARN 2022-06-29T00:56:32.361Z fetchSnodePoolFromSeedNodeRetryable attempt #4 failed. 0 retries left... Error: request to [REDACTED] failed, reason: self signed certificate ERROR 2022-06-29T00:56:32.362Z allowOnlyOneAtATime - error DEPTH_ZERO_SELF_SIGNED_CERT request to [REDACTED] failed, reason: self signed certificate WARN 2022-06-29T00:56:32.362Z SessionSnodeAPI::fetchSnodePoolFromSeedNodeWithRetries - error DEPTH_ZERO_SELF_SIGNED_CERT request to [REDACTED] failed, reason: self signed certificate WARN 2022-06-29T00:56:32.362Z SessionSnodeAPI::fetchSnodePoolFromSeedNodeWithRetries - error DEPTH_ZERO_SELF_SIGNED_CERT request to [REDACTED] failed, reason: self signed certificate

Self-signed cert warning on the seed URL. Most likely an application or network firewall appliance is blocking the domain and the firewall is showing a "blocked" page under self-signed SSL/TLS. Or your macOS Keychain is missing the standard CA certs. Or you untrusted the Root CAs for the certs the network is using.

InoMurko commented 2 years ago

My log:

WARN  2022-06-29T07:09:19.661Z [path] Got status at destination: 401
WARN  2022-06-29T07:09:19.661Z Couldn't reach snode at: (...ac28d5); setting his failure count to 2
ERROR 2022-06-29T07:09:19.661Z [path] lokiRpc::processingOnionResponse - Rethrowing error Bad Path handled. Retry this request. Status: 401'
WARN  2022-06-29T07:09:19.661Z onionFetchRetryable attempt #4 failed. 0 retries left...
WARN  2022-06-29T07:09:19.661Z onionFetchRetryable failed  Bad Path handled. Retry this request. Status: 401
WARN  2022-06-29T07:09:19.662Z retrieveNextMessages attempt #1 failed. 1 retries left... Error
KeeJef commented 2 years ago

Is this still occurring in 1.9.0?

InoMurko commented 2 years ago

Is this still occurring in 1.9.0?

Nop!