Page 1 of 1

port forwarding

PostPosted: Sat Apr 02, 2011 6:40 am
by dirkalberteverts
Hello all,i really need some help with this.I seem not to get connected to the ss server outside my house.I tried everything and read all topics about this problem.
I made screenshots to make it easier for everybody to help me.
My ports are open,so here no problem.I use mandriva for OS.

Image
Image
[/img]

PostPosted: Sat Apr 02, 2011 3:26 pm
by GJ51
Most problems are due to improper setup on the router. Setting a fixed internal ip address for the server and proper port forwarding rules on the router are essential for long term stability.

Never use port 80 or 443 - ISP's often use or block them and these are also the default ports on WHS for the remote login page. 8080,8081, work fine. 808X always works. I've seen others use different port numbers that have caused install failures.

READ: http://monroeworld.com/android/subsonic/ This is the Windows tutorial but most of the concepts apply to any setup. Specific setup instructions for other Operating Systems are available in the Tutorials section. http://forum.subsonic.org/forum/viewforum.php?f=6 and on the Subsonic website at http://www.subsonic.org/pages/installation.jsp

In Subsonic Settings/Network - UNCHECK " Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding)." make sure to hit the SAVE button, you may have to scroll down to see it depending on your screen size. UPnP or Plug & Pray works sometimes, but not very often and you're better off learning what's going on anyway. You're dipping your toe into the network mgmt. thing anyway, might as well learn what's going on as home networks don't get simpler as time goes on. As your network gets more complex, you're going to have to learn this stuff! No time like the present.

Manually assign a fixed intenal IP and static route to your server at the upper end of the address range of the router, out of the way of DHCP, e.g. 192.168.1.254

Set up your router manually. uPNP might work, but most often it doesn't. Learing how to do it will be a skill you'll love having as your network grows.

Check the Subsonic Control Panel to make sure it's using the right port you're going to use. I typically use 8080 - 440, 8081 - 441, etc.

Set up port forwarding in your router to direct traffic on the selected port to your server. Consult your router documentation to do this, they are all a bit different.

Learn your external IP address assigned by your ISP. Go to http://www.canyouseeme.org/ enter your SS port number and click the Check box to be sure the Subsonic port is open.

Test your setup by entering your external IP:port# to see if it connects. e.g. http://98.117.185.5:8084/ If it works, you're good to go.

PostPosted: Sun Apr 03, 2011 5:15 am
by dirkalberteverts
when i type in my name.subsonic.org:8080 i see that my name changes to my internal ip adress where the subsonicserver runs on.Shouldn that be my external ip adress?

PostPosted: Sun Apr 03, 2011 3:06 pm
by GJ51
Doesn't really matter as long as you can connect. If your inside your network, some routers automatically translate to the internal ip.

PostPosted: Sun Apr 03, 2011 5:05 pm
by bushman4
Just a quick point that I noticed...

When connecting to your redirected subsonic.org address (ie the name.subsonic.org address) you DO NOT NEED THE PORT NUMBER AT THE END OF THE URL!

If your registered Subsonic.org name is pickle.subsonic.org and your server is running on port 1234, the proper address is "http://pickle.subsonic.org" NOT "http://pickle.subsonic.org:1234."

The Subsonic.org servers then see this as an HTTP request for your subsonic.org domain name and redirect your browser to your current external IP address, and the port, and context path that Subsonic is running under.

Just want to be clear... it is VERY possible that Sindre's servers are only configured to respond to requests on the standard Web Ports and any attempt to contact "http://pickle.subsonic.org:1234" would fail.

HTH,

PostPosted: Sun Apr 03, 2011 5:28 pm
by GJ51
Thanks Glenn,

That's correct. The Subsonic.org server translates the Servername.subsonic.org request into the ip:port# of the server it is requesting. The port number should NOT be appended to the Subsonic.org address. When you save the network settings, the local SS instance transmits the IP and port number to the Subsonic.org server. When you access your server with the http://servername.subsonic.org, it uses that information to transmit the request back to your local server using the correct ip and port number.

Also remember that you can't make a direct https connection using the subsonic.org address. The Subsonic.org server only uses the http address, but Subsonic will respond to the request over ssl if you have it enabled. You can make a direct connection to the ssl port if you use your external ip and port number, or if you use another DNS server that will accept https requests. This works with WHS. e.g. https://maplegrove.homeserver.com:442