I am working with azure cloud service.
I tried to deploy simple web role to azure as cloud service. My web role just a simple asp net mvc app which convert html to pdf(I am using hiqpdf for conversion) without connection to db.
My web role deployed successfully, Virtual Machine was created and i can access my site through rdp on local iis of VM.
But i cannot access site through public url(my.cloudapp.net) b/c of error: ERR_CONNECTION_TIMED_OUT.
Related
I am currently trying to run an integration test with Selenium on the following setup:
IdentityServer4 hosted in a net core 3.1 REST service - running in its own docker container (securityservice)
MVC Test Web User Interface running under net core 3.1 - running in its own docker container (testuserinterface)
The selenium test is running on my local pc under a net core 3.1 test project
Where I am getting the issue is when i attempt to access a secure page on the Web Application the redirect is attempted to the identity server to show the user login page, however the url that the redirect is setup with id that of the docker container (e.g. http://securityservice/accouunt/login). This url is not accessible from my local browser so my test is failing locally.
Is there a way that the login url can be customised (only for test purposes) to be that of the local machine and the locally exposed docker port (e.g. http://127.0.0.1:dockerport/account/login).
I have tried many different examples and combinations with currently no success.
Any help in this area would be most appreciated.
Thanks in advance,
Stuart
What I have done for local development and testing in some cases is to create a local HTTPS certificate using mkcert and then in my local host file add an entry to map the domain of the certificate to 127.0.0.1
So I can use urls like https://identityservice:6001 to point to my IdentityServer.
We have a .NET CORE web application running in Docker container on Linux. Our application connects to SQL Server. We have a requirement to connect to the database using Windows Authentication, and from my IIS experience I know that application needs to run within the context of the AD user that will be used to connect to SQL using Windows Auth.
Am I correct in this assumption? How do I define this with web app running on Kestrel in Linux Docker?
I have created a web application using SQL Server as a database.
My client don't provide internet access to his employees.
So how can i deploy a MVC web application there so that it can be accessed by everyone which are connected to each other locally.
Publish your web application by right click on your application and select publish option to a local folder on your file system.
Provide published code to you client's IT group.
Put your database inside App_Data folder
If MVC framework is not installed on client server machine then you will have to request you client install MVC framework on server machine and then configure application on IIS.
For help you can check given below link -
How do I deploy MVC3 Hello World App to localhost and configure IIS
I can access a web service from remote machine through vpn.
And cannot access that web service from my local machine. I tried to install Visual studio in remote machine but there is no enough space.
I would like to create a web application and deploy it in remote machine, which will test that web service. Is it possible? or please let me know how to test that web service through my mvc web application.
We have created a Windows server 2012 virtual machine is Azure and deployed ASP.NET MVC website in IIS. Right now, we have enabled IIS logging and its saving log files on local disk.
Is there any way by which we can save IIS logs to Azure blob storage or table storage?
There are lot of articles about how to do this in web role OR in Azure Web Site, but not for IIS in manually created virtual machine.
Thanks for the help!
You'll need to write a process to export them to external storage. Web Roles use the azure PaaS agent which isn't currently available in IaaS. Web Sites are a higher level service built on PaaS so the agent is available there already.
If you poke around, I'm sure there are several sample projects already available that will help with this.