Edit: For anyone with this issue, stopping and starting the Openmetrics plugin after saving the password in XO fixed it. I keep getting the {"error":"Query authentication does not match server setting"} problem, is there something I'm missing? I run XO proxied through Nginx with HTTPS, is there some additional config required to get it working? I have set the key with openssl rand -hex 32 and have verified that is saved correctly in the plugin, and that I am using the same key for curl. I am able to obtain the /health endpoint as expected, I just cannot obtain the full metrics, only returns that error. Command: curl --insecure -H "Authorization: Bearer mytoken" https://xo.mydomain.local/openmetrics/metrics XO commit: 91c5d I should note that running the command inside my Docker container returns only the error, including the health endpoint. Do I need to expose 9004?

so, I stopped rebooting my XOA everyday [image: 1770450390599-6c5ad7ea-5c6a-4fe9-88bf-58c69406edd4-2542a03d-3948-429f-8089-7eab68cf592e.png] just patched 6.1.1, it restarted xo-server [image: 1770450434127-b7adabb8-4d4f-4805-8b25-ddbedffe5cc0-cc0c1cce-6950-4f3c-b328-2e6d9d4889c7.png] guess I'll have to let it disabled for 48h to see if with new patch, RAM is still ramping up. will report back.

Also.. Thank you for taking a look at it and solving it so quickly, @florent It is a quite nice interaction when reporting bugs that they are looked at and triaged. Not saying everything needs to be a priority 1. But I do appreciate being close to the process. And if I can help make things better by reporting bugs, in a hopefully constructive way. Then I'll continue to contribute my way.