# Android app can't see my discourse

**URL:** https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395
**Category:** Support
**Created:** [2월 14, 2017, 11:17오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395 "2017-02-14T23:17:25Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![Tom\_Newsom](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_newsom/32/115981_2.png) [@Tom\_Newsom](https://meta.discourse.org/u/Tom_Newsom)
#### Post date: [2월 14, 2017, 11:17오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/1 "2017-02-14T23:17:25Z")

</div>

Unless I’m missing some setting I have to enable on our end, the official app won’t connect to

> **[Discourse – South London Makerspace](https://discourse.southlondonmakerspace.org)**
>
> South London Makerspace is a social community workshop, where members can make things, share knowledge and make friends.

 ![](https://global.discourse-cdn.com/meta/original/3X/f/1/f1247337a7229ae900950e47f7f3dc875625b43a.png)

It works with Meta just fine. In fact I’m posting from it now…

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2월 14, 2017, 11:35오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/2 "2017-02-14T23:35:14Z")

</div>

Not sure, this is a question for @sam.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 14, 2017, 11:45오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/3 "2017-02-14T23:45:37Z")

</div>

Maybe missing protocol and https redirect is not in place

---

<div class="post-metadata">

### Author: ![Tom\_Newsom](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_newsom/32/115981_2.png) [@Tom\_Newsom](https://meta.discourse.org/u/Tom_Newsom)
#### Post date: [2월 14, 2017, 11:56오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/4 "2017-02-14T23:56:25Z")

</div>

Could you explain in a bit more detail (for this self-taught imposter-sysadmin!)

Our https setup predates Let’s Encrypt, but I remember following a guide here on meta line by line.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [2월 14, 2017, 11:59오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/5 "2017-02-14T23:59:17Z")

</div>

I thought Official App worked only with Hosted sites. Am I wrong, or do I misunderstand his question?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 15, 2017, 12:04오전 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/6 "2017-02-15T00:04:37Z")

</div>

> [@Tom\_Newsom](#):
>
> Our https setup predates Let’s Encrypt,

try adding `https://` before, does it work? are you updated to latest? my guess is that there are issues with the http redirect.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2월 15, 2017, 12:05오전 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/7 "2017-02-15T00:05:15Z")

</div>

It works fine with all discourse site provided they are running latest, but you get no push notifications.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [2월 15, 2017, 12:08오전 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/8 "2017-02-15T00:08:36Z")

</div>

I see. But you can still get mobile notifications with [discourse-push-notifications plugin](https://github.com/discourse/discourse-push-notifications/commits/master), just not through the App, right?

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2월 15, 2017, 12:47오전 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/9 "2017-02-15T00:47:42Z")

</div>

> [@pfaffman](#):
>
> But you can still get mobile notifications with discourse-push-notifications plugin, just not through the App, right?

Yeah, but clicking on the notification will open Chrome, not the app.

And that is Android only.

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [4월 17, 2019, 12:19오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/10 "2019-04-17T12:19:03Z")

</div>

I have the same issue with `talk.libreho.st`. I have successfully installed in the app 10 Discourse instances on TLDs ranging from `.org` to `.wiki` and `.network`, but this one fails.

- ✅ responds to port 80 with 301 redirect to port 443
- ✅ has a valid SSL certificate
- ✅ no error logged on the web server

Checked with:

- `curl -I -v http://talk.libreho.st/`
- `curl -I -v https://talk.libreho.st/`

Tried both without and with the scheme.

* * *

Edit: I’m running version 1.2.1, will upgrade to 1.3.0 first…

---

<div class="post-metadata">

### Author: ![dax](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dax/32/244677_2.png) [@dax](https://meta.discourse.org/u/dax)
#### Post date: [4월 17, 2019, 12:57오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/11 "2019-04-17T12:57:08Z")

</div>

I tried to add `talk.libreho.st` with success

 ![Screenshot_20190417_144547](https://global.discourse-cdn.com/meta/original/3X/9/9/99b4f0b408b6f0722a23841e4242db34892d9a65.jpeg)

Android 9, Huawei mate 20 pro.

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [4월 17, 2019, 1:44오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/12 "2019-04-17T13:44:20Z")

</div>

Thanks @dax. I upgraded to 1.3.0, and it still fails. I have no idea why. Other domains work fine.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [4월 17, 2019, 1:49오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/13 "2019-04-17T13:49:47Z")

</div>

`talk.libreho.st` Works for me too on iOS, which suggests it’s your test device.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [4월 17, 2019, 3:41오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/14 "2019-04-17T15:41:57Z")

</div>

Are you using a Samsung phone running Android 7 ?

> [@Community not found in App Android Version 7](https://meta.discourse.org/t/community-not-found-in-app-android-version-7/69624/37):
>
> Hello Gerhard, The problem is solved. After looking at the SSLLabs results again i noticed a difference between the Android 7.0 handhake. Our site gave ECDH secp384r1 while your site gave ECDH secp256r1. After some googling i landed on the following site: [https://stackoverflow.com/questions/39133437/sslhandshakeexception-handshake-failed-on-android-n-7-0](https://stackoverflow.com/questions/39133437/sslhandshakeexception-handshake-failed-on-android-n-7-0) So there seems to be a bug in Android 7.0. I now changed the line “ssl\_ecdh\_curve secp384r1” to “ssl\_ecdh\_curve prime256v1” in “web.ssl.temp…

---

<div class="post-metadata">

### Author: ![h.vdheurik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/h.vdheurik/32/78661_2.png) [@h.vdheurik](https://meta.discourse.org/u/h.vdheurik)
#### Post date: [4월 18, 2019, 9:04오전 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/15 "2019-04-18T09:04:36Z")

</div>

Yes, it was a Samsung phone with Android 7.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [4월 18, 2019, 9:37오전 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/16 "2019-04-18T09:37:39Z")

</div>

Right, we know it was in your case, since you helpfully reported it – we were asking @hellekin if the same thing applies to him. Sorry to bug you 😛

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [4월 18, 2019, 1:43오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/17 "2019-04-18T13:43:05Z")

</div>

I’m using a non-rooted Android 7.0 with MicroG installed and no Gaggle account. I’m trying to upgrade everything, test with various things enabled or disabled. After resetting all apps and rebooting, I found that there’s one system app remaining disabled and that is not possible to enable: “Android System WebView”. After some research I have managed to update it by disabling Chrome, then updated it, and re-enabled Chrome. I tried to update Chrome from 63 to 73, but the system tells me I must use “root or privileged install”. Then I updated everything, re-enabled all Gaggle apps and Discourse app. Still no luck. This is very strange.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [4월 18, 2019, 1:47오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/18 "2019-04-18T13:47:27Z")

</div>

That sounds very _very_ hard to support.

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [4월 18, 2019, 1:49오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/19 "2019-04-18T13:49:57Z")

</div>

I cannot see any reason why `.st` would fail only on my device. If you know of another Discourse instance on this TLD, I’d be happy to test that as well.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [4월 18, 2019, 1:52오후 UTC](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395/20 "2019-04-18T13:52:22Z")

</div>

Did you read the link from @falco above? It’s unlikely to be the domain and more likely to be the specific ecdh handshake.

[Next page](https://meta.discourse.org/t/android-app-cant-see-my-discourse/57395.md?page=2)
