Setting up remote access

[theshyla]

Hello, sorry if this is a dumb question but I've been having a lot of trouble setting up my server so it can be viewed anywhere. Preferably I'd like to know a way I can bind a server to a domain I bought. I tried following some tutorials but I'm not tech savvy enough to understand them fully. Is there a simple explanation on how I can set this up?

[Venson]

Hey @theshyla

This is a very broad topic. As you said there are a lot of guides out there, even a few very good ones in this forum.
Maybe its for the best you pick one and ask specific questions on issues you do not understand or need help with.

[theshyla]

Hey @theshyla

This is a very broad topic. As you said there are a lot of guides out there, even a few very good ones in this forum.
Maybe its for the best you pick one and ask specific questions on issues you do not understand or need help with.

Ok, earlier I was following a tutorial and I nearly got it, but at the end I had to type "nssm start Caddy" into Windows Powershell and it always returned this error

[Venson]

Ok to use nssm which is an non-windows program you first have to download and setup:

https://nssm.cc/download

I can recommend this guide from our forum:
https://forum.jellyfin.org/t-access-your...with-caddy

[theshyla]

Ok to use nssm which is an non-windows program you first have to download and setup:

https://nssm.cc/download

I can recommend this guide from our forum:
https://forum.jellyfin.org/t-access-your...with-caddy

I did follow the instructions on installing nssm but it doesn't seem to work still. Are there any good video tutorials on getting this to work? I can't really follow text tutorials well.

[SmaMan]

There's plenty of video tutorials out there. Since you're using Caddy I'm assuming this is the path you're trying to follow.

However, there's one big issue with this and many other tutorials out there that probably will not work. If you're with a major ISP in a major country, then you're probably on Carrier-Grade NAT. ISPs now put multiple homes under the same outbound IP address, which makes you a lot more secure, but it'll make what we're doing a lot more difficult.

So if that tutorial doesn't work and the (sometimes outdated) Jellyfin documentation doesn't get you very far, I'd recommend giving this a try. With the exception of the last few steps which just set up your server to kick back on in the event of a connection issue, this tutorial worked for me. 

Basically, you'll be renting a cheap VPS and tunneling your home server through the NAT and into it. You can then associate that VPS with the domain you bought and you should be good to go.

[Anderson]

There's plenty of video tutorials out there. Since you're using Caddy I'm assuming this is the path you're trying to follow.

However, there's one big issue with this and many other tutorials out there that probably will not work. If you're with a major ISP in a major country, then you're probably on Carrier-Grade NAT. ISPs now put multiple homes under the same outbound IP address, which makes you a lot more secure, but it'll make what we're doing a lot more difficult.

So if that tutorial doesn't work and the (sometimes outdated) Jellyfin documentation doesn't get you very far, I'd recommend giving this a try. With the exception of the last few steps which just set up your server to kick back on in the event of a connection issue, this tutorial worked for me. 

Basically, you'll be renting a cheap VPS and tunneling your home server through the NAT and into it. You can then associate that VPS with the domain you bought and you should be good to go.

This worked for me thanks a lot.

[dicksonshymala]

Setting up a server for external access can be challenging, but here's a simplified guide:

Domain Binding:

Ensure your server has a static IP address.
Go to your domain registrar's website where you bought the domain.
Find DNS settings or Domain Management.
Create an A (Address) record pointing to your server's IP.
Router Configuration:

Access your router settings (usually via a web browser).
Set up port forwarding for the specific port your server uses (commonly 80 for HTTP).
Forward external requests on that port to your server's internal IP like hydrogen v6 executor.
Firewall Settings:

Adjust your server's firewall to allow traffic on the chosen port.
Dynamic DNS (Optional):

If your home IP is dynamic, consider using Dynamic DNS services for a hostname that auto-updates with your changing IP.
Remember, security is crucial. Keep your server and router firmware updated, use strong passwords, and consider HTTPS. If the technical details are still challenging, seeking help from someone tech-savvy or a professional might be beneficial.