For the last 9 hours our self hosted Apose Cloud server is failing. /words/info appears to return an empty object “{}”. The docker log shows the error below. We have tried restarting the docker container. Please advise.
LicenseInitializer:InitLicense() - Failed to initialize metered license for Aspose.Words
System.InvalidOperationException: Authentication failed.
at w.Fu(Object d)
at w.ou(Object d)
at w.Xr(w d, B v)
at w.Ng()
at w.hm(Boolean d)
at w.Fu(Object d)
at w.ou(Object d)
at w.mg()
at w.Eg(Object d, UInt32 v)
at w.hm(Boolean d)
at w.Uu(Object[] d, Type[] v, Type[] c, Object[] t)
at w.Mu(Stream d, String v, Object[] c, Type[] t, Type[] n, Object[] B)
at w.Xu(Stream d, String v, Object[] c)
at w.Ju(Stream d, String v, Object[] c)
at Aspose.Words.Metered.SetMeteredKey(String publicKey, String privateKey)
at Aspose.Words.Cloud.LicenseInitializer.InitMeteredLicense(String , String)
@digiwise
It seems that your self-hosted Aspose Cloud server is encountering an authentication issue related to the metered license for Aspose.Words. The error message indicates that the initialization of the license has failed due to an authentication failure.
Here are some steps you can take to troubleshoot and resolve this issue:
-
Check License Credentials: Ensure that you are using the correct metered license credentials (public key and private key). The credentials for the self-hosted version are different from those used in the Aspose hosted cloud service. If you haven’t done so already, you may need to contact the Aspose sales team to obtain the correct metered license keys.
-
Configuration Parameters: Make sure that you have set the necessary parameters correctly in your configuration. The parameters for the license (LicensePublicKey and LicensePrivateKey) are distinct from the authentication parameters (User and Password). Ensure that all parameters are configured properly in your setup.
-
Update Docker Container: Verify that you are using the latest version of the Aspose.Words Cloud Docker Container. If you are not on the latest version, consider updating to the most recent release, as it may contain important fixes and improvements.
-
Logs and Debugging: If the issue persists, check the Docker logs for any additional error messages that might provide more context. You may also want to share screenshots or a video of the issue along with your configuration file for further assistance.
If you follow these steps and still encounter issues, please provide more details about your configuration and any additional error messages you may be seeing. This will help in diagnosing the problem more effectively.
Sources:
[1]: Aspose.Words Docker Container - Authentication Failed Error
[2]: Aspose.Words Docker Container - Authentication Failed Error
[3]: Aspose.Words Docker Container - Authentication Failed Error
The service ‘came good’ about an hour after my previous post. No changes were made at our end. I assume this means it was an issue at Aspose’s end. Can a human please advise what went wrong with the service and what has been done to prevent recurrence?
It might be the case that when you tried to start container the billing was offline for some reason. After it came back you successfully started container