Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is search down? #141

Closed
InstanceOfMichael opened this issue Mar 14, 2019 · 9 comments

Comments

@InstanceOfMichael
Copy link

commented Mar 14, 2019

https://status.algolia.com/hn this page shows nginx 404 white page.

The search itself shows the loading spinner indefinitely. It's not worked for new for me at least the last three days.

@Haroenv

This comment has been minimized.

Copy link
Member

commented Mar 14, 2019

cc @JonasBa. Do you see error messages in the console loading the regular search page? It seem to be working for me, but you're right that the status page you linked is down.

@InstanceOfMichael

This comment has been minimized.

Copy link
Author

commented Mar 14, 2019

I tried more things. It shows the loading indicator indefinity on all 4 versions of Firefox for Android never showing results

It works fine on Dolphin browser for Android. It works on chrome and firefox desktop.

@sgabler

This comment has been minimized.

Copy link

commented Mar 16, 2019

I have the same issue on Firefox mobile for Android. The spinning wheel keeps spinning indefinitely. Other Android browsers work fine for me. Had that issue for a couple of weeks, but only just discovered this repo here.

@JonasBa

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2019

Could you please check if you see any errors in the console? We have been trying to reproduce the issue without success using browserstack. If you see any errors or could provide us more information that would make it easier to debug we’d greatly appreciate it 🙌🏼

@ghost

This comment has been minimized.

Copy link

commented Mar 16, 2019

Here's what it looks like for me (in a private window):
algolia

The console output:
image

That Google Analytics warning is caused by ublock origin. But I also have the same spinning wheel if i disable ublock origin.

Nothing stands out for me in the console, but the network panel shows a couple of 500s:
image

I also disabled "Do not Track" and "Tracking Protection" in the Settings, but the result was the same.


Here are the headers from one of those 500s.

Request

POST /dev/v1/measure HTTP/1.1
Host: telemetry.algolia.com
User-Agent: Mozilla/5.0 (Android 8.0.0; Mobile; rv:65.0) Gecko/65.0 Firefox/65.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
Accept-Language: en-US,de-DE;q=0.7,en;q=0.3
Accept-Encoding: gzip, deflate, br
Referer: https://hn.algolia.com/?query=Microsoft&sort=byPopularity&prefix=false&page=0&dateRange=all&type=story
Content-Type: text/plain;charset=UTF-8
Content-Length: 95
Connection: keep-alive
Cookie: __cfduid=d2dfabea329792d41b64d434037c6a1751551360835; _ga=GA1.2.1209937608.1552747374; _gid=GA1.2.892106583.1552747374

Response

HTTP/2.0 500 Internal Server Error
date: Sat, 16 Mar 2019 14:44:46 GMT
content-type: text/html
x-amzn-requestid: 0b4925fc-47fa-11e9-8d22-8bb3b3019059
x-amzn-remapped-content-length: 291
x-amz-apigw-id: Wo7K0GTIliAFugw=
x-amzn-trace-id: Root=1-5c8d0bde-7781d817c207127ebcbafd91;Sampled=0
x-cache: Error from cloudfront
via: 1.1 aec69d2871c7aeb74988020f07480fa4.cloudfront.net (CloudFront)
x-amz-cf-id: lnyNbFmQO7exXuLPhWZajQ883D_XAuHfTnrHmWSnZ03NO5pi7r5jUw==
strict-transport-security: max-age=31536000; includeSubDomains; preload
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 4b8781d088652d95-TXL
X-Firefox-Spdy: h2

Notice the x-cache: Error from cloudfront in the response. Maybe this is related?

@JonasBa

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2019

Thanks a lot @sgr-amboss, I'm having a look and I have a feeling of what could be wrong. It seems that the timeout is set to NaN, which should not be the case. We have been testing better adjustments of timeouts depending on the network that our users are on and it seems that I've broken the adjustments in the last release. Updating it now, thanks a lot for taking the time and effort to send me the console output ❤️

@ghost

This comment has been minimized.

Copy link

commented Mar 16, 2019

Just realized that the gif i posted was cut after a few seconds. I probably messed up somewhere. Here's the actual gif:
algolia2

Thank you for taking a look, but at least for me this issue can definitely wait. No need to sacrifice your weekend 😉

@JonasBa

This comment has been minimized.

Copy link
Contributor

commented Mar 16, 2019

@sgr-amboss thanks a lot, definitely not an issue! I've just deployed a fix. Thanks again for the detailed report, it helped me quickly debug the issue and fix it, appreciate the help 🙌 Let me know if you still see some odd behaviour :)

@JonasBa JonasBa closed this Mar 16, 2019

@ghost

This comment has been minimized.

Copy link

commented Mar 16, 2019

Thank you. It now works perfectly! 🥇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.