Connecting to Zend Debugger on remote server - shared-hosting

I am having great difficulty connecting to the zend debugger on a dreamhost account.
I get the following error message.
Failed to connect to host '192.168.11.7'. Failed to connect to host '192.168.56.1'. Failed to connect to host '127.0.0.1'.
Is this a problem with the debugger not being able to connect to my local machine? Do I need to forward a port on my router perhaps?
I have also added my external ip to the allowed hosts but to no avail.
Any hints much appreciated,
thanks

Is XDebug enable on Dreamhost - not sure it is. You can port forward using an SSH shell, Check here

Related

SQL Server 2014 cannot connect to remote Server

Before I get flagged, I will say that I have tried everything that I could find, but I still cannot connect:
I have opened TCP Port (1433), Server is listening on ['any' < ipv4 > 1433].
I have enable the server browser service
I have enabled remote connections in my SQL server
I have also assigned the TCP port to the TCP protocol for sqlexpress here
I also tried tried to debug the connection using the NETSTAT.exe and it says the TCP 1433 is listening.
I have restarted the service several times when I try to connect from my local PC I get the following error
I can connect remotely to my server using IIS and url.
Question:
What can I do to debug the connection between the devices?
For people that are interested in the question.
I have fixed the issue, (by luck), so what I did I was playing around with the different kind of ports and I added a rule for range ports from
1430 to 1440
and that seemed to fix the problem.
Check it out here
Also for people that use Azure make sure to add a rule in the network security group.
Thanks for the help

JCosole can't connect to glassfish / change address of http listeners

I run a FreeBSD 11.0 server at home, in my private network. I wanted to learn some Java EE, so I installed GlassFish 4.1 at the server. After creating a domain (domain1), I wanted to login in via JConsole. But I get this error message "Connection failed: non-JRMP server at remote endpoint". The ip of the server is 19.168.178.91, so I tried to connect to "192.168.178.91:8686" is that roight?
My other issue is, in the book, which I'm using, they install glassfish at the same machine, which is used use to programm, so they changed the address of the three http listeners, of the IIOP-listener and of the jmx-connector from 0.0.0.0 to 127.0.0.1. Should I change it to the ip of the server or just leave it like it is?
Thank you in advance

Apache Drill-embedded can't connect due to VPN

I'm trying to use Apache Drill in embedded mode (drill-embedded) however when it starts it shows an error:
Error: Failure in connecting to Drill: org.apache.drill.exec.pc.RpcException: CONNECTION : io.netty.channel.ConnectTimeoutException: connection timed out: /192.168.1.11:31010 (state=,code=0)
If I disconnect the corporate VPN it will startup just fine. Connections to the IP of the network adapter are being blocked by the VPN software, which is expected, so I need it to connect to the loopback (127.0.0.1) instead. How can I configure this? I have several other server/services running fine that use the loopback, but for whatever reason Drill insists on using the IP of the adapter.
I've tried various settings in drill-override.conf but can't seem to find the right one that would cause it to connect to the loopback.
Any ideas?
A similar question was asked on the mailing list, and the following answer by Aditya seems to have fixed the problem for the user:
Could you please check your "/etc/hosts" file for a possible
mis-configuration of "localhost" and ensure that all localhost names
are set to default.
I had the same problem and was able to work around it by setting the environment variable DRILL_HOST_NAME=localhost. I think you can also set this in conf/drill-env.sh, there's a line there that exports that environment variable and you can uncomment it and set a value.

Vagrant Virtualbox Webserver, Cannot access from external network

I am having an issue and I am not sure where to go, hopefully you guys can help me out here.
I have a virtual box machine that has a bridged network, therefor the device is on my LAN and there is network connectivity to the device.
I can connect to the web server using my local ip adress 192.168.2.41:25878, however when I try to connect to it with my public IP address x.x.x.x:25878 the web browser is waiting for a connection but it never seems to establish.
Here are my config files for Apache2 / Vagrant
VagrantFile - https://gist.github.com/anonymous/7cca95da3cfc22de5333
Apache2 Site - https://gist.github.com/anonymous/d60efd938d9d7d7de60e
Ports.conf - https://gist.github.com/anonymous/8b0c20a78b36cc5d03b0
The port forwarding is correctly set up on my router. What is really puzzling me, is that I am able to connect to the web server using the local IP address 192.168.2.41:25878, however I cannot access it via the public IP address. The web browser is not rejecting the connection, so I am assuming that I have a config error somewhere, specifically in apache.. The web browser shows a spinning wheel when trying to connect.
I've been trying to solve this issue for almost a week now.. I would appreciate any help that you guys may provide.
SOLVED
So I am not sure why the setup above was not working... I changed from bridged networking to NAT and setup host to guest port forwarding through Vagrant (VirtualBox) and it started working!
I also switched to Nginx instead of using Apache.

Connect to Remotely Hosted WCF Service via netTcpBinding

I can connect to my WCF service locally with no problem but when I host it remotely, I receive this error:
TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.200.58:1991.
Please note that he firewall is already turned off on the host.
I cannot figure out what is wrong. Any help?
Thanks!
Looks like a firewall problem. Check you port 1991 open on the target and client machines
Try using the command (which requires elevated permissions - run as administrator)
netstat -anb
You have likely already searched but I found another question that might guide you to your answer;
WCF No connection could be made because the target machine actively refused