Couple of possibilities.Hello,
@Glorious1 is there a way to confirm the curl command is running? maybe that is it?
If this is accurate, your forwarding is backwards. You need to forward external port 1277 to internal freenas IP port 22.Router
- Forwarding the IP address of the freeNAS from the local port of 22 to external port 1277
Should look something like this (replacing the IP address with yours:If this is accurate, your forwarding is backwards. You need to forward external port 1277 to internal freenas IP port 22.
So your tunnel (which I presume is for the webGUI access) is forwarding traffic that lands on your freenas back out to the external port of your router, which then forwards to your internal ssh port. Sounds like you need to change the destination of the putty tunnel to be the local freenas ip and webGUI port.
- Tunnel set up in putty (forwarding local port 44444 to domain.duckdns.org:55555)
So your tunnel (which I presume is for the webGUI access) is forwarding traffic that lands on your freenas back out to the external port of your router, which then forwards to your internal ssh port. Sounds like you need to change the destination of the putty tunnel to be the local freenas ip and webGUI port.
Yes, my goal is to get to the webgui.Your laptop config doesn't make sense. Port 44444 (which I assume you are using for the web gui) will eventually get forwarded to the SSH port of the freenas which won't give you webgui.
Yes.Your laptop is the one you have with you outside your home network right?
Okay. So I think I understand a little more now. Or, at the very least, I have a better idea of what I don't understand.So once you've connected from it via ssh to freenas, your tunnel should be configured to go directly to the internal ip address and port of the freenas webgui. Then you access the gui on your laptop with http://127.0.0.1:44444.
- Configure port forwarding on home router (external port 55555 is forwarded to FreeNAS_LocalIP:22)
- SSH to domain.duckdns.org:55555 (the Tunnel should be set up in putty prior to connecting (forwarding local port 44444 to destination 127.0.0.1:80))
- open web browser on remote end of tunnel and go to http://127.0.0.1:44444
yes. you need allowtcpforwarding enabled.Is this kind of tunneling forbidden by missing that setting?
Ah, alright. There's my problem then. Is there a way other than editing the ssh_config file to enable that setting from the terminal? Otherwise, it would seem that I would have to stop the ssh service in order to update the config file. And I can't edit the config file after it's stopped if I can't access it via ssh.yes. you need allowtcpforwarding enabled.