I'm trying to connect to my server by FTPS (SSL) from Wordpress. But I'm getting failed to connect.
I'm using a different port, 2222 instead of 22. I can connect to the server with Filezilla or other programs but not with Wordpress.
And yes I'm inserting the port to hostname.
Hostname
xxx.xxx.xxx.xxx:2222
FTP/SSH Username
xxxxxxxxxx
FTP/SSH Password
xxxxxxxxxxxxxx
Connection Type
FTPS (SSL)
Error
Failed to connect to FTP Server xxx.xxx.xxx.xxx:2222
Related
There are more than 300 FTP users created by FileZilla Server manually in Windows Server 2012 R2.
We can use the existing FTP users (Port 21) with FileZilla and WinSCP for authentication (username and password as static).
With a policy of security, we need to use SFTP (Port 22) for file transfer. So, we've set up OpenSSH in the windows server and can telnet with port 22.
The problem are we can't use the existing FTP users to access the server using WinSCP with port 22, although opening port 22 already
I have website hosted on GCP windows VM on IIS and running absolutely fine with internal ip address of the machine. However when trying to access the website with same internal IP through VPN it does not work . Firewall rules have been added to allow 0.0.0.0/0 TCP:80 port.
when I did telnet I received following error "Could not open connection to the host, on port 80: Connect failed" Not sure what I am missing.
I want to forward the ip of my localhost server for being publicly accessible.
But while trying to configure my router on port 80(as it is localhost's listening port) it shows "Error: The port of the remote web management is conflicting with of the virtual server."
Is there any fix to it?
I was able to resolve this by updating the Web Management Port to a port other than 80. This setting for me was found under Security -> Remote Management -> Web Management Port.
After updating, I could enable port forwarding on port 80.
So a couple of days before, I tried creating a Home FTP Server, which I can access from my own network. It worked. But now I want to go further. I wanted my Home FTP Server accessible from any network via an external IPv4 address. So here is my problem.
Every time if I want to connect to my server on localhost or on my local IP address, it works. But when I try to connect with the same credentials on my external IP address, it says that it cannot retrieve the directory listing:
Status: Connecting to *************:800...
Status: Connection established, waiting for welcome message...
Status: Logged in
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is current directory.
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (**,***,*,***,***,106)
Command: MLSD
Error: The data connection could not be established: ECONNREFUSED - Connection refused by server
Response: 425 Can't open data connection for transfer of "/"
Error: Failed to retrieve directory listing
The (obfuscated) IP address in the 227 response does not match the (obfuscated) server IP address in the "Connecting to ..." message.
I tried turning off my firewall, forwarded port 21 and port 800 for both TCP and UDP, but nothing worked. I also made exceptions for both ports, and that didn't work as well.
Another problem is, that if I want to log in on my external IP address on my FileZilla Server, it shows this:
Connecting to server -censored-:14147...
Error, could not connect to server
Trying to reconnect in 5 seconds
My question is: how do I create a Home FTP Server which is can access remotely?
Response: 227 Entering Passive Mode (**,***,*,***,***,106)
Command: MLSD
Error: The data connection could not be established: ECONNREFUSED - Connection refused by server
If the IP address in the 227 response to the PASV command does not match the actual FTP server IP address, the server is misconfigured.
This usually happens, when the server is not aware of its external IP address and reports its internal IP address. But most FTP clients (including FileZilla) would be able to detect that by checking the IP address against a range of addresses reserved for local communications within a private network. See Server sent passive reply with unroutable address in FileZilla. As that did not happen, the server is probably explicitly configured with an incorrect IP address.
For generic information, see my article about network configuration needed for FTP.
You have to reconfigure the FTP server to the new IP address. In FileZilla FTP server you can do that by going to Edit > Settings > Passive mode settings > IPv4 specific > External Server IP Address for passive transfers in FileZilla Server Interface.
I'm running Sequel Pro 0.9.9.1 and can connect to a remote mySQL (v 14.14) database hosted on a server that only allows SSH connections. When I connect via Sequel Pro, I only need to fill out the ssh user and password to connect without issue. I am able to access all databases in this manner.
I then try to connect to the database in R (2.14.0) using RMySQL (0.9-3), but this command fails:
conn <- dbConnect(MySQL(), user="ssh_user", password="ssh_password", host="localhost")
with the error: "RS-DBI driver: (Failed to connect to database: Error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)" regardless of if I use single quotes (suggested elsewhere), change the user and/or password to "root" or "", or substitute "127.0.0.1" for "localhost". If I substitute the server host for host in the R command, I am told I cannot access the server (which is true, it is configured to only be accessed via ssh).
What are the correct user, password and host to use to connect to a database accessed via ssh through Sequel Pro in this manner?
I've never done this, but I assume you could use SSH to tunnel the appropriate port, as discussed here: http://www.howtogeek.com/howto/ubuntu/access-your-mysql-server-remotely-over-ssh/ .
In brief, you would:
Tunnel the appropriate port through SSH, which by default would be
3306 for MySQL.
Use dbConnect() to connect to the MySQL server as
if it was on your local machine.
This bypasses the need for Sequel Pro. The tunnel essentially allows traffic on your local 3306 port to be tunneled through an SSH connection on port 22 between your local machine and the server and then forwarded to port 3306 locally on the server.