for some reason S3Bucketlogs was holding, and no was no reason of knowing why. Cloudtrail seems to be a solution in terms of properly debugging the situation. Capture and consolidate user activity and API usage across AWS Regions and accounts on a single, centrally controlled platform. AWS Cloudtrail https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-stuck-progress/ https://console.aws.amazon.com/cloudtrail/home?region=us-east-1#/[…]
An error occurred (ValidationError) when calling the CreateChangeSet operation: Parameters: [vars] must have values
once you create a stack with specific parameters, you must use those parameters throughout its entire existence or else you get this error
CloudFormation: One or more of the CNAMEs you provided are already associated with a different resource
Resource handler returned message: “Invalid request provided: One or more of the CNAMEs you provided are already associated with a different resource. (Service: CloudFront, Status Code: 409, Request ID: f820c050-6624-48c0-975d-7e3d9bb70eb3, Extended Request ID: null)” (RequestToken: 041d3aeb-f7a6-8313-9c74-c9c7d8c12c52, HandlerErrorCode: InvalidRequest) I already have a cloud distribution for the domain I’m creating the[…]
Configure aws credentials
inside of ~/.aws/, aws saves all of your profiles and corresponding information, like secrets and region.
Another update is currently in progress
https://www.wpbeginner.com/wp-tutorials/how-to-fix-another-update-in-process-error-in-wordpress/ delete this row and you should be good
throw error and remove all previous output
put a ob_start at the very beginning before anything gets outputted
NPM: pull packages from gitlab
lets say you want to download package from a private repo “werm-fw-templates” another way for project
.npmrc conflict
I was trying to publish to the package repo @werm-fw:registry https://gitlab.selectiont.com/api/v4/projects/543/packages/npm/ open up /root/.npmrc and remove these lines and it should work In npm.w I wrote a script that sets the registry right before it publishes it. If I don’t do this, it wont work, unless i set the “publishConfig”[…]
intentionaly throw “[emerg] host not found in upstream ” error in nginx
though this host does not exists, I do not get an error back from nginx. But if I add a subdomain