I did some tests the problem seems to be in the “SIGN” phase the manifest.js program sends the signature request to this server: “https://grafana.com/api/plugins/ci/sign” which modifies the rootUrls by removing 443, in the start phase of grafana.exe the internal plugin does not start because appUrl is different to rootUrls in MANIFEST.TXT. I tried removing the http_port from the defauls.ini file but in this case the plugin loads but the programme starts with port 3000 by default.
As a result it is not possible to use Grafana in https with the standard port 443 and a private plugin.
Thanks, but if I use npx @grafana/toolkit plugin:sign --rootUrls https://your-domain.com/
and write nothing value in defaults.ini: http_port =
grafana start with 3000 by default, if I write 443 in defaults.ini at start of plugin appUrl is : https://your-domain.com:443/ and rootUrls is https://your-domain.com/ and not matches.
I think the problem is only I use the private plugin, I write plugin to connect, in SQL sintax, to a non stardard DB (advantage database)