Device registration: User message in case of connection failure

[radinamatic]

Suggested change

Old:

 <p>{% trans "The device needs to have internet access when first being registered. Please ensure it is connected to the internet, and then" %} <a href="." class="refresh-link">{% trans "refresh this page" %}</a>.</p>

New:

<p>{% trans "The device needs internet access in order to be registered. Please ensure you are connected to the internet, and then" %} <a href="." class="refresh-link">{% trans "refresh this page" %}</a>. If you are still getting this message, it might indicate a temporary problem with the central server. Please wait a few minutes and try again later.</p>

...in python-packages/securesync/templates/securesync/register_public_key_client.html

Summary

KA Lite seems unable to connect to register the device in order to download the videos & languages. Refreshing the page has no effect, and the machine is correctly connected to Internet (see the loaded elpais.com in the other window).

Is staging.learningequality.org where the device register happens? It seems to be running OK, so the culprit might be other.

Screenshots

[benjaoming]

Just experienced exactly the same on FF, Ubuntu 0.16.9 installation.

@radinamatic are you able to reproduce this for 0.16.9 in all cases? It might be a server-side issue..

[benjaoming]

Also, try running the server with kalite start --foreground in order to get more logging and see what it says at the exact moments of registration.

[radinamatic]

Apparently, one-click registration on WXP is working today:

[radinamatic]

Works on Ubuntu too, fresh 0.16.9 install:

Seems it's most likely the temporary problem with our server, so I suggest changing this line into:

<p>{% trans "The device needs internet access in order to be registered. Please ensure you are connected to the internet, and then" %} <a href="." class="refresh-link">{% trans "refresh this page" %}</a>. If you are still getting this message, it might indicate a temporary problem with the central server. Please wait a few minutes and try again later.</p>

[benjaoming]

@radinamatic okay the string freeze is up, but I think you are hinting at two issues:

1. a possible issue with network connectivity during registration, could be related to other DNS issues we've discussed
2. a user message change.

I'm altering the issue to be about the latter, if you have more information to provide on the first subject, please open a new issue.

[benjaoming]

Changed description.

[radinamatic]

@benjaoming User message change is generic enough in order to cover multiple connection issues. If the string freeze is up, does that mean it will not make it for the 0.17?

[benjaoming]

@radinamatic - that would have been the standard policy, however I don't see a problem adding an error message in this case and it gets released untranslated, it's an error message after all.

[benjaoming]

It's freezing up again in 0.16.9. The same in 0.17.0. Still not seeing any useful log messages: No JS error, no server-side error, no connection error from the browser. Everything is stuck at this picture:

[benjaoming]

I have Wiresharked myself during this error message. No network activity at all during the error message.

[benjaoming]

Maybe relevant: learningequality/ka-lite-content-packs#58 (comment)

[benjaoming]

Connection failures seem to be reproducing across the spectre. Downloading all_metadata.json is also failing. Suspecting new CSP / CORS stuff to be the cause.

[benjaoming]

I'll try this: https://github.com/ottoyiu/django-cors-headers/

[rtibbles]

Adding dataType to jsonp might be sufficient to fix this: https://github.com/learningequality/ka-lite/blob/master/kalite/updates/static/js/updates/bundle_modules/update_languages.js#L35

So this options object becomes:

{
    cache: false,
    dataType: "jsonp"
}

[benjaoming]

Hmm, I tried to update django-cors-headers to work with Django 1.5.. which was a rabbit hole.

Trying @rtibbles 's suggestion to change to jsonp..

[benjaoming]

@rtibbles oh yes, I tried that yesterday, we need to list out the json fields, too, but seems plausible. Will PR soon..

[benjaoming]

Changed to jsonp but the request is still never received by Pantry, and XHR .fail is still called straight-away.

[benjaoming]

Thanks Chromium, this error message helps a lot :)

XMLHttpRequest cannot load http://pantry.learningequality.org/downloads/ka-lite/0.17/content/contentpa…ata.json?callback=jQuery21407293127653173606_1486484313736&_=1486484313737. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:8000' is therefore not allowed access. The response had HTTP status code 405.

[benjaoming]

Some gateway in front of the Pantry server seems to be giving a 405 when the browser tries to retrieve CORS policies:

jquery.js:8630 OPTIONS http://pantry.learningequality.org/downloads/ka-lite/0.17/content/contentpa…ta.json?callback=jQuery214017264082951495596_1486485490415&_=1486485490416 405 (Not Allowed)

Can someone please tell me why we even have a gateway in front of Pantry and if we can lower the complexity level a bit here? :)

[radinamatic]

Pinging @aronasorman 🆘

[benjaoming]

Okay, we got through the diversion - actually the problem was a misconfiguration of pantry.learningequality.org and that's been fixed.

We can concentrate on the original issue about the user message.

[radinamatic]

Latest screencast is here.

[mrpau-eugene]

Has anyone filed a PR on updating the user message in case the internet is unavailable or gets disconnected?

[benjaoming]

@mrpau-eugene no, this issue is still unsolved and relevant, PR is welcome!