LeeThompson
commented
1 month ago UPDATE: There is something going on with the CORS policy that seems to be new. Did Glances prior to v3 set CORS headers?
I worked around this by changing the API version from v3 to v4 and enabled CORS on Traefik and seem to have this working again.
Not sure what the proper solution is.
Workaround
Traefik
https://doc.traefik.io/traefik/middlewares/http/headers/
I use staticfile for my environment so I made these changes in staticconfig.yml:
In the middlewares: section.
testHeader:
headers:
accessControlAllowMethods:
- GET
- OPTIONS
- PUT
accessControlAllowHeaders: "*"
accessControlAllowOriginList: "*"
accessControlMaxAge: 100
addVaryHeader: falseI have 3 machines that run glances, so I have it set up in Traefik so each one can be accessed like http://glances.local/docker1/ http://glances.local/docker2/ etc.
Under services: section:
glancesdocker1:
loadBalancer:
servers:
- url: http://docker1.local:61208/Under the routers section is where the CORS configuration comes in.
glances_docker1
entryPoints:
- http
rule: "Host(`glances.local`) && PathPrefix(`/docker1`)"
middlewares:
- testHeader
service: glancesdocker1Dasherr
The include\worker.js needs changed:
Basically the api/v3 needs changed to api/v4.
Presumably you could also do this in Traefik but I think this is easier.
function refreshWidgetGlances(nW) {
$.getJSON({url: gSettings.widgets[nW].settings.url + 'api/4/quicklook'}).done(function (result, status, xhr) {
document.getElementById('cpuPrct' + nW).innerText = result.cpu + '%'
document.getElementById('memPrct' + nW).innerText = result.mem + '%'
});
$.getJSON({url: gSettings.widgets[nW].settings.url + 'api/4/sensors'}).done(function (result, status, xhr) {
document.getElementById('cpuTemp' + nW).innerText = (result.length > 0? result[0].value + 'C' : '-')
});
}Of course in the various settings pages, in the widget section the URLs will need to be updated to http://glances.local/docker1/ and so on.
erohtar
Glances API changed and they've dropped support for the older API formats.
Unfortunately since many users may still be running Glances 3.x, there will probably need to be alternate code paths.
I'm running Glances 4.0.4 here and Dasherr just show blank entries now. Fortunately, it's not urgent for me.
If need be I can run test code on my Dasherr install.
(The widget configuration should probably have an api version setting?)
Did some initial poking around as shown below. Sadly my JavaScript is very iffy so I'm not able to make code suggestions.
I did try to change:
$.getJSON({url: gSettings.widgets[nW].settings.url + 'api/3/quicklook'}).done(function (result, status, xhr) {to$.getJSON({url: gSettings.widgets[nW].settings.url + 'api/4/quicklook'}).done(function (result, status, xhr) {etc but it didn't do anything useful.One interesting thing is FIrefox showed this in the console:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://redacted:61208/api/4/quicklook. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.More information at Mozilla Reference
http://redacted:61208/api/4/sensorshttp://redacted:61208/api/4/quicklookhttp://redacted:61208/api/3/quicklook