Mobile: Clicking Create New Account causes processing spinner icon to keep spinning


(David Taylor) #21

The padlock might actually be misleading us… the padlock seems to appear/disappear sporadically for me, and I think it’s because one of the images in the header is not being loaded securely

The main logo code at the top of try.discourse.org

<img width="64" height="45" src="https://discourse.org/images/nav-icon.png" alt="logo">

This then gets 302 redirected to a non-secure address

curl -vv -L https://discourse.org/images/nav-icon.png
*   Trying 104.25.152.10...
* TCP_NODELAY set
* Connected to discourse.org (104.25.152.10) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
* Server certificate: ssl389619.cloudflaressl.com
* Server certificate: COMODO ECC Domain Validation Secure Server CA 2
* Server certificate: COMODO ECC Certification Authority
> GET /images/nav-icon.png HTTP/1.1
> Host: discourse.org
> User-Agent: curl/7.51.0
> Accept: */*
> 
< HTTP/1.1 302 Found
< Date: Fri, 13 Jan 2017 23:57:46 GMT
< Content-Length: 0
< Connection: keep-alive
< Set-Cookie: __cfduid=d8eedaeec0f7cde48c1545924348047281484351865; expires=Sat, 13-Jan-18 23:57:45 GMT; path=/; domain=.discourse.org; HttpOnly
< Cache-Control: no-cache
< Location: http://www.discourse.org/images/nav-icon.png
< CF-Cache-Status: MISS
< Server: cloudflare-nginx
< CF-RAY: 320ccad90b4a350c-LHR

This is on a home network, no weird enterprise proxies. I doubt this is the root cause of the topic of this thread, but it’s certainly confusing things!


(Matt Palmer) #23

Thanks for that test, @Doker; I’ve found the relevant requests in the logs, and I’ll pass them on to someone who can do a better dissection than me.

Good catch, @david, on the redirecting image. That redirect should be preserving the HTTPSness of the original request, so obviously something has come unstuck in our haproxy config, so I’ll take a look at that. Also, I’ll look at getting the src on that link changed, since a spurious redirect isn’t great for performance, regardless of any other considerations.


(Jeff Atwood) #24

Yeah requesting https://discourse.org/images/nav-icon.png definitely results in an incorrect redirect to http. I think that redirect is coming from CloudFlare though.

edit: for now, I’ve replaced that navigation icon with an image from the CDN.


(Andrew) #25

I’m testing on a home network with no enterprise proxies. On the same network with the same phone, I’ve had it work and not work for me on various occasions. The first time I tried three days ago (screenshot above), I didn’t have the padlock showing and it didn’t work. I’ve tried every day since then, each time I see the padlock and it works no problem. Unfortunately, on our discourse forum that we’re trying to launch (with no customizations, other than css/html), I continue to get the same spinning icon issue even though the accounts are created and activation email sent.

iPhone 6, Version iOS 10.2, Latest Safari, no plugins

I just tested with my phone again and it worked fine; however, I just tested with my wife’s phone and it didn’t work…her details:

Time: 16:44 PST
IP: 108.172.56.95
Device: iPhone 6, Version iOS 10.2, Latest Safari, no plugins


(Jeff Atwood) #26

Wait, so you’re saying on the same device it didn’t work before, now it is working?

I definitely changed out the image on try.discourse.org that was getting erroneously redirected to http, but that’s it.


(Andrew) #27

Yes on my phone the first time I tested on try.discourse.org it didn’t work (that was my first screenshot three days ago). Every day I’ve tried since, it has worked for me, including today. However on my wife’s phone, it hasn’t worked at any time (the latest details above). We have the same device, same ioS version, no plugins and obviously on the same home network.


(Matt Palmer) #29

Hi @AndrewM,

Thanks for that test, especially the different behaviours between devices on the same network. I can see two interactions in our logs a few minutes apart; could you confirm that the first one (at about 16:37 PST) was the successful one from your device, while the second (at about 16:44 PST) was the unsuccessful one from your wife’s device? The two sessions show different behaviours behind the scenes, and I want to make sure we’re correlating the correct ones to successful / unsuccessful interactions.


(Jeff Atwood) #30

Can you try in incognito (private) mode to rule out any cookies or anything like that? Another variable is your network. Are you on wifi or cellular? Try switching from one to the other.


(Andrew) #31

@mpalmer yes, the first one was from my phone and successful and the second attempt was from my wife’s phone and unsuccessful.


(Andrew) #32

I just tested on my wife’s phone which has never worked, and using private mode it worked just fine the first time. In all tests we’ve done we’re on our home wifi.


(Jeff Atwood) #33

Ok this implies there’s something weird going on with the browser and/or browser state in that case. Not sure what it would be, as there’s no cookie/login info on that browser?


(David Taylor) #34

Back on the university network again - was unable to access http:// so I think I was confused yesterday by the padlock. The 301 redirect does indeed work correctly.

Tried on my laptop using chrome - worked fine
Tried on an iPad emulator on my laptop - worked fine
Tried on my actual iPad - got the issue twice

Approx 15:06 UTC and 15:21 UTC
IP: 128.243.2.139
iPad Air 2, iOS 10, enterprise wifi network

In between those two attempts I tried in “private browsing” mode and it worked fine…

I had the safari dev tools open (via USB) and there was nothing in the console. Network tab showed a dropped connection to “poll” which I’m guessing is the messagebus - could that be related? Does account creation information get sent over the messagebus?

Tried to do some more testing but my IP has now been blocked from creating more accounts on try.discourse.org :joy: