I loaded Bamboo server onto and AWS Ec2 instance but it is not secure. When I try to link Bamboo to Bitbucket I get a Failed to load data from Bitbucket. [403 Forbidden].
So after reading this post on correcting “XSRF Check failed” errors, I still get the 403 error, not sure what I am doing wrong, has anyone else gone through this problem?
what was done to finally fix it?
Thanks
Related
I´m trying to deploy a AWS EC2 Mac instance.
During the process of setting the instance up, I get asked to allocate a dedicated host for it.
When I try to do it, I keep getting the following message:
Your request for accessing resources in this region is being validated, and you will not be able to launch additional resources in this region until the validation is complete. We will notify you by email once your request has been validated. While normally resolved within minutes, please allow up to 4 hours for this process to complete. If the issue still persists, please let us know by writing to aws-verification#amazon.com for further assistance.
It´s been more than a day since I started trying, so the problem isn´t the 4 hours mentioned in the message.
Anyone has any ideas how to solve this?
Thank you!
Is the AWS account in which you are trying to provision those resources brand new?
Messages like the one you are seeing are usually seen in case the account in question hasn't been fully activated or lacks billing information.
If my assumption is correct check the root account email inbox for confirmation/verification email requests from AWS. And make sure that your credit card information is up to date.
My group had a web application running using Elastic Beanstalk. For several months, it worked fine, but now the website shows the error
'radiology-ai-env.eba-wgmpba4k.us-west-2.elasticbeanstalk.com is currently unable to handle this request.'
When I try to rebuild the environment, I get two error messages:
1.) LaunchWaitCondition failed. The expected number of EC2 instances were not initialized within the given time. Rebuild the environment. If this persists, contact support.
2.) Stack named 'awseb-e-pw8nbmshem-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].
I am wondering what can be changed to fix this issue, and would appreciate any help. Thank you so much in advance!! I can follow up with more info if it is helpful.
P.s. this is a flask python3 app
I have tested this app on local host and it works well, but when I try to deploy this app to the google cloud all I get is an error, which I can't seem to fix, I have tried even giving the compute engine and app engine the admin permission in iAM panel, but still no success, please help.
i have the code on github https://github.com/ManinderSinghAjimal/flask-test-app-1.git
The error:
ERROR: (gcloud.app.deploy) Error Response: [13] Flex operation projects/flask-1-281017/regions/asia-south1/operations/047ccf3a-d10b-446c-98fa-cf8b0030f076 error [INTERNAL]: An internal error occurred while processing task /appengine-flex-v1/insert_flex_deployment/flex_create_resources>2020-06-22T13:46:06.604Z15036.ow.0: Deployment Manager operation flask-1-281017/operation-1592833567657-5a8ac76fc8c66-e121f85c-538636c0 errors: [code: "RESOURCE_ERROR"
location: "/deployments/aef-default-20200622t191524/resources/aef-default-20200622t191524"
message: "{\"ResourceType\":\"compute.beta.regionAutoscaler\",\"ResourceErrorCode\":\"403\",\"ResourceErrorMessage\":{\"code\":403,\"message\":\"The caller does not have permission\",\"status\":\"PERMISSION_DENIED\",\"statusMessage\":\"Forbidden\",\"requestPath\":\"https://compute.googleapis.com/compute/beta/projects/flask-1-281017/regions/asia-south1/autoscalers\",\"httpMethod\":\"POST\"}}"
]
this actually makes no sense to me, so if anyone can suggest something, it will be really helpful.
This issue could be related to resources in the zone that your project is located (some time gcp resources get low in some zones and regions and it is difficult to deploy an app in that zone/region).You could try out different zones/regions for example instead asia-south1 you can try with asia-northeast3
after running AWS Elastic Beanstalk application for few weeks suddenly I can't open my application. Page simply displays an error which doesn't provide much information how to fix it.
Error
A problem occurred while loading your page: AWS Query failed to deserialize response
(and there is no more information, Googling also haven't found any answer)
So before updating my subscription and starting paying to Amazon not insignificant amount of money for being able to contact their technical support I thought I will ask here first if someone here encountered this issue.
Thanks for any suggestions.
After receiving this generic error, I was able to dig into the actual error message by using the EB CLI. In my case the CLI threw "ZIP does not support timestamps before 1980".
When trying to set up a HiveMQ (1.4.1) Cluster on AWS (using the bundles examples/cluster.xml file) the server upstart fails with an error:
Unable to load class for protocol pbcast.STREAMING_STATE_TRANSFER
There's really no more info on why this would fail.
The problem was that the examples/cluster.xml file used the old syntax for STREAMING_STATE_TRANSFER, while it should use just STATE_TRANSFER instead.
Hope that helps someone else. :)