I'm trying to use FileZilla to connect to my own Apache server, but I can't figure out what the username and password should be for the server. Is there any way to find these values, or some sort of defaults I should try? Sorry for the stupid question, this is basically my first time working with any sort of server.
If your issue is trying to connect to the server that contains your Apache installation, then all you have to do is connect to it using the IP address of the server on your network (example: 192.168.1.10), enter a valid username and corresponding password of a user on that machine, and you should be able to connect.
Refer to this document for more details:
http://wiki.filezilla-project.org/FileZilla_Client_Tutorial_(en)#Connecting_to_a_server
Related
I am trying to connect Laravel Forge database from Sequel pro. I am getting the "The SSH Tunnel could not authenticate with the remote host. Please check your password and ensure you still have access" error.
Initially I was asked to enter the paraphrase. I got the same result even with the right paraphrase.
Thanks in advance.
I am new to Ldap. I'm using windows10 OS and I'm trying to connect to a remote ldap server in order to perform an ldapsearch operation. I have browsed about this but till now I have only come across very very complicated steps and I'm not sure if its the right way as well.
So can someone share the steps in order to achieve this?
I would rather recommend Apache Directory Studio that works pretty similar to any other kind of LDAP browse, such as the above mentioned Softerra.
However, on Wikipedia you can find an exhausting List of LDAP software.
You could use the an LDAP browser, such as the Softerra LDAP Browser.
https://www.ldapadministrator.com/softerra-ldap-browser.htm
Then you enter the URL and authentication data of the server where you want to connect and you're ready to browse the data.
You will probably pass a "bind DN" (which identifies the user) and the password of him.
The entire scenario of my situation seems 10/10 sketchy, I'll admit. So I won't bother convincing you this isn't a malicious attempt to access a server that isn't mine - I'll simply say once, that this is a legitimate need for assistance.
That said, basically my problem goes back to me being a little too restrictive when it came to SSH access to my CentOS 6 server. Basically I restricted access to my custom SSH port from only two IP addresses - one being my home address, and one being my work address - via iptables. The problem is, I no longer work where I do, and my home IP address changed ever since I upgraded my internet.
Obviously this means I no longer am able to connect to my server via SSH since I don't own that IP address anymore.
My question is, is there anything I can do to access this server? I have no console access, but I do at least know the IP address I used to use to log into the server (maybe possible to spoof an IP address, but I have no clue). The only other thing I can think of is I have DirectAdmin installed on the server and can still login with the admin account. Other than that, I've got nothing.
If anyone has any idea on what I can do, it would be greatly appreciated.
You can change the SSH port number from Directadmin file editor (if you have root password),
Then restart the sshd service from service manager
And you can connect to SSH via new port number!
I'm trying to connect to my Google Cloud SQL instance from my desktop but am getting the following error:
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0
According to the docs this means that the client's IP isn't authorised to access the instance. I have done the standard "what's my ip" google search and added the IP to the "Authorised Networks" list of the instance (as well as a bunch of variations and /x ranges - none have worked, yes I restarted the instance). I have set a root password and even tried connecting with the necessary SSL certs - yields the same error.
I can connect to other (non-google) sql databases, I can ping the database, and I'm not behind any significant firewalls.
How i'm typically trying to connect (also tried SSL):
mysql --host=the.instance.ip.add --user=root --password
Nothing I try seems to work.
I feel like I must be missing something obvious - any suggestions welcome (this is a nightmare).
Could you check again if you have authorized the correct IP address.
If using your desktop from home, you may be having a private IP address for the desktop. What you really need to authorize is the public IP address.
The "what's my ip" search on Google doesn't currently work properly when the ISP is proxying the web traffic transparently. Better information on the IP seems to be provided by Proxy Test from http://www.lagado.com/proxy-test.
Make sure that the IP you are using is the public IP, keep in mind that this can change from time to time depending on your Internet provider. The easiest way to authorize any network is to add 0.0.0.0/0 to the witelist
I check my ip addres in this page https://www.whatismyip.com/es/
I purchased shared hosting from Vexxhost.I wanted to host my Rails application with them.I was given cpanel details.I generated SSH keys using the cPanel and converted it to .ppk format.Next, i downloaded the key.But when i try SSH login using Putty, i get the message Server Refused Our Key.Then i'm prompted for the password.When i enter password, message is displayed: Shell access is not available for your account.Contact support.I did contact support, but no reply.Am I doing any mistake in the procedure?
I haven't used cpanel to generate ssh keys, usually I do it at the ubuntu console. Is it possible that the ppk conversion has encoding issues? or it not done right?
Do you have access to a linux box? It would be simpler to test it there.
I have configured a server myself with ssh access, and if user does not have ssh access they are presented with user/pass. So it appears that your ssh credentials are denied, but your password is recognized as accurate. Authentication is happening.
About the issue of shell support. It could be that they enable shell support only if you connect with valid ssh credentials - in which case, you need to contact support.
Or, your account does not have ssh access, and you still need to contact support.
hope it helps