Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 1 year ago.
Improve this question
I have an application deployed to google cloud (java 11/ spring, classic stack) for over a year and a half (feb 2020) and it worked flawlessly until now.
I had CORS configured like this
#Bean
public FilterRegistrationBean simpleCorsFilter() {
UrlBasedCorsConfigurationSource source = new UrlBasedCorsConfigurationSource();
CorsConfiguration config = new CorsConfiguration();
config.setAllowCredentials(true);
config.setAllowedOrigins(Collections.singletonList("*")); // bad practice i know
config.setAllowedMethods(Collections.singletonList("*"));
config.setAllowedHeaders(Collections.singletonList("*"));
source.registerCorsConfiguration("/**", config);
FilterRegistrationBean bean = new FilterRegistrationBean(new CorsFilter(source), new ServletRegistrationBean[0]);
bean.setOrder(-2147483648);
return bean;
}
And frontend is hosted on firebase.
Since year and half nobody redeployed anything, but it started throwing CORS errors just now.
Is there some update google cloud / some policy I missed that it stopped working all of a sudden? Tried on EDGE and CHrome, as well as Safari, so it should not be browser...
Okay nevermind, so I found out that the BILLING ACCOUNT has expired somehow. Then the server was turned off and in that case you get this weird CORS error.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 14 days ago.
The community reviewed whether to reopen this question 14 days ago and left it closed:
Original close reason(s) were not resolved
Improve this question
My SSL certificate is stuck at Pending Validation. It eventually fails and times out after few days.
I own my domain on Route 53 and added the CNAME record in the newly created Public Hosted Zone. While requesting a certificate, I put fully qualifed domain name as watsky1337.link. I tried *.watsky1337.link but that also didn't change the outcome.
My cloudformation template for creating the certificate request:
{
"Resources":{
"MyCertificate":{
"Type":"AWS::CertificateManager::Certificate",
"Properties":{
"DomainName":"*.watsky1337.link",
"ValidationMethod":"DNS"
}
}
}
}
And, cloudformation template for adding CNAME record to the Public Hosted Zone:
{
"Resources": {
"myDNSRecord": {
"Type": "AWS::Route53::RecordSet",
"Properties": {
"HostedZoneId": "Z01832163FDLRM2C7PVYW",
"Name": "_42fb819b92f98e5ef699548b8d5a52df.watsky1337.link",
"ResourceRecords": [
"_13b8185f6fa218a71d9fbb82bfbe705c.ndlxkpgcgs.acm-validations.aws."
],
"Type": "CNAME",
"TTL": "900"
}
}
}
}
Here's a detailed view of the Certificate
And here are the record sets in this hosted zone
I have the required permissions to do all this because this is my own personal AWS account.
I tried to troubleshoot it by checking if my nameservers are visible if I check it on CLI but they aren't. What am I doing wrong?
Based on Mark B's comment, I changed the nameservers in registrar to the ones in public hosted zone so that they're same.
And now my Certificate's status is issued:
Nameservers are also visible now:
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I test ray on local with different machines. Most of them run fine but one of these got (pid=raylet) E0515 16:26:30.978312 358451 node_manager.cc:3537] Failed to send get core worker stats request: IOError: 8: Sent message larger than max (290460356 vs. 104857600) this warning. And the performance in this machine dose lower then others. If there are any connections between them?
When Ray head cluster is initialized, it starts a built-in dashboard which collects metrics across the cluster. I guess since your cluster is really large, some of this requests exceed the max request size.
In this case, you can turn off the dashboard. You can do this by setting an argument --include-web-ui when you launch the head node. For example,
If you launch the head node from the script.
ray.init(include_webui=False)
If you launch the head node using the command line tool
ray start --include-webui=False
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I would like to set up my workmail to get an incoming email but, I cannot see how and I have this message:
Your domain's incoming mail is not enabled
I think the original asker has abandoned this thread. But it is an issue that many people are struggling with and nobody has a really good answer. So I am going to show the screenshot as Flux was asking in the comment.
I am known to answer my own questions here, so by me getting on the case I will hopefully be able to catalyze a definitive answer.
I am managing my domain with AWS Rout 56 also, and surprised that there is nothing in workMail to just automatically set this up. You see that there are 3 DKIM related CNAME records that are said to be "Pending". This is odd, because I had many other records that needed setup, and I set them up manually and hit the retry button and every time it was discovering the DNS change immediately. Only with these 3 records it keeps with this weird "Pending" status.
Definitely in my case that 72 hours issue should not be an issue, it's not about DNS propagation. There is something else about this DKIM which is causing the "Pending" status.
UPDATE: This "Pending" status has now (~4 hours later) gone to "Verified". So there is nothing wrong with the DNS settings any more. Still the message remains "Your domain's incoming mail is not enabled."
Another thing that has been said elsewhere was to check the SES rules. I had a little clash trying to set up SES rules before I discovered WorkMail, then I went to set up WorkMail but deleted my bad SES rules. So now I added one simple rule back:
Under SES "Configure Email Receiving" there is one rule set called INBOUND_MAIL. In that under "View Active Rule Set" I created one rule:
Recipients: c...t.org
Actions:
1. WorkMail Action
Deliver mail to WorkMail organization m-26...71
Which is the ARN of my WorkMail organization. So that's there.
Still, with all that it keeps saying inbound email is not configured. In Thuderbird I have set up outbound email with IMAP and SMTP just fine, but replying to the emails sent from the new organization will always bounce with:
550 5.1.1 Requested action not taken: mailbox unavailable
UPDATE: I haven't forgotten about this issue yet, still not figured it out, but I will and will report here.
I'm trying several times to deploy a new version of a service on my app engine flexible instance using the sdk and the command gcloud app deploy, but all i get is this error
"ERROR: (gcloud.app.deploy) Error Response: [4] Timed out waiting for
the app infrastructure to become healthy."
.
I Couldn't found any answer about it on the issue tracker of gcp.
On this question, he got the same problem, but no one could answered it.
Any guidance will be very helpfull.
According to the gcp team, this particular error was caused because we reached the "In-use IP addresses" quota limit.
They also said that are working on improve the error messages.
"The engineering team has just created a fix for better quota error
details. There is no ETA for when the fix will be released, but I
would guess it would be in the next version of gcloud."
Over half a year later after Loneck's answer I've got the same error. I guessed it could be anything. This is why I've choosen to delete the project, create a new one in a new zone and deployed it there. Then it worked for me. It might have been any other limitation in the zone that I've choosen at the beginning.
I ran into this and solved it by retrying the deploy 3 times.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I am trying to move a traveler profile into a PNR by sending the "NM" Sabre command via the SabreCommandLLSRQ web service call and get "Invalid Input for GDS" as the response. This command works via Sabre Red, but for some reason doesn't seem support via webservice.
Is there a list of unsupported commands, or is there something I'm missing?
Apparently, the Output format of the request was set to "SDS" instead of "SCREEN" and that apparently has some serious side effects on what commands can be executed.
Is this for Legacy Stars or new Sabre Profiles?
Have you checked out the Move Profile to PNR service API?
https://developer.sabre.com/docs/read/soap_apis/profiles/build_reservation/Copy_Profile_to_Itinerary
Might not be relevant, but if you're using PassengerDetailsRQ you can just set UniqueId on ProfileRQ
https://developer.sabre.com/docs/read/soap_apis/management/itinerary/Passenger_Details
Blockquote I like to connect Flights api App using php file dsbridge.php by making
ajax request to the class curl Bridge getting array response
error - invalid_client
error_descr - Credentials are missing or the syntax is not correct.
When I make the _dsAppKey using base64 tool using this procedure.
1. Base64 your Client Id
2. Base64 Client Secret
3. Concatenate both Base64 values with a :
4. Base64 the concatenation.
It still gives me the Response code as NULL. This code gives me the
Access token. You have to send another request to the Sabre Api.
Pl. help me with the complete example.