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 1 year ago.
Improve this question
I keep getting this when I try to visit a website that I have previously visited many times before.
403 ERROR
The request could not be satisfied.
The Amazon CloudFront distribution is configured to block access from your country. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: db4AJqwG88H12zSDESOE7SIS8twSWZGScHR005VdWdEQ4RF8fx_ITA==
This might mean that the website is blocked on your country, your IP is blocked, or the website it's wrongly configured.
You can try contacting the site owner. 😉
Related
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 1 year ago.
Improve this question
I have just moved a MERN Stack app to AWS and I'm currently facing some problems with the certificates.
Current Scenario:
My website (example.com) has Cloudflare as the DNS Management.
I have added Cloudflare's Full SSL (end-to-end) encryption and a page rule for always redirect to https.
On the AWS Side, I have an Application Load Balancer (ALB) which is having a listener for HTTPS:443 using the certificate provided by AWS CA for example.com.
Problem:
When making a call to example.com, it redirects me to https://example.com and renders the static page which is fine.
When I change the page to https://example.com/articles the website goes berserk and changes it to http://example.com/articles and the certificate sign shows insecure now! Although, I do get my articles response from the server. Moreover, this is only happening in chrome and not firefox!
I would be more than happy to share any details/images required to support my query.
Thanks in advance!
Please share your page rules here. Your page rules are getting problem for you.
You can use the Always Use HTTPS function provided without wasting your page rules.
so I've followed the documentation of Amazon's S3 and Route 53 to host a static website.
it worked perfectly and the next day my site was online. I kept updating my index.html afterward with small stuff like extra Text here and there and so far I had no issues, it would every time update the site to reflect the new changes. Until suddenly I visit my website and get a "server IP address could not be found" and I cannot reach my website.
I checked dnschecker.org and internic.net to verify the DNS status of my site, and it showed everything green. I created an Availability test in the Route 53 dashboard and it returns 200 OK.
I also made sure the 4 server names from the Hosted Zone match the ones internic is returning.
so apparently every service says that my site is reachable, but it's not. I have not changed any Public Access options since the first time after I've initially done it using the documentation.
I have also tried reaching the site from a different browser, different PC, and from my phone. they all cannot reach the website.
I absolutely have no idea what to do, to get my site back running. I would very much appreciate some insight.
Footnote: I am very new to this, so please let me know if I need to provide extra information
so it turned out the reason is that I was on the college's Network and somehow my website got delisted from their DNS server (I don't have an exact explanation, just an observation).
my website loaded using Data on my phone and also if I turned on a VPN on my PC. so basically its a DNS problem
I've made two IPs on 1 instance so I currently have two sites like http://example.com and http://example1.com
however the problem is the only one site has ssl setup (https://example.com)
so, when I try to connect to https://example1.com, it's automatically redirect to https://example.com.
I want to make 2 different sites with ssl. If you know any answers, please help me.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
How can I set cookies with c++ on a mongoose web server?
I found something here https://www.cesanta.com/developer/mongoose#_mg_http_parse_header But i'm not sure if is what I'm looking.
You should send a Set-Cookie HTTP header to the client. There multiple ways of doing that with mongoose, for example using mg_send_head() , https://www.cesanta.com/developer/mongoose#_mg_send_head :
mg_send_head(conn, 200, content_len, "Set-Cookie: token=1234; Expires=Wed, 09 Jun 2021 10:18:14 GMT");
Set-Cookie header format is described in https://www.rfc-editor.org/rfc/rfc6265. Wikipedia also has a good article on it, https://en.wikipedia.org/wiki/HTTP_cookie
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 8 years ago.
Improve this question
I am trying to make a graph api call to post status update to a fan pages.
I am using http post here
my base url: https://graph.facebook.com/{page_id}/feed
message=hi&access_token={access_token}
I am however getting an error
{"error":{"message":"An unexpected error has occurred. Please retry your request later.","type":"OAuthException","code":2}}
Could you tell me if I am missing anything?
Things I checked:
Access token is valid
Page exisits
You need the extended permission manage_pages for your app (or through graph explorer) to be able to publish to the page feed. Once you have a new access_token with that permission, this should work:
curl \
-F "message=hi" \
"https://graph.facebook.com/<page_id>/feed"
Or whatever method you prefer.
Edit: You may also need the page access token, as described in the Publish page API
There was a genuine bug at Fb's end.