Continuing the previous entry, I mentioned that besides changing the built-in web server to allow access from more than the localhost, another way to get into your Admin remotely is to use SSH. BlueDragon user Chris Pyle shared these observations:
I have had success tunneling my BD admin requests via SSH. Forward local port 8080 (or another one if you have a local BD install) via SSH to the remote server port 8080.
This will also allow you to leave the remote server configured to only accept BD admin requests from localhost/127.0.0.1 as that is where the incoming SSH tunnel will appear to come from. Of course this is easy to do with a *nix server and any client, it's also possible with a windows server but getting a free ssh server going under windows has taken more work when I did it in the past.
As a side note, once you have the SSH service running on your remote box you can and should also tunnel any insecure protocols you use (MySQL, MS SQL Server, FTP) for remote development.
This works very well for me and the built-in compression of SSH seems to speed things up (I use ISDN , but the speed-up is even more dramatic when connecting via dial-up).
After seeing that, user Jason Wagstaff added the following:
thanks for the information and was painless getting it to work. if others want to give it a try here is some info that might be helpful.
here is a tutorial to get it running with Putty(ssh client) on windows. http://www.jfitz.com/tips/putty_config.html
on *nux set up a ssh session in a terminal window. ssh -L localport:remotemachine:remoteport accountname@remotemachine
you can add the -C switch is for compression if you are on a slow connection. Here is an example:
ssh -C -L 8080:mybox.myisp.com:8080 myaccount@mybox.myisp.com
enter password at prompt then you can use your browser to accesss http://localhost:8080 for the BlueDragonAdmin on your remote machine.
Hope that information may prove helpful to others seeking that solution. As I get time to try it all out myself, I may revisit this entry to add any of my own observations.
If you then want to make the ssh forwarded connection available to other
computers you'll need to add a -g to the ssh command. Also, do not use the
-C option unless you are on a slow connection. On a fast connection it
will actually slow things down (according to the ssh man pages.)
sporter