Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
My QMC Portal was working before and I changed the prefix in Virtual Proxies and now I am getting
The operation failed due to insufficient privileges even for the root user.
How can I again reset or login ? I am being logged out of automatically. And when I try to open hub URL I the page keeps on reloading with message Connection Lost. Make Sure click sense is working.
Now you have learned the hard way to have an extra virtual proxy that admin can use if something goes wrong with the main virtual proxy.
You should probably open a support case to get the best help with this issue, but if you are on Qlik Sense Enterprise on Windows (on-prem) and you are brave enough you could try to alter the repository database. The virtual proxy prefixes are located in postgre->QSR->schemas->public.VirtualProxyConfigs. In your situation, I would consider trying to change the prefix there, back to what it was before you changed it through qmc. But I don't know if there's other repo alterations as well when the proxy prefix is changed in qmc, so it is possible that trying to fix this manually like this make your problem worse.
Be aware: I'm not a qlik support person, try this at your own risk and make sure to backup the repository database first, if you decide to try this approach.
Now you have learned the hard way to have an extra virtual proxy that admin can use if something goes wrong with the main virtual proxy.
You should probably open a support case to get the best help with this issue, but if you are on Qlik Sense Enterprise on Windows (on-prem) and you are brave enough you could try to alter the repository database. The virtual proxy prefixes are located in postgre->QSR->schemas->public.VirtualProxyConfigs. In your situation, I would consider trying to change the prefix there, back to what it was before you changed it through qmc. But I don't know if there's other repo alterations as well when the proxy prefix is changed in qmc, so it is possible that trying to fix this manually like this make your problem worse.
Be aware: I'm not a qlik support person, try this at your own risk and make sure to backup the repository database first, if you decide to try this approach.