Remote Server not accessible from outside home network

Serviio Pro v1.10.1
2019 iMac 27"
MAC OS 15.5 Sequoia
3.6 ghz 8-core Intel Core i9
Ubiquiti Dream Router 7
StarLink Internet Service

Can't access my remote server from outside the home wifi network.

Serviio is showing no connectivity.

Screenshot 2025-06-04 at 12.53.16.png (399.46 KiB) Viewed 18777 times

I've forwarded the port in my router settings. but still can't get connectivity via Serviio.

Screenshot 2025-06-04 at 13.03.04.png (90.53 KiB) Viewed 18777 times

Any help or ideas?

Thanks

[atc98092]

I'm not familiar with the Starlink router, so don't know if port forwarding is something they offer. And it sounds like you are going through a second router, so port 23424 would need to be forwarded correctly though both. If the Starlink router can be placed in bridge mode, then you only have your main router to configure for port forwarding.

I'm not familiar with the Starlink router, so don't know if port forwarding is something they offer. And it sounds like you are going through a second router, so port 23424 would need to be forwarded correctly though both. If the Starlink router can be placed in bridge mode, then you only have your main router to configure for port forwarding.

So the StarLink router is bypasses when you use a 3rd party router. All settings then defer to the Ubiquiti except for StarLink's default settings for the dish.

[atc98092]

OK, then you’re basically doing the same thing I am with my Comcast modem. I set it in bridge mode and do all the port forwarding in my own personal router. As long as you have the correct ports assigned, and are using the correct URL to reach your home network, it should work. How are you determining your home URL? Are you using a dynamic DNS, or do you have a static IP?

OK, then you’re basically doing the same thing I am with my Comcast modem. I set it in bridge mode and do all the port forwarding in my own personal router. As long as you have the correct ports assigned, and are using the correct URL to reach your home network, it should work. How are you determining your home URL? Are you using a dynamic DNS, or do you have a static IP?

I just go to whatismyip and then type in

http://XXX.XXX.X.XX:23424/mediabrowser/

I've also tried

https://xxx.xxx.x.xx:23424/mediabrowser/

Neither one brings up my media server.

[atc98092]

You can't use HTTPS unless you have SSL set up on your Serviio computer, and then the port number is 23524.

The problem with using a service like that to determine your home IP is that it likely changes constantly (by that I mean as often as every day, sometimes sooner or longer). By the time you've checked it while at home and then tried it from a public access point, it very well might have changed. There's a number of free services that provide dynamic DNS services. Just do a web search for free ddns service and you'll see what's available. Then you no longer have to mess with using IP addresses, but have your own home URL. The first search result came back to https://www.noip.com/. I'm not endorsing them specifically, but you can see what's involved. For the one I use I run a program on my computer that monitors my public IP address and relays it to the company so they can update the address in the public DNS servers. I like that method as I have total control over how it monitors and reports any changes.

Are you trying to forward the port to an outside IP address?

None of the addresses in the listing are in a private IP block...

[atc98092]

Good catch, I didn't notice that internal IP address. Your 216.147.121.x is in the public section of the approved IP addressing range. Home networks must use private IP address ranges. There are three groups of addresses that should be used in home networks. Using something in the public IP address range could cause routing issues.

There are three IPv4 private ranges for Class A, Class B and Class C IP address ranges. These private IP address ranges are given below:

Class A: 10.0.0.0 to 10.255.255.255 (16.777.216 IP addresses)
Class B: 172.16.0.0 to 172.31.255.255 (1.048.576 IP addresses)
Class C: 192.168.0.0 to 192.168.255.255 (65.536 IP addresses)

Most home networks use a Class C address. When you purchase a router, the most common range is 192.168.0.x or 192.168.1.x. Either one will support 254 separate devices on your network, and if you need more than that you can alter the NETMASK setting (normally 255.255.255.0) to enable more addresses. Networking discussions can get quite involved, so I won't spend more time here getting into details. But if your home network is not using IP addresses within one of the private ranges, you need to reconfigure your home network.

While using an internal IP Address range with addresses not in the "private" address space is unusual, it will most likely not yield to problems (obviously you will not be able to reach a web-server using these addresses), the issue you experience ist most likley CGNAT.
Starlink ist not a real internet access. You are located behind a large NAT network shared with many others. Incoming connections are not possible or very limited (read about NAT hole punching, or setup a small virtual Server with a real IPv4 Address, connect with VPN to this, then forward everything to your home from t here, or buy a service which gives you similar).
Or maybe there is an option that you can buy an IPv6 address space from starlink, then, use IPv6.

[atc98092]

Most ISPs are no different than Starlink, in that they don't make your home router directly connected to the public Internet. Very few ISPs are direct Internet providers, so Starlink is no different in that respect. Comcast (my current ISP) is that way, as is CenturyLink (my previous ISP). I had a connection issues years ago with CL and after they researched it they discovered the problem was outside their firewall, meaning the problem was not within their internal network. I doubt the issue lies with the ISP being Starlink.

Now if Starlink is using that IP range on devices inside your network, that tells me there's no firewall between your network and the Starlink internal network, and I wouldn't like that personally. I would add my own personal router to firewall my network from the Starlink network. As I mentioned before, I do that with my Xfinity network, even though their modems do provide private IP addresses inside the modem's firewall.

Are you trying to forward the port to an outside IP address?

None of the addresses in the listing are in a private IP block...

ummmm. I really dont know much about all this.

This used to work when I had another ISP and on my older iMac that died 2 months ago. Now for whatever reason it doesn't work on StarLink or with my new iMac.

You can't use HTTPS unless you have SSL set up on your Serviio computer, and then the port number is 23524.

The problem with using a service like that to determine your home IP is that it likely changes constantly (by that I mean as often as every day, sometimes sooner or longer). By the time you've checked it while at home and then tried it from a public access point, it very well might have changed. There's a number of free services that provide dynamic DNS services. Just do a web search for free ddns service and you'll see what's available. Then you no longer have to mess with using IP addresses, but have your own home URL. The first search result came back to https://www.noip.com/. I'm not endorsing them specifically, but you can see what's involved. For the one I use I run a program on my computer that monitors my public IP address and relays it to the company so they can update the address in the public DNS servers. I like that method as I have total control over how it monitors and reports any changes.

I tried the NoIP thing. can't get anything to recognize. I have no idea what I'm doing honestly. This all worked on my previous ISP and my 2010 iMac. Now with StarLink and my replacement 2019 iMac nothing works. Makes no sense to me.

The port is forwarded in my Ubiquiti router but when I check it via portchecktool.com it says it can't find it.

Screenshot 2025-06-21 at 00.23.58.png (70.18 KiB) Viewed 17410 times

[atc98092]

All I can guess is Starlink is doing something different in their modems, although I don't know what that might be. Assuming your Starlink modem/router is not in bridge mode, the port has to be forwarded in it as well as your internal router. If it is in bridge mode, then in theory it should be invisible to the Internet stream. Just a guess on my part, but I think the port isn't being forwarded in the Starlink equipment.