I need to first get a dynamic DNS address? Or do I just need my domain?
You can do both. You can refer to a DYN with a CNAME record on namecheap or you can just refer to your current IP and update it if it changes. In my experience your IP wont change unless you have a major power outage or the modem is down for an extended period of time.
1 Like
Found the steps:
https://www.namecheap.com/support/knowledgebase/article.aspx/36/11/how-do-i-start-using-dynamic-dns
I should probably set this up first before proceeding to other projects that are domain related
I am right @MichaelLindman ?
FWIW I just have an A record pointing to my current IP. You can run dyndns, and in all reality you should, but its not necessary to get things working. My IP only ever changes if the modem goes down for an extended period of time, which hasnt happened for over a year now (power outage, internet outage, etc). It takes me 2 seconds to look it up again and fix it. Me personally, I dont want to run a client just to point it at my IP.
2 Likes
You should setup the domain so it ultimately points to your home network either using DDNS or just manually pointing the domain to your IP like @Adubs suggests, I personally don't use DDNS and add an A record to my IP address as it changes once a year at most.
1 Like
A record in my domain settings right. And public IP is the one that sometimes changes?
Thx
Yes, add an A record that points to your public IP address in your domain settings.
1 Like
I'm done that step. Entered my public IP into the A Record spot in the control panel.
Edit: I should still setup a proxy first using Apache on Ubuntu. (Reverse or forward proxy?)
Yes, add a reverse proxy in Apache and set the ServerName to whatever your CNAME record is and forward the assigned port and in theory the domain should point to the service under the proxy.
1 Like
Where do I find the assigned port?
It's usually port 80 for http?
You have to forward the port on your router for the port you set in the VirtualHost on Apache, it is usually 80 for HTTP and 443 for HTTPS.
1 Like
Should I set port 443 in Apache ?. I also have SSL cert. That came with domain.
It would be ServeName domain:443 in Apache?
For HTTPS to work you have to do extra configuration for Apache and also Plex/whatever service you are using. I'd say get it working with HTTP first and add SSL later as it would only complicate things more for you at this stage.
1 Like
porn site of course
1 Like
I would also like to note that I've never actually got Plex working correctly with HTTPS as it does some weird stuff that I haven't manged to figure out yet but I'll take another look at it and see if I have better luck this time.
Edit: So... I just got Plex working with HTTPS but have no idea why its working now when it didn't before as the configuration is pretty much the same.
1 Like
There's always emby and mpd I guess.