Closed sharmaashish closed 5 years ago
This could very likely be due to the missing steps that are instead in the security repo's readme. I've copied it here in #304
I tried to set "disable_security=true" in config.ini but the problem remains. BTW the quip in the VM works well so I wonder which version it is.
I'm sorry to have left this issue hanging, can I offer any more help here?
Hello,
I am facing this same issue. I have followed the instructions regarding setting "disable_security=true" in config.ini and have also tried the workaround with Google API but I am seeing the same error. Has there been any resolution to this issue?
Best, Michael
Hello,
Apologies that you have been experiencing this issue. Which config.ini did you change? Unfortunately, this version of the system is quite picky to how it's modified due to the build steps. There should be a copy of the source config.ini in your data directory, and this one should be live. If all else fails, you can edit the config.ini directly in the viewer container. Please let me know if you would like assistance or troubleshooting help with this, and I'll use that to better update the documentation.
Thank you for reporting, Ryan
Hi Ryan,
Thank you for your response. I proceeded to edit the config.ini file in the data directory and the web application now seems to be working. I will update you if I encounter any further issues.
Best, Michael
In the past week, two separate users have tried to install QuIP using our instructions. They both got stuck on the Google OAuth client signup