I'm trying to deploy a parse application according to this document https://aws.amazon.com/it/blogs/mobile/how-to-set-up-parse-server-on-aws-using-aws-elastic-beanstalk/ .
I deployed the application in aws, created a mongolab cluster, copied the connection string in the environment panel and started the application.
If I try to test using curl according the aws tutorial I receive an interval server error.
How can I understand what's the problem?
Related
We are facing an issue on our application which uses google big query with OAuth authentication. When we run the application on docker container during runtime we get an authentication URL on the docker console like below :
Please open the following address in your browser:
https://accounts.google.com/o/oauth2/auth?access_type=offline&approval_prompt=auto&client_id=330834658013-dg6niu0iihdcatin3c3mi6haqebrjinm.apps.googleusercontent.com&redirect_uri=http://localhost:61984/Callback&response_type=code&scope=https://www.googleapis.com/auth/bigquery%20https://www.googleapis.com/auth/cloud-platform%20https://www.googleapis.com/auth/drive
If we open the URL outside the container in the browser. We do not get the response and application get failed.
We tried to run the application other than docker container, we found that It automatically redirect to the browser and successfully get the response after that an folder named as 'credentials' containing StoredCredentials file is created locally which get referred next time for authentication.
As described above, due to authentication is not done by URL on docker container. The credential folder is also not created. Could you explain the resolution on priority.
We tried to run the application other than docker, It is running successfully. As it automatically redirect the URL and completes the authentication. Same is expected on docker container as well.
I'm unable to start the WSO2am 3.0.0 . I have to replicate WSO2am from an environment. But when I do so, the service doesn't start , it keeps printing warning messages saying it cannot fetch certain things from the remote endpoint. This is a single node setup, with nginx as reverse proxy, and running on Amazon VM(Amazon linux 2) and RDS(MySql).
Attached are the screenshots of the logs printing the warnings.screenshot1 screenshot2
Preface
I've just finished the Getting Started with Endpoints for Cloud Run tutorial for the second time. When I first tried running this tutorial with my own Cloud Run app, I got either a 413 Request too large or 504 Upstream request timeout error. Thinking that I may have taken too large a leap trying to deploy Endpoints on my Cloud Run service, I started the tutorial over using only the tutorial code, i.e., creating a Cloud Run service with the Cloud Run quickstart and using the given YAML in the Endpoints tutorial. Unfortunately, again, after running through all the commands, enabling services, and deploying Endpoints, I get either 413 Request too large or 504 Upstream request timeout.
Issue
Following the Getting Started with Endpoints for Cloud Run, I get either a 413 Request too large or 504 Upstream request timeout error. I feel like I must be missing something major, as I can't find any other comments or documentation on this issue. Has anyone run into this issue before or does anyone have advice as to how I can debug the issue?
What I've Tried So Far
Beyond restarting the tutorial with the Cloud Run tutorial image, I've looked at the logs and seen that one request creates many error logs within milliseconds of each other. To be clear, the Cloud Run service is functioning, as I've tested both my own and Google's service without the Endpoints layer. I didn't have any issues accessing the services then.
Let me know what else I can provide, and thanks in advance for any help.
I was able to reproduce your issue.
In order to work with Cloud Endpoints with Cloud Run you need at least two services deployed:
Your destination service (hello), a dummy service can be created from the Quickstart.
The endpoint service (gateway), which will be the one redirecting the requests.
In this case you probably had HOST to wrongly be gateway-HASH-uc.a.run.app:
...
host: HOST
...
x-google-backend:
address: https://gateway-HASH-uc.a.run.app
The Host is the 2nd service, and the x-google-backend is the 1st service.
To fix the issue you have to deploy another service and redo the tutorial.
I have added this question on ServerFault but no one replied.
I have a .net application which calls a webservice deployed on my local windows server 2012 on IIS, and the sql server database resides on that server too. All employees connect to the same service and DB since we're all on the same domain, and I publish the app and webservice to the server through visual studio (2012).
Now I need to make employees access this application when they are outside the company's network, so I deployed the webservice on IIS on one of our remote windows 2012 servers, I created a public shared folder in my remote server and added to app webservice files to it and in visual studio I changed the publish method to web deploy and filled in the information as below:
Server: https://x.x.x.x/
Site Name: https://x.x.x.x/PublicFolder
Destication URL: https://x.x.x.x/PublicFolder/Application
When I click Validate Connection, it fails with the following message:
Could not connect to the remote computer ("x.x.x.x"). on the remote
computer make sure that Web Deploy is installed and that the required
process ("Web Management Service") is started. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Unable to connect to the remote server
Note that I tried to replace https with http and I got another error:
Could not connect to the remote computer ("x.x.x.x"). on the remote
computer make sure that Web Deploy is installed and that the required
process ("Web Management Service") is started. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_NOT_ADMIN.
the remote server returned an error: (401)Unauthorized
I went to the previous link and I did what they suggested:
Create a separate user group MSDepSvcUsers on remote computer.
Create an local account A on both local & remote computer.
Add A to MSDepSvcUsers on remote computer.
Use account A to publish, this will allow you to publish without
needing to use built-in admin account.
but the same error (NOT_ADMIN) remained
UPDATE: I found another possible solution:
Add/modify windows registery key
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\”
and set it “1”.
After I added this registry key, the error changed to:
site 'http:' does not exist ... #ERROR_SITE_DOES_NOT_EXIST
So now if I put wrong credentials, I get the unauthorized error, if I use correct credentials I get side does not exist error.
What should I do?
It worked!!
I mean the connection, it's now validated, all I had to do is change site name from "http://x.x.x.x/PublicFolder" to "Default Web Site\SiteName" !!
This was really confusing, finally got it!
hello friends i developed a simple java web application and hosted in vmware cloudfoundry but i am unable to launch my application in the browser . it gives this error
HTTP Status 404 - /
type Status report
message /
description The requested resource (/) is not available.
Apache Tomcat/6.0.35
kindly reply me at aravnd8babu#gmail.com
Did you add the application URL in your host file? If not add a new entry i.e:
Cloudfoundry-IP applicationName.vcap.me
In your local tomcat the URL is localhost:8080/applicationName but in cloudfoundry it is applicationName.vcap.me
Run the command "vmc apps" and provide the output.