the problem is NOT in your config.js, there is NO MAGIC. The web server DOES NOT check the content of this file. The server returns the MIME type by checking the file NAME (not content).
Use the following command in terminal (the "-crlf" depends on your server):
then use the following commands (as usually for telnet www.somesite.com 80):
GET /infcloud/config.js HTTP/1.1
and you will get something like:
HTTP/1.1 200 OK
Date: Sun, 09 Feb 2020 10:57:09 GMT
Last-Modified: Tue, 22 Sep 2015 13:30:13 GMT
Cache-Control: max-age=0, must-revalidate, no-cache, no-transform, private
Expires: Sun, 09 Feb 2020 10:57:09 GMT
<content of the config.js>
The content type is the line which must be set correctly! If the Content-type will be correct in the response, then it will work also in your browser (after forcing it to clear the cache by executing the cache_update.sh).
..just an additional note:
I noticed that the file /etc/mime.types has been changed on Jan 28, obviously by my hoster (I have no write access in /etc) and this corresponds well with
The date from which infcloud would no more work for me.
The file, however, contains a line
And then just comment out loading config.js in index.html ?
am Sonntag, 9. Februar 2020, 10:10:30 CET schrieb Werner Joss:
Thanks for reply - and no, I did not change anything since it used to work.
But from the browser console output, I suppose the configuration is not loaded correctly, see the attached screenshot,
Telling me the MIME type of file config.js is wrong.
As a result, globalInterfaceLanguage is not defined in main.js
In config.js, the corresponding line is
I'm not sure how to change the MIME type of config.js ?
Am Samstag, 8. Februar 2020, 19:59:22 CET schrieb Ján Máté:
there is nothing what can block the client from working if your client configuration or server configuration is the same. You very probably changed something somewhere.
The only thing you can do is to check the console.log in your browser ...
On 8 Feb 2020, at 09:17, Werner Joss <email@example.com> wrote:
I'm just stumbling over an issue, that has been there then and now already in the past, but now seems to be persistant:
I can no longer log into my infcloud instance as the Login screen is just empty.
Looking in the page source in the Browser, I see that all containers have the attribute display:none
<><div id="LoginPage" style="opacity: 1; display:none">
What could I try to solve this ?