Selfhosted

By default a router would reject all incoming connections. Your alternatives are:

• Configure the ISP router to forward a port.
• Configure the ISP router to set your own router or PC as DMZ, which means forwarding all connections.
• Configure the ISP router to work in bridge mode rather than router mode, meaning it will act as if it wasn't there (but will still login to the ISP connection) and let your own router or PC handle things.
• If you cannot configure the ISP router in any way, only solution remains to replace it with your own router. Whether this will work depends on how it connects to the ISP (both the physical connection type and the login).

It doesn't make sense for the ISP to allocate a static public IP without letting you make any configuration to use it, so perhaps talk to them to figure out your options.

I know there are higher orders of nerds than me who will have some supremely elegant solution, but you identified as a beginner, so here are my two cents:

Going the static IP route and directly exposing your server to the outside world is a potentially major security hazard unless you know what you’re doing. Especially when getting started, it may be a good idea to consider using a router with built in VPN capabilities for accessing your network remotely when you need SSH access, or other maintenance tools.

Media serving software like Plex and Jellyfin will be able to serve content without the VPN just fine, and it will keep your more vulnerable controls behind your network security as you are learning and getting things set up. As you get more experienced and ambitious, then you can consider exposing your setup to the outside world, but be sure to put in security safe guards so you don’t get brute forced by bots like a back alley cyborg hooker.

VPN routers are cheap, security breaches are not.

I consider myself at a somewhat moderate level of proficiency at this point, but I still use the VPN system for my server because I never have to worry about it. It takes two seconds to check the OpenVPN toggle if I’m away from home and need to restart something, but 99% of the time, the content servers just work and my major maintenance can wait until I’m on the same network.

My ISP had the same problem, ultimately I was able to convince them to let me use my own router. In doing that, I was able to at first use a standard off the shelf router and later a pfsense firewall to handle NAT that exposed my servers to the outside world.

Before I was able to do that, I was pretty convinced I wasn't going to be able to self host. There are other options, such as special VPNs for self-hosting, but that's not really the point, is it?

Sorry just re-read your post. So the router they supplied does not have this setting? What make and model is it?

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

6 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.

[Thread #233 for this sub, first seen 23rd Oct 2023, 13:15] [FAQ] [Full list] [Contact] [Source code]

You need to forward ports to your minipc, so it sounds like you need a different router.

Do you have a modem? You should be able to configure port forwarding in that