FileZilla Connection timed out, Error Connecting to Server - ftp-client

I am having an issue with FileZilla, when I try access my FTP account, I get this:
Status: Connecting to xxx.xxx.xxx.xxx:xx (Ip adds:port)
Error: Connection timed out
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to (Ip adds:port)
Error: Connection timed out
Error: Could not connect to server
This was working fine till yesterday. It works on another pc, but its not working onn my pc now. I tried disabling Windows Firewall (as I am using Windows 8 OS). Also I completely reinstalled FileZilla, still that didn't do it. Is there anything more I can try?

I was connected to the Internet from another Laptop, with sharing the internet connection. So there was the problem, it had restricted to access the ports. When I connected directly to the Internet the problem was solved.

I had a similar issue. Turned out I was using an incorrect protocol to login to the ftp server. The ftp server was ssh secured. Selecting SFTP option instead of FTP worked for me.
https://vincent254.wordpress.com/2015/03/16/what-to-do-incase-you-get-this-filezilla-connection-error/

You might need to write the host in this format
ftp.example.com
This works if you are having the following error as well
ECONNREFUSED - Connection refused by server

Change Your Internet Connection then connect FileZilla
thanks

Related

NoMachine cannot connect to Debian server, error 138

I can't connect to the KDE GUI installed on my Debian server, using NoMachine. Connection over SSH (Both through PuTTy as X forwarding) works just fine, but somehow I can't figure out how to connect using NoMachine and the NX protocol.
I installed the NoMachine server on my Debian server (nomachine_5.1.54_1_amd64.deb), which seems to work fine. It listens on port 4000. I disabled the firewall on the server.
Then I installed NoMachine on my windows system and tried to connect to the server, using the same IP address as with the ssh connection, and the login credentials I use to login on the server.
I approach the server from another network, using a VPN connection and the HTTP proxy for the network connection.
I tried the tips provided online, but can't get it to work. I still get the error message:
Could not connect to the server.
Error is 138: Connection timed out
Help would be highly appreciated!
You should use the same IP address that is shown in the Welcome GUI like the attached image (taken from the nomachine website)
nomachine welcome gui showing where to connect

Does node.js server need internet connection to run?

I disable the internet connection and run the node server npm start, then it throws the error:
And now enabling internet connection and running the server works fine:
So, I want to confirm if this really needs to be connected to the internet while starting the server?
If it really needs internet connection, then is there any idea to run the server offline?
If I connect to the internet and run the server and there after plug out the internet connection then there's nothing goes wrong. Everything works fine. I don't know why just running the server requires the internet connection.
OMG! It's really cool! I got it working offline after hard research in my code using 127.0.0.1 instead of localhost for mongo uri.
Using localhost needed for me to connect to the internet.
And using 127.0.0.1 worked in both condition i.e. with internet connection and without internet connection.
But, really I'm totally amazed of this.
I found the really cool topic on this which made me clear about this.
If you use 127.0.0.1, then (intelligent) software will just turn that directly into an IP address and use it.
And there's no guarantee that your hosts file will actually be used for that resolution (first, or at all) so localhost may become a totally different IP address.

Can my chef-server and workstation be on different clouds ..?

Say .. I have a scenario where my workstation is in my local network and my chef server is in AWS . In knife.rb ,i gave the AWS Public IP in the chef server url. Will this work or not for open source chef .??
i tried doing that.i am getting the following error:-
ERROR: Network Error: Error connecting to https://xx.xx.xx.xx/cookbooks?num_versions=all - Connection timed out - connect(2)
Check your knife configuration and network settings
can some one help me out in this.
Sure, as long as your workstation (usually your PC/Mac) has IP connectivity to the Chef server that's how it works. Given your output, it looks like access to port 443 is not allowed (or you entered the wrong IP of your chef server).

How to tell on Linux (Lucid) if a connection is coming into the server?

So I have an issue where I am remotely connecting to a Mongodb on my linode box, and I am not longer able to access this DB. I can from my local machine, but when I am on this remote server (where the website runs) it is not working. I am not seeing the connection come into the Mongo logs, so this leads me to believe that maybe it is being intercepted by a firewall?
How can I watch traffic and see if this connection is at least making it to my linode box? I am connecting with Mongoid, so if there is a way to prove no connection there too.
Right now the only error I get is a erb view timeout execution error - not much to go on.
Thanks,
Daniel

Azure a connection attempt failed

I've a sitecore azure deployment 2.0. Unfortunately, when I try to run this from company network I get the error below:
A connection attempt failed because the connected party did not
properly respond after a period of time, or established connection
failed because connected host has failed to respond 213.199.180.206:80
When I try below on the same machine it works:
http://www.google.com
https://www.google.com
Wondering what exactly is causing the above issue given both 443 and 80 works well via IE.
Thanks.
Definitely sounds like a corporate firewall/gateway problem. Have written a blog post with my experiences of just these types of issues. http://reservoirdevs.wordpress.com/2013/10/18/sitecore-azure-walkthrough-and-gotchas/
My solution was to try from outside the corporate network. It then worked fine.
This sounds like your firewall on your Azure machine is not set to allow incoming http traffic on port 80. Although there could be a lot of other reasons for this timeout.

Resources