element-hq / element-hq/element-android

"No network" error when attempting to connect to a local, non-public synapse server via HTTP

Open
#6,721 16 comments 1 reaction 0 assignees View on GitHub
A-Onboarding O-Uncommon S-Major Security T-Defect
Dominant language
Kotlin
Stars
3.7k
Forks
917
PR merge metrics
No merged PRs in 30d

Description

### Steps to reproduce

Basically, having the same issue noted in this error report below from a year ago. I would really like to have a way to work around this error. Being local only homeserver, I would like to avoid having to make SSL certs for a single user at this time. I have been able to link all other devices that are on iOS without issue. I receive the same "No Network" error, but no further information. The local network connection with this device works flawlessly otherwise.

My server address is: 'http://synapse.lan:8008'

I immediately receive a No Network error on Anroid only, exactly the same issue noted in the report below.

Thank you in advance.

Referenced issue linked below:

https://github.com/vector-im/element-android/issues/3280#issue-876271603

### Outcome

#### What did you expect to happen?

_Similar to iOS, Windows and Linux applications, connection to server established, and moving to a login screen._

#### What happened instead?
I receive a "No network" error with no further error codes or reasoning. Rest of network connections aside from element-android work flawlessly.

### Your phone model

Samsung S9

### Operating system version

Android 12

### Application version and app store

element-android 1.4.27

### Homeserver

Synapse, local-only, non-federated, non-public facing via HTTP

### Will you send logs?

No

### Are you willing to provide a PR?

No

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.