Can't reach WebUI or jails from the web

[cen]

My Web UI and all plugins have static local addresses and are accessible on different ports.
WebUI: https://192.168.1.70:10000
Owncloud https://192.168.1.72:10002
etc

The reason I changed the ports from 80 is because my retarded router cannot port forward to same internal ports even tho IP is different. So each service has different port. Now I want to access them from the internet

Port forward rules:
Freenas WEBUI: TCP 10000 (external) 192.168.1.70 10000(internal)
owncloud: TCP 10002 (external) 192.168.1.72 10002(internal)
etc

But when I try to access https://mypublicip:10000 (or any other port) I get "Unable to connect" on all browsers. If I access my public IP with no custom port I get thrown on my router UI page.

http://canyouseeme.org/ shows ports 10000, 10002 etc open.

Any ideas what could be wrong with my setup?

 

[cyberjock]

ROFLMFAO. You actually trying to make your stuff open to the world via port forwarding!

Please.. post your public IP so we can see how fast you get pwned.

Anyone have that hilarious thread from the other day where someone created the russian mafia account and told his "comrade" how safe port forwarding was?

 

[DJ9]

Here: http://forums.freenas.org/index.php...-open-cifs-ports-on-router.22416/#post-133513

 

[cyberjock]

DJ9, you are my hero today! LOL!

 

[cen]

That is why firewalls exist. Having Freenas and plugins on LAN is completely useless if you are not at home so I need to make it accessible from the web.

 

[cyberjock]

That is why firewalls exist. Having Freenas and plugins on LAN is completely useless if you are not at home so I need to make it accessible from the web.

Yep... and that is why VPN was invented!

 

[korna]

Without the sarcasm :p They are right. You should not expose the web ui of your router or nas on the internet. Someone could probably brute force the login.

What you could do, as suggested, is set up a VPN or forward the web UI via a secure SSH tunnel (with certificate not normal user login)

Regarding your port forwarding problem which in all likeliness is going to repeat itself with SSH, try a RAW connection with Putty and see what it throws at you

 

[cen]

I'll try it out and see what happens.

 

[Whattteva]

I think I know what's wrong with your port forwarding. Are you trying to access the sites using your public IP from WITHIN a computer inside your internal network?
If so, that will ONLY work if your router supports NAT loopback feature (which I found most consumer-grade routers do not like to support).
Try it from a real computer outside of your internal network (or you could use a proxy server) and it should work.

That being said, I still would like to heavily re-emphasize what others have already done prior to my post. I would really highly discourage what you are trying to do in favor of more secure channels like VPN or SSH.