#1178 - Public Key is required
Hello, we installed SugarChimp-7.1.5-professional-for-Sugar6.zip and tried to enter the license key and it always says "Public Key is required". Even as we tested the Link from the logfile "https://www.sugaroutfitters.com/api/v1/key/validate?key=...." in Firefox, we got only the information "Public Key is required". What could be the Problem?
thx and kind regards Daniel
9 years ago
Hi Daniel, I can help with this.
What version and edition of Sugar are you running? In the menu at the top right, there should be an About option that tells you all of this.
Thanks!
9 years ago
Hi, thx for the fast reply, its Version 6.5.20 (Build 1001) regards Daniel
9 years ago
Thanks for the details. It sounds like the installation process didn't may not have copied over all of the necessary files for SugarChimp to work properly. Sometimes Sugar will do this when installing a module. You can try re-installing SugarChimp again to see if it gets past the licensing step this time.
If it doesn't, there may be a permissions issue on your Sugar instance that is preventing all of the SugarChimp files to be properly added. Here are a few links to check out for that:
http://support.sugarcrm.com/04_Knowledge_Base/02Administration/100Install/Required_File_System_Permissions_on_Linux/ http://support.sugarcrm.com/04_Knowledge_Base/02Administration/100Install/Setting_File_Permissions_and_Ownership_in_config.php/ http://www.shanedowling.com/sugarcrm-permissions-script/
Let me know what you find on this. Thanks!
9 years ago
Hi, we installed it already three times Wy is the link used in the browser-Url gives always "Public Key is required" too?
thx and regards Daniel
9 years ago
Hi Daniel, I'm not sure why you're seeing that. SugarChimp is in a really stable place right now, so usually issues like this are related to permission issues on the server your Sugar instance is running on.
Let's take this conversation to email to see if we can better diagnose what's going on. Be looking for an email from us. Thanks!
9 years ago
The issue seemed to be the particular web host they were using and php 5.3+ wasn't being used. After moving to a system with php 5.5, all is working.
I'm going to close this case for now. Create a new case or shoot us an email if you need anything else. Thanks!