Im trying to set my main repository up on my remote machine so that my other machine can connect and work with it, however I dont have a static IP on the remote machine, so Im using a service called no-ip. Its a dynamic DNS service that gives me an easy pipe to the box.
However when trying to bind my domain name to the proxy server it refuses to stick. I can only use a integer based IP address.
Is there anyway that I could get these 2 machines working together?
Hmm… I think you may have hit an edge case we were not expecting. I can make a developer issue to address this though. Would you be able to give me logs so it will help them find the area of the code they would need to fix? I’m assuming this error is being thrown by the Slave.
there actually isn’t an error thrown, it just wont connect if I use my dynamic DNS as the proxy server from the remote machine.
And if I try and put myhostname.noip.me as the ipaddress in the Web Service and Proxy tab, the string just vanishes once I open the config window again.
I could potentially be trying to set this up incorrectly too.
I have 2 machines, in different locations on different networks. Im attempting to setup machine 1 as the repo manager and a slave. I am setting the repository up on a shared folder that both machines btsync. The machines also have identical file systems / paths.
Setup machine 1 with mongo, deadline, define it as the server, go to Repo settings, put the current IP of my WAN in. Forward port 8080 to the machine. Test from my laptop on a VPN that the machine is pingable.
Setup machine 2 install slave, try and connect to repository using proxy server pointing at the current IP of machine 1. can’t connect.
This is the error I get if I try and connect to the repository using ‘repository’ mode. As expected it can’t connect because they’re not on the same network.
I’ll totally concede that there is a margin of user error at work here. If you could point me in the right direction that would be great.
Ah! Are you putting the host name here?:
That is the interface to listen on, so you can either use the IP address of the machine running the Proxy, or you can leave it at “0.0.0.0” to listen on every network card on the machine which runs it. It’s sort of like the IP address version of “.” for files on Windows / DOS.
Can you try with those four zeros, then send along the error when using the Proxy mode to connect?