Securit Side Note: Never never never setup a server where root can SSH in! Serious security flaw. You will then be able to type "localhost:1234" (for example) into the browser and it will connect to the service running on the remote server on port 1234. If you just have the one server, you tunnel into it with the Dynamic connection, set your proxy.
It sounds like you just have the one server, but I wanted to be sure this was clear. If a browser running on server A could not connect to Server B (if the process on Server B only listens on 127.0.0.1) then you still couldn't connect. So if you tunnel into Server A, and want to connect to server B, you type into your browser whatever address you would type into a Browser running on Server A. Then point your browser's proxy to localhost:1234. But you have to type a hostname/ip and port into the browser as if the browser were running on the machine the SSH Server is on. This will open a port on your local computer to which you can point the Proxy setting of your Browser and allow you to use the tunnel as a proxy server. What is possible however is to establis a Dynamic connection with the SSH Server.
Using a name is now not necessary, since the browser is for remote server sites only. I can set this up as a proxy in my browser and the browser will treat any request to localhost:anyport as if it was made on the remote server. Thanks to the provided answers and comments the port forwarding works now using Is this possible with ssh? I've read the man pages and googled around for two days now, but it does not seem to work. to be able to define the remote port in my browser I would like to connect to my.tunnel.name:port, in order to be able to call the different sites.assign a name to the tunnel and use e.g.All of them are bound to 127.0.0.1 on the remote machine. Now I want to access several admin sites on the remote server (a MongoDB status page, a RabbitMQ page etc, all on different ports). To establish a tunnel from my MacBook to my dedicated server at my hosting provider.
0 kommentar(er)
