I'm trying to automate deploying a site to our production server after a build. The production server is hosted by some third party provider and is not on our LAN.
If I:
Install Web Deploy on our build machine (source)
Install Web Deploy on the production machine (destination)
Install the additional Web Deploy Remote Service on the production machine
Given that the production machine is "out in the wild," how is the service secured such that only I can publish files to the production machine? Does it use windows authentication?
It uses windows authentication.
See the following KB article to see how to secure the service:
http://technet.microsoft.com/en-us/library/dd569093(WS.10).aspx
Related
I'm trying to deploy the simplest ASP.NET Core 2.1 Web App (Razor or MVC) I can imagine from Visual Studio 2017 15.8.2
and still failing.
I followed the instructions in
https://github.com/aspnet/Tooling/blob/AspNetVMs/docs/create-asp-net-vm-with-webdeploy.md
step by step
finished creating VM
checked the web management service is up and running
installed Web Deploy 3.6 as described above tutorial
installed Windows features required - ASP.NET 4.6
Port 80 (http) and 8172 (WebDeploy) is open
checked the inbound rules in Azure portal
and Windows Firewall in Remote Desktop
But WebDeploy still fails.
I used the credentials when I log on to the VM using RDP
It says
ERROR_COULD_NOT_CONNECT_TO_REMOTESVC
but I checked the web management service is running
Also, when trying to configure deploy profile, 'Validate Connection' fails without any error message.
What am I missing?
When installing Web Deploy 3.6, choose custom and select all checkboxes.
'Typical' setup does't work.
End up with "500 - Internal server error", but hey,
at least file uploading works, and that's a huge step for MSFT, huh?
EDIT: When Web Deploy 3.6 was installed with 'typcial', the web management service was not running and set 'manual' so I turned it on and set the startup type 'automatic' in [services] but the problem continued. So I changed the Web Deploy setup to custom/select all and succeeded uploading.
I have simple ASP.Net web app in which there is Socket connection implementation.
It is working in local IIS Server, but not working when deployed on Azure.
Source Code on GitHub.
It is working in local IIS Server, but not working when deployed on Azure.
I previously followed this tutorial to build my web application with WebSockets. Per my understanding, you need to enable the Web sockets option under the "SETTINGS > Application settings" of your Azure web App on Azure Portal. Moreover, here is a similar tutorial about Introduction to WebSockets on Windows Azure Web Sites, you could refer to it.
UPDATE:
For using SSL for WebSockets under Azure Web Apps, you could just connect to wss://{your-appname}.azurewebsites.net (WebSockets over HTTPS). Azure Web Sites supports SSL even on free sites by using a default SSL certificate for *.azurewebsites.net. Details you could follow this tutorial.
TEST:
Additionally, if it does not work in your web app, you could leverage the Log stream under the MONITORING section of your app service on Azure Portal to retrieve the detailed error message to narrow this issue.
Actually,I got error when I deploy use "MSDeployUseChecksum" ,if remove "MSDeployUseChecksum", deploy will successed. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4295,5): msdeploy error ERROR_PROXY_GATEWAY: Web deployment task failed. (Could not connect to the remote computer ("dev-cms.scm.didix-dev-ase.p.azurewebsites.net") using the specified process ("Web Management Service"). This can happen if a proxy server is interrupting communication with the destination server. Disable the proxy server and try again. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_PROXY_GATEWAY.
pubxml file
When I'm trying to publish using Web Deploy (Visual Studio 2017 for Windows) to a Linux app service hosted in Azure the following error occurs:
Could not connect to the remote computer ("my-linux-api.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.
The remote server returned an error: (405) Method Not Allowed.
The link in the error description seems to refer windows based hosts.
The service is up and running and responds to my request:
How can I fix that?
There is no Web Deploy on Linux. That's a Windows/IIS thing.
Push with git instead. The .scm. service (Kudu) knows how to handle the ASP.NET Core deployment on Linux.
I am trying to understand why the same C# Oracle access code works under VS2010 environment but not under IIS.
I am building a web service to access Oracle 9.2 database on the remote machine. The web service must be hosted in the IIS under Windows 2003 machine. The same machine is hosting Oracle 9.2 database.
The web service must be compiled for x86 CPU because of Windows 2003 that is 32-bit architecture.
My Visual Studio project is WCF Application.
When I run the service under ASP.NET Development Server everything works fine. The database is connected and all CRUD operations are possible.
When I deploy everything under IIS on my machine or any other machine the I am getting "ORA-03134: Connections to this server version are no longer supported." at the time of connecting.
I supposed it is some kind of permission problem so I run the service under special Application Pool with LocalSystem account. I even gave to the Oracle client folder installed on my machine Full Control permissions for IIS users but this should not be needed because of LocalSystem account.
Anyway I tried and nothing. It is always the same error.
What could be the reason ?