Locally deploying content between two site instances works fine.
It's when moving one instance to a remote server that gives me the following error message:
Module : login
Description : Remote user
Result : Error
Message : Connection timed out
My apache access log entries are:
./node_operations/deploy_now/86 HTTP/1.1" 302
./admin/build/deploy/logs/details/6 HTTP/1.1" 200
Deployment module version: 6.x-1.x-dev
Service module version: 6.x-2.2
Does anybody have an idea what could cause this problem?
Probably firewall is blocking if you are seeing timeout. You can fire up telnet on the dev box and test that you can actually connect to the target over port 80 - since deployment module uses xmlrpc to push content. If all is working there you can check the Drupal watchdog logs.
Related
I have an Xamp server running on MacOs 10.14.6.
I activated port forwarding on it like that :
localhost:8080 -> 80 (Over SSH)
localhost:8443 -> 443 (Over SSH)
I can navigate to my website on localhost:8443 with no issue.
I have another server running Symfony 5.4 available at localhost:8000. I can navigate to this website with no issue too.
But from the 'Xamp hosted' website, I'm not able to make a request to the 'Symfony hosted' server. I have a "Connection Refused error".
I tried to request both 127.0.0.1:8000 and localhost:8000 : same behavior.
I tried to set the Symfony server to listen to a different port too : same behavior.
It only works when I make a request to the real local ip address (like 192.168.1.34:8000). The problem is that this IP is not stable so I'd like to make the localhost work properly.
What could be the cause of this error ?
What can I do to use localhost hostname for my requests ?
you can disable the task manager section for applications running on the same port which may when you want to request a connection on the server you will use it will get a similar rejection. I think it's more or less like that
I installed pydio with cells v3 on my windows server behind nginx.
The service is up and reachable from both the outside the network at sub.domain.com and within my network using the servers local IP. From outside, SSL is working, from inside the self-issued SSL certificate is used and flaged as insecure.
The browser interface is working perfectly fine. However, I can't log in using the win-desktop client or andriod app. Entering https://sub.domain.com and clicking 'Username' opens the browser and I get a 520 'Web server is returning an unknown error.' Before the error, the pydio interface is rendered for a few milliseconds:
Connecting...
Application is not yet connected to agent. Please wait
while we are trying to connect...
followed immediately by
Disconnecting
Application is disconnected from agent. Please wait
while we are trying to reconnect...
However, the logs in the admin page don't show any errors.
Interestingly, when the 520 error is shown in the browser, the URL begins with domain.com, not sub.domain.com.
I have only mapped sub.domain.com to internal-server-IP:8080 in nginx.
Am I missing something here?
I have developed a app using bokeh and running it using
bokeh serve app.py.
The app is running fine on local, but when I deploy it on prod (kubernetes), it shows following errors:
On application log
400 GET /app/ws (100.110.109.133) 0.46ms
On Browser console
bokeh.min.js?v=57d29d5936e494351385d736f792154c:551 WebSocket connection to 'ws://***/app/ws' failed: Error during WebSocket handshake: Unexpected response code: 400
bokeh.min.js?v=57d29d5936e494351385d736f792154c:551 [bokeh] Failed to connect to Bokeh server: Could not open websocket
xqTrUSbsN4huCcddNcjrkVZtk46inlGUacd44jX5kzED: Error: Could not open websocket
How to debug the cause of issue? I think something is not right in k8 infra, some header is blocked or nginx config is the issue but how to debug the cause?
How to debug the cause of issue?
Since you have a working setup, just compare two sets of headers for the ws requests - one from the working setup and one from the not working one.
Find the missing headers or headers with seemingly wrong values and try to find out why they're missing or being replaced.
I got 2 servers with two equal wcf services hosted on them and one client application server. I can connect to endpoints and send a requests to both services using test wcf client app (.NET Web Service Studio) from my local machine successfully. But when I am trying to connect from client application server using the same test wcf client app I successfully connected only to the one wcf service server, but I have got an error when connecting to another one:
System.Net.WebException: There was an error downloading 'https://XXX/XXX?wsdl'. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it XX.XXX.XX.XXX:443
I performed netstat -an | find "443" command in command prompt on the client server and on my local machine to find out the difference and here what I have got:
1. On my local machine:
2. On the client app server:
What I already tried to do on client application server is:
- turned off firewall;
- stopped windows firewall service
- uninstalled mcafee virusscan enterprise application.
(I tried to set "prevent mass mailing worms from send mail" first, but mcafee was in foreign language that I don't understand, so I just uninstalled it)
after running command netstat -aon | findstr "443" on client application server I have got this result:
but I still got an error.
Does anybody know how to solve this issue?
Could be the problem on the wcf service server side?
The solution was predictable simple one - firewall was blocking the port,
but it's important to notice that the issue was caused by firewall on the wcf service server side, but not on client application server, which is making the request to that service.
I asked the technical support of that server, and they made firewall changes.
After that error was disappeared.
I faced the same issue and tried different ways to fix this. Nothing works. Later i found the issue which is, the application i tried to run is https and in my IIS, https binding was not created. I created binding https with the website and it works.
I installed a fresh AMI for EC2 (http://aws.amazon.com/amis/Microsoft/5147732567196848) and have installed Web deploy 2.1 on it.
The web deploy 2.1 service is running for real as
netstat -an
Shows 8172 is being listened on by the Web Deployment Agent Service.
But, when I try to deploy to this site using Project->right-click->Publish (via web deploy) I receive the following error message
------ Build started: Project: Cir.Web, Configuration: Debug Any CPU ------
Cir.Web -> C:\Projects\CrazyInsaneRobot\Source\Cir.Web\bin\Cir.Web.dll
------ Publish started: Project: Cir.Web, Configuration: Debug Any CPU ------
Transformed Web.config using Web.Debug.config into obj\Debug\TransformWebConfig\transformed\Web.config.
Auto ConnectionString Transformed Views\Web.config into obj\Debug\CSAutoParameterize\transformed\Views\Web.config.
Auto ConnectionString Transformed obj\Debug\TransformWebConfig\transformed\Web.config into obj\Debug\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Debug\Package\PackageTmp.
Start Web Deploy Publish the Application/package to https://ec2-175-41-170-198.ap-southeast-1.compute.amazonaws.com:8172/msdeploy.axd?site=Default%20Web%20Site ...
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): Warning : Retrying the sync because a socket error (10054) occurred.
Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): Warning : Retrying the sync because a socket error (10054) occurred.
Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 2 of
...
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): Warning : Retrying the sync because a socket error (10054) occurred.
Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 10 of 10.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): Error : Web deployment task failed.(Could not complete the request to remote agent URL 'https://ec2-175-41-170-198.ap-southeast-1.compute.amazonaws.com:8172/msdeploy.axd?site=Default Web Site'.)
This error indicates that you cannot connect to the server. Make sure the service URL is correct, firewall and network settings on this computer and on the server computer are configured properly, and the appropriate services have been started on the server.
Error details:
Could not complete the request to remote agent URL 'https://ec2-175-41-170-198.ap-southeast-1.compute.amazonaws.com:8172/msdeploy.axd?site=Default Web Site'.
The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Publish failed to deploy.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
My firewall on the EC2 instance has been turned off. And my AWS firewall settings are
which are the recommended settings.
Other notes/thoughts:
My Web Deploy Error log in the windows error log is completely empty
I've used web deploy before using a different AMI in the past and succeeded without problems.
If anyone has any suggestions about how to debug this, I would be so ever grateful!
I contact Microsoft directly about this problem and they had an immediate answer for me.
From MS guy:
It looks like your Web Management Service not contactable. I have seen this before when the certificate for the service is invalid. Can you run the attached script on your server?
Start a PowerShell prompt elevated
Run set-executionpolicy unrestricted –force
Run .\00_Certificate.ps1
Net stop wmsvc
Net start wmsvc
Does this fix the problem?
The script he is referring to is available here
This error can also occur when you specify the end point in the wrong format.
For example when selecting to publish an application Visual Studio gives examples of the end point format such as https://RemoteServer:8172/MsDeploy.axd
Turns out it actually wanted this without the http prefix e.g.
0.0.0.0:8172/MsDeploy.axd
If you get an error about certificates after this you just need to check the box allow untrusted certificates in the publish screen.
Agrahahah!
I had this same problem with Web Deploy when it was installed by the Web Platform Installer. After manually uninstalling and reinstalling Web Deploy directly (NOT using Web PI) it worked fine...
Some very helpful answers for an error message with many causes. I had this error and it turned out that the "IIS Web site/application" name used for the destination server was wrong.
So, causes for this could include:
Bad username or password
Incorrect web site name for destination (In Visual Studio, this is set on the Package/Publish Web tab of a web project's properties)
SSL cert for web management (for example if your server was sysprepped after IIS was installed)
I get the same error when i tried to deploy a website.
In the EventViewer (Windows Logs/System) i had an error log, that the log file of the Web Management Service could not be created ("Unable to create log file D:\Logfiles\WMSVC\W3SVC1\u_ex131126.log. Make sure that the logging directory is correct and this computer has write access to that directory.".
I just removed the readonly flag of the log folder and all worked fine again.