Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 19 hours ago.
Improve this question
I have hosted a website in Windows Amazon EC2 instance,
I am able to browse the website locally in the server.
But when browsing from outside I am getting a timeout error.
Plz help
Below is the URL:
http://ec2-18-188-142-103.us-east-2.compute.amazonaws.com:3000/
Below is the screenshot of the error
Please change security group and add a inbound rule
Add protocol and set your custom IP
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 6 days ago.
Improve this question
There is no (0, 0) LatLng. I changed the podfile and info file too.
I created the same API for both. Then I created a specific API for the iOS side and restricted it, again nothing changed. My app sends requests to the Google developers' API but does not show any traffic. I assume there is a problem, however, I could not fix it.
I appreciate your help. Thanks in advance.
This is the Traffic
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
Our app allows users to sign in with Instagram.
Everything works well in general but one user just submitted the issue:
When he tries to authorize in IG from our app, he receives the following error:
{"error_type":"OAuthException", "code":400, "error_message":"There was an error with your request. Please try again."}
Trying again does not help.
He still sees the issue and cannot connect his IG account.
Can anyone help at least with the direction we have to follow in our investigation?
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I just want to make sure before I go purchase anything.
I have an app on heroku. The URL is myappname.herokuapps.com on cedar stack.
I purchased a custom domain on godady and set up CNAME to make the forwarding work. I am able to use my custom domain to access the app on heroku. The problem is that, I get the browser warnings on FF, Chrome, IE, etc. The message is below:
This is probably not the site you are looking for!
You attempted to reach www.mydomain.com, but instead you actually reached a server identifying itself as *.herokuapp.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of www.mydomain.com.
You should not proceed, especially if you have never seen this warning before for this site.
My questions are:
I need to purchase a SSL to fix this right?
Do I need to get a wildcard certification or do any of them work?
Any recommendations on where to purchase it? I saw some options such as RapidSSL, SSL Endpoint add-on on Heroku, etc.
NO! You probably just didn't configured properly. Here you can check the steps. You probably didn't get the addon for custom domains.
The ssl add-on is only required if you want to use SSL and https. You should be able to browse to http://mycustomdomain.com/ without getting a warning. Going to https://mycustomdomain.com/ will yield the warning unless you add the ssl add-on and a certificate for the domain.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I created an website. For a week I had an under-construction-page, google did find that paged and indexed it. My question is: How did google find my site, while there were no links to this site and the name has never been used before?
Your domain name went in a domain name server. Google probably found it there.
There are so many websites that automatically gather Whois information of domain names with complete information about them. If you are pretty sure that you have never shown your domain to Google, i guess these websites did this.
You browser (Chrome) or your browser's plugin might have sent an anonimous report of your browsing statistics to Google - you did open your site in a browser right?
You weren't using a robots.txt file blocking Google.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 8 years ago.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
This question does not appear to be about programming within the scope defined in the help center.
Improve this question
I cant access the live domain for the Rails 3 application i created on my macbook. I can obviously access localhost:3000 for testing purposes, but when i log on to my live domain http://truthpage.me it sends the request and eventually times out. Doesnt work in any browser on my machine only. We are hosting the app with heroku if that makes any difference. Do any of you guys have a solution to why this doesnt work? thank you for your time.
Try flushing your DNS cache:
$> dscacheutil -flushcache
Also, ensure there's nothing causing an unintentional redirection in your hosts file for that domain:
$> cat /private/etc/hosts
Is this working from other machines or locations? If this is working from other location then it may be some issue with your local ISP. If you recently changed DNS records then it can also be a DNS propagation issue. Sometimes, it takes 24 hours to propagate the DNS across the globe.