Blog
- Home
- Blog
'Cannot find the DirectAdmin binary: Extraction failed' error
This article covers methods to resolve 'Cannot find the DirectAdmin binary: Extraction failed' error.
AWS s3 lambda 500 Internal Service Error - Fix it Now ?
This article covers methods to resolve AWS s3 lambda 500 Internal Service Error.
Basically, this error occurs if Lambda function's resource-based policy doesn’t include permission for your API to invoke the function.
This error occurs if your Lambda function's resource-based policy doesn't include permission for your API to invoke the function.
When you build an API Gateway API with standard Lambda integration using the API Gateway console, the console automatically adds the required permissions. However, when you set up a stage variable to call a Lambda function through your API, you must manually add these permissions.
Finally, To verify that the error is caused by missing permissions, review your API's logs.
Enable Git on Virtualmin - Best way to do it ?
This article covers steps to enable Git on Virtualmin.
To do this:
- Go to Webmin -> Webmin Configuration -> Webmin Modules.
- In the From ftp or http URL field, enter the URL .http://download.webmin.com/download/plugins/virtualmin-git.wbm.gz .
- Click the Install Module button.
Once the plugin is installed, you can enable it in Virtualmin as follows :
- Go to System Settings -> Features and Plugins.
- Check the box in the left hand column next to Git repositories.
- Click Save.
Webmin "Error code ssl_error_rx_record_too_long" - Fix it Now ?
This article covers how to troubleshoot "Error code ssl_error_rx_record_too_long" in Webmin. Usually the ssl_error_rx_record_too_long error means that the service is not speaking in SSL - for example, if you try to access an http-only service via https.
Are you sure that webmin is set up to talk in ssl on port :10000?
AWS S3 403 Forbidden Error - Fix it Now ?
This article covers methods to fix HTTP 403 Forbidden error for our customers.
To troubleshoot the HTTP 403 Forbidden error from the Amazon S3 console, check the following:
- Missing permissions to s3:PutObject or s3:PutObjectAcl.
- Missing permissions to use an AWS Key Management Service (AWS KMS) key.
- Explicit deny statement in the bucket policy.
- Bucket access control list (ACL) doesn't allow the AWS account root user to write objects.
- AWS Organizations service control policy doesn't allow access to Amazon S3.
Plesk AH01071: got error 'primary script unknown' - Fix it Now ?
This article covers how to resolve AH01071: got error 'primary script unknown' in Plesk for our customers. This can happen as a result of Incorrect permissions on domain's folder.
