# Add a new site (android) 'was not found'

**URL:** https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589
**Category:** Support
**Created:** [July 21, 2017, 11:19am UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589 "2017-07-21T11:19:23Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![robgriff444](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@robgriff444](https://meta.discourse.org/u/robgriff444)
#### Post date: [July 21, 2017, 11:19am UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/1 "2017-07-21T11:19:23Z")

</div>

I’m trying to add [community.chakralinux.org](http://community.chakralinux.org) to my discourse app on android and it says it was not found. [Meta.discourse.org](http://Meta.discourse.org) works. Any ideas?

---

<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: [July 21, 2017, 12:35pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/2 "2017-07-21T12:35:11Z")

</div>

Your site don’t use HTTPS and it’s a requirement for the app

---

<div class="post-metadata">

### Author: ![robgriff444](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@robgriff444](https://meta.discourse.org/u/robgriff444)
#### Post date: [July 21, 2017, 12:54pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/3 "2017-07-21T12:54:53Z")

</div>

Thanks, It is HTTPS, I checked in Google chrome, is there something more specific that may be at fault?

---

<div class="post-metadata">

### Author: ![totte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/totte/32/18158_2.png) [@totte](https://meta.discourse.org/u/totte)
#### Post date: [July 21, 2017, 12:56pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/4 "2017-07-21T12:56:08Z")

</div>

> [@Trash](#):
>
> Your site don’t use HTTPS and it’s a requirement for the app

How did you determine that? It appears to use HTTPS to me, the “Force HTTPS” setting is enabled, and the certificate is valid until April, 2018.

---

<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: [July 21, 2017, 1:01pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/5 "2017-07-21T13:01:31Z")

</div>

That’s what I see if I click the link in the OP (using Firefox)

 ![gL9yKzf](https://global.discourse-cdn.com/meta/original/4X/c/5/0/c50e97a69a0288419fa92b95181cbd95b75a0aa6.png)  
Have you configured the redirect from HTTP to HTTPS?

---

<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: [July 21, 2017, 1:01pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/6 "2017-07-21T13:01:53Z")

</div>

I clicked the link and the http version loaded.

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

---

<div class="post-metadata">

### Author: ![totte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/totte/32/18158_2.png) [@totte](https://meta.discourse.org/u/totte)
#### Post date: [July 21, 2017, 1:20pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/7 "2017-07-21T13:20:09Z")

</div>

That’s peculiar. I can reproduce in Firefox. It used to have a [letsencrypt.org](http://letsencrypt.org) certificate, until we started using Fastly, as per [the official recommendations](https://meta.discourse.org/t/enable-a-cdn-for-your-discourse/14857). The instructions followed were [these](https://meta.discourse.org/t/enable-a-cdn-for-your-discourse/14857/12). Given the “Force HTTPS” option, I never considered this. The website got all A+ scores on [Qualys’](https://www.ssllabs.com/ssltest/analyze.html?d=community.chakralinux.org&hideResults=on).

I thought the redirection to be provided out of the box, would it be required to configure the `web.ssl.template.yml` to do this properly?

I set up a request setting to force TLS, as per [this guide](https://docs.fastly.com/guides/securing-communications/allowing-only-tls-connections-to-your-site).

Then:

```plaintext
$ curl -I -L "http://community.chakralinux.org" 
HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html; charset=utf-8
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Discourse-Route: categories/index
Cache-Control: no-store, must-revalidate, no-cache, private
X-Request-Id: 8711a2e1-8f03-43e2-b591-3f210d9136da
X-Runtime: 0.200937
X-Discourse-TrackView: 1
Referrer-Policy: no-referrer-when-downgrade
Strict-Transport-Security: max-age=31536000
Transfer-Encoding: chunked
Accept-Ranges: bytes
Date: Fri, 21 Jul 2017 13:05:06 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-bma7022-BMA
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1500642307.597531,VS0,VE236
Vary: Accept-Encoding

```

Now:

```plaintext
$ curl -I -L "http://community.chakralinux.org"
HTTP/1.1 301 Moved Permanently
Server: Varnish
Retry-After: 0
Location: https://community.chakralinux.org/
Content-Length: 0
Accept-Ranges: bytes
Date: Fri, 21 Jul 2017 13:46:13 GMT
Via: 1.1 varnish
Connection: close
X-Served-By: cache-bma7022-BMA
X-Cache: HIT
X-Cache-Hits: 0
X-Timer: S1500644774.956754,VS0,VE2

HTTP/1.1 200 OK
Server: nginx
Content-Type: text/html; charset=utf-8
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Discourse-Route: categories/index
Cache-Control: no-store, must-revalidate, no-cache, private
X-Request-Id: fb53fb0c-936e-459e-8154-b8ca0176db35
X-Runtime: 0.222025
X-Discourse-TrackView: 1
Referrer-Policy: no-referrer-when-downgrade
Strict-Transport-Security: max-age=31536000
Transfer-Encoding: chunked
Accept-Ranges: bytes
Date: Fri, 21 Jul 2017 13:46:14 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-bma7022-BMA
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1500644774.126033,VS0,VE256
Vary: Accept-Encoding

```

---

<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: [July 21, 2017, 2:00pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/8 "2017-07-21T14:00:23Z")

</div>

Did you pay to have Fastly support SSL for your site? Last I looked, it was expensive and looked cumbersome to configure.

---

<div class="post-metadata">

### Author: ![totte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/totte/32/18158_2.png) [@totte](https://meta.discourse.org/u/totte)
#### Post date: [July 21, 2017, 2:11pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/9 "2017-07-21T14:11:36Z")

</div>

They provide us with a TLS wildcard certificate. I have no frame of reference when it comes to the pricing and configuration learning curve, so I can’t comment on that.

Either way, `curl` and Firefox both appear to be redirected as they should. I installed the Discourse application on my Huawei “Nexus 6P” phone which runs Android 7.1.2, and trying to add the URL `community.chakralinux.org` does produce the error “[community.chakralinux.org](http://community.chakralinux.org) was not found!”. The Discourse installation is version v1.9.0.beta4 +126.

---

<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: [July 22, 2017, 1:51pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/10 "2017-07-22T13:51:26Z")

</div>

I have difficult to add my forum too (“was not found”).  
I’ve just upgraded the forum to the very latest version of discourse (v1.9.0.beta4 +196) and now I can add my site to the app. (Huawei Y6II)

---

<div class="post-metadata">

### Author: ![totte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/totte/32/18158_2.png) [@totte](https://meta.discourse.org/u/totte)
#### Post date: [July 22, 2017, 2:31pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/11 "2017-07-22T14:31:45Z")

</div>

I upgraded the installation:

```
# cd /var/discourse
# git pull
# ./launcher rebuild app

```

The version is now `v1.9.0.beta4 +196`, and when visiting `/admin/upgrade` everything is listed as “Up to date”. I reinstalled the Discourse application on my phone and tried adding the website to it again, but it still returns the same error, “[url] was not found!”. Adding this site (meta) works just fine.

Is there a way to enable verbose error logging or output from the Discourse application, in order to troubleshoot this further? I tried looking in `/logs` but when making the request (pressing ✔ to add the site) nothing pops up.

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 22, 2017, 2:38pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/12 "2017-07-22T14:38:03Z")

</div>

Just a quick note: I will investigate those issues next week.

---

<div class="post-metadata">

### Author: ![robgriff444](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@robgriff444](https://meta.discourse.org/u/robgriff444)
#### Post date: [July 22, 2017, 2:38pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/13 "2017-07-22T14:38:40Z")

</div>

@totte Site says error 503 on my desktop, restarted pc and router , no change,  
5 mins later, now says site is in maintenance  
Edit. Not looked for a while but at midnight it’s back up but still can’t use discourse app.

---

<div class="post-metadata">

### Author: ![totte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/totte/32/18158_2.png) [@totte](https://meta.discourse.org/u/totte)
#### Post date: [July 23, 2017, 9:53am UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/15 "2017-07-23T09:53:22Z")

</div>

I get the feeling that this could be related to our Fastly configuration. I don’t know whether the following is relevant or not, but I have _not_ completed this (serving **message bus** from the origin, and setting the **long polling base url** ):

> [@Full site CDN acceleration for Discourse](https://meta.discourse.org/t/full-site-cdn-acceleration-for-discourse/21467):
>
> [Fastly](http://www.fastly.com/) , [CloudFlare](https://www.cloudflare.com) and a few other CDNs offer a mode where they accelerate dynamic content. In a nutshell you point your domain IP address at the CDN and the CDN will intelligently decide how to deal with the request. Static content can be easily served from cache Dynamic content can be routed to the site. This provides some advantages over only shipping static assets which is covered in [the CDN howto](https://meta.discourse.org/t/enable-a-cdn-for-your-discourse/14857). You can elect for “[shielding](http://www.fastly.com/products/origin-shield/)” that protects your site from traffic spikes. Dynamic cont…

While the `fastly.template.yml` is included (by me) in the `app.yml` configuration file, a quick edit to comment it out, and a rebuild later, I am still unable to add the site in the Android application. I did not, however, reinstall it, or clear the cache, or anything like that on the Android device.

@j.jaffeux I’m a bit wary of what details can be shared or not, but would be happy to provide them in a private message, should it be required.

@robgriff444 I upgraded and rebuilt the installation yesterday, presumably at the same moment when you tried to access the website. I might arrange for an explanatory “maintenance page” to be displayed in the future, as opposed to a 502 or 503.

---

<div class="post-metadata">

### Author: ![Nicholas\_Tolstoshev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nicholas_tolstoshev/32/62714_2.png) [@Nicholas\_Tolstoshev](https://meta.discourse.org/u/Nicholas_Tolstoshev)
#### Post date: [August 4, 2017, 4:52pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/16 "2017-08-04T16:52:50Z")

</div>

I’m getting the same error message with our site: [forum.growersnetwork.org](http://forum.growersnetwork.org)  
It works fine on iOS but can’t get it to work on Android.

---

<div class="post-metadata">

### Author: ![Nicholas\_Tolstoshev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nicholas_tolstoshev/32/62714_2.png) [@Nicholas\_Tolstoshev](https://meta.discourse.org/u/Nicholas_Tolstoshev)
#### Post date: [August 4, 2017, 4:54pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/17 "2017-08-04T16:54:37Z")

</div>

We’re using Cloudflare in case that factors in to the issue.

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [September 18, 2017, 11:00am UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/18 "2017-09-18T11:00:42Z")

</div>

A similar issue has been solved, worth a read probably: [Community not found in App Android Version 7](https://meta.discourse.org/t/community-not-found-due-to-lack-of-https-redirection/69624)

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [September 23, 2017, 5:01pm UTC](https://meta.discourse.org/t/add-a-new-site-android-was-not-found/66589/19 "2017-09-23T17:01:10Z")

</div>

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
