I have a real-time application that is using SignalR. On development environment it's working perfectly so as in Azure. I redeployed the same app on AWS Elastic Beanstalk using IIS 10 on Windows server 2019 platform, I got the Handshake was canceled error. When I got this error on my development environment and Azure, all I did to fix this issue was to turn on Web Sockets. But I realize in AWS EB I do not have this possibility.
I'm wondering if the IIS 10 AWS EB support this feature. If it doesn't, is there any alternative to the SignalR?
Related
We are trying to host a custom Outlook Add-in on an AWS EC2 instance. We are using a windows server in EC2 to host this. Currently we are using webpack dev server to host it locally and everything is working fine. Now we need to deploy and have this app run as a service in the Windows Server.
We have tried to deploy the build on an IIS server. But we were not able to proceed after logging in to the application. We are getting the error as a Bad request. We also have tried to deploy it on Apache server using XAMP. But the results were the same. It is getting deployed in the webservers, however when we are hitting the backend application it seems to be erroring out.
The error we are getting is Error: redirect_uri_mismatch, when we try to authenticate and redirect to the authenticated home page of the application.
When we deploy the same using webpack-dev-server in the instance, It is working as indented.
We are facing issue to identify the proper reason for this error and unable to deploy the service in EC2.
EDIT
Screenshoot-1
Screenshot-2
We have an asp.net app that gets deployed to both On-Prem and on Azure VMs. We are trying to figure out how to configure the app so that when deployed on an Azure VM it will use Azure App Configuration Service, but when deployed On-Prem it will continue to use the settings in the config files?
How can we know on app start up whether or not we are deployed on an Azure VM?
If you can, I would recommend you add a special environment variable when you provision your Azure VM or deploy your application. If not, you may use Azure Instance Metadata Service to tell the code is running in Azure VMs.
I am using the amazon aws e2 to host a parse server database. It was working fine for the last couple of weeks, but today I got an error 503 saying: The server is temporarily unable to service your request due to maintenance downtime or capacity problems. My question is: is it because I'm using the free t2.micro tier and I have run out of quota? Or can there be some other problem? I just launched another instance and it seems to be working fine for now.
Have you set up a load balancer? Checkout Elastic Beanstalk, which manages EC2 instances to automatically spin servers up and down as your needs require it. Your server may have just crashed and nothign was set up to automatically redeploy it.
I'm facing some trouble while trying to start a windows service that I've created with Apache Daemon on an Amazon EC2 Instance (Windows Server 2012 R2). The error I'm getting is "Windows could not start the service_name on local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1."
I checked some other links and most of the similar problems are related to Apache servers issues, but I already have Apache Tomcat working perfectly here and the problem seems to be related to the windows service only.
Does anyone have any idea?
I am creating wso2 Paas on Amazon Ec2 by following the instructions in Quick Start Guide with Screencasts. After running the ./boot.sh am getting the following message.
Starting WSO2 Private PaaS server as ubuntu user...
Nothing happens after this message and the terminal is frozen after 2 hours.
I am using centos 6.7, screen terminal and amazon ec2 instance type is t1.micro, ami is Private PaaS ami-4e062c1c for doing this.
Please suggest a solution for this.
WSO2 has discontinued WSO2 Private PaaS solution. Please refer [1] for the new PaaS strategy. On AWS, WSO2 middleware can be deployed either on VMs using AWS deployment automation and autoscaling features or with containers using Kubernetes, DC/OS, ECS.
[1] http://wso2.com/cloud/paas/