Workbench fails to connect when using SSH tunnel to hosted DB - database-connection

experiencing connecting workbench through SSH tunnel to connect to a hosted mysql DB. I'm using port 3309 as I have a local wamp server running mysql on 33066
My first time trying to connect via SSH so any help would be appreciated...
If I try through workbench using standard TCP/IP over SSH I get the below error message
Failed to Connect to MySQL at dbxxx.db.1and1.com:3306 through SSH tunnel at user#homexxxxxxx.1and1-data.host:22 with user dboxxxxxx
[Content]
Lost connection to MySQL server at 'reading initial communication packet', system error: 0
If I use an SSH connection via putty with port forwarding I get the following error
Putty port forward config: source = 3309 destination = dbxxx.db.1and1.com:3306
Error I get back when connecting through workbench is:
Failed to Connect to MySQL at 127.0.0.1:3309 with user dbuser
[Content]
Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Related

Can not connect docker mysql that's forwarding to 3306

When I'm trying to connect to a docker MySQL that's running and forwarding to my local TCP:3306 I get the following answer
mysql -u root -pPASSWORD
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
but when I do mysql -u root -pPASSWORD -h127.0.0.1 it connects wonderfully.
Any clue?
[UPDATE]
Considering the comments and this post I create ~/.my.cnf
with this content
[Mysql]
user=root
password=yourpass
host=127.0.0.1
port=3306
Giving these changes I could connect the localhost with the 127.0.0.1 address.
If you don't specify a host with -h (or a host directive in your .my.cnf), then MySQL defaults to connect to localhost. Connections to localhost use the UNIX domain socket interface, not TCP/IP. So it's not connecting to a TCP/IP port, and therefore does not forward to your docker container.
This distinction between localhost and 127.0.0.1 is a historical oddity of MySQL. Normally localhost and 127.0.0.1 are assumed to be equivalent. But MySQL treats the hostname "localhost" as special, using it to invoke the UNIX domain socket interface. This is a bit faster than using TCP/IP, but of course only works if the connection is on the local computer.

pgadmin4 : Unable to connect to local server

I've installed a dpage/pgadmin4(port:5050) on my vmware centos8 from Docker.
And my database postgis(version:11.2-1,port:5432) also run on docker.
Now I can connect my postgis by using navicat but pdadmin4 not works.
I've got this:
Unable to connect to server:
could not connect to server: Permission denied Is the server running on host "172.17.0.1" and accepting TCP/IP connections on port 5432?
or:
Unable to connect to server:
could not connect to server: Permission denied Is the server running on host "xxxx.xxxx.xxx.xxxx"(centos ip) and accepting TCP/IP connections on port 5432?
I tried ways from stackoverflow but not work.

ios push notification connection refused

I have a AWS server which runs centos 7 operating system. The server has CSF installed and is a production server. My site is running fine on it (PHP). Now when I am trying to send a notification to ios I am getting connection refused error. Then when I did telnet I got the following response:
telnet gateway.sandbox.push.apple.com 2195Trying 17.188.166.22...
telnet: connect to address 17.188.166.22: Connection refused
Trying 17.188.166.23...
telnet: connect to address 17.188.166.23: Connection refused ...
In outgoing ports aws server security allows all traffic.Why is this happening ? Do I need to open inbound ports for 2195? I read in this site that its not required.

Connection failed: Host 'linux547.grserver.gr' is not allowed to connect to this MariaDB server

code here i am trying to connect my site to a database using this code:
but I get this error:
Connection failed: Host 'linux547.grserver.gr' is not allowed to connect to this MariaDB server
Does anyone have any suggestions? Thanks

Neo4J Rest interface listener not starting

I have exported a graph of around 1300 nodes and 3500 edges from Gephi 0.8.2 beta into Neo4J 1.9RC1. However, after exporting I cannot connect to the server using REST API anymore because I cannot find any listener either on port 1337 or on port 7474. Hence, neither the shell interface nor the web interface is working.
Everytime I try to connect using the Shell it says "Connection Refused". When run in verbose mode it says "
D:\neo4j-enterprise-1.9.RC1\bin>Neo4jShell.bat -v
ERROR (-v for expanded information):
Connection refused
java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
"
Could someone please explain what is going on?
I have checked using netstat that the ports 1337 and 7474 are free and noone else is listening on them.
The same behavior is noticed on Neo4J version 1.8.2 enterprise stable as well.
You are trying to start the shell, not the server. You want to run the bin\neo4j start command, then it should be listening on those ports.

Resources