Thank you for your answer.
Now I think...

Le 27/08/2015 14:16, Ján Máté a écrit :
What do you expect if you have problem with your certificate?

[Error] Failed to load resource: The certificate for this server is invalid. You might be connecting to a server that is pretending to be “” which could put your confidential information at risk. (cache.manifest, line 0)
[Error] SyntaxError: Unexpected identifier 'such'
(anonymous function)
[Error] TypeError: $('input[placeholder],textarea[placeholder]').placeholder is not a function. (In '$('input[placeholder],textarea[placeholder]').placeholder()', '$('input[placeholder],textarea[placeholder]').placeholder' is undefined)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (favicon.ico, line 0)

and from readme.txt:

5.) problems with SSL /https/ and invalid (or self-signed) certificates
    - Why the client cannot connect to server with invalid/self-signed certificates?
      If a user opens a web page and the browser detects invalid/self-signed certificate it warns user about this problem, and usually shows an option to accept the server certificate (or add a security exception) manually. If the request is sent by JavaScript there is NO such option to show user the security warning, and also it is NOT possible to add security exception directly by JavaScript!
    - What to do to solve this problem?
      a.) use valid server certificate from commercial CA or
      b.) if your server certificate is not self-signed and is issued by your own CA, add your CA certificate into "Trusted Root Certificates" in your browser/system or
      c.) open the principal URL directly by browser, accept the invalid certificate (or add a security exception) manually



On 27 Aug 2015, at 14:06, Pierre Couderc <> wrote:

Our internet has come back, and I have same problem on :

The login dialog does not appear in the white page.

I please readers to try and give me an advice.

Thank you