Title is a bit vague because I don’t know the correct terms to phrase it properly.
I have a Raspberry Pi that I use to run jellyfin, transmission, blocky, soju. Recently I added libreddit to it seeing how the rate limits are affecting public instances.
The problem is that currently if I need to go my libreddit instance, I have to go to 192.168.0.x:xxxx which is extremely unfun to type.
Is there a way I can access it more elegantly? One solution I found was to configure blocky with a custom DNS that points to the RPi where I can configure an nginx reverse proxy so that lr.rpi.local for example serves libreddit.
Any other ideas for this?
You can edit the hosts file on your local device, but I would recommend you take a look at using the rpi for a pihole/ DNS server. Then you can edit the hosts file on the PI to make it so that any device on your network redirects with the custom name.
Hell if you want to have fun install nginx proxy manager then you can set up routing so that anything is easily accessible from inside you net ie: rpi/jellyfin or rpi/soju.
If youre interested in doing anything like that and youre stuck ill help with any questions. I setup docker containers with proxies all the time
Thanks a lot. I got it to work:
assuming you are using a desktop os, e.g windows/linux, put an entry in /etc/hosts, e.g. 192.168.0.x yourname
then you can use yourname:xxxx
Thanks
You can configure many routers to act as DNS servers, then advertise themselves to client devices as a DNS server (with a secondary like 8.8.8.8 or whatever). Then you can just use the hostname of the device you want to access and as long as your client device is using your router for DNS it will resolve correctly.
How specifically to set this up depends on your networking equipment
Not sure if this helps, as I’m not 100% certain how I set this up (it was too long ago), but by giving my rpi a hostname I can simply use ‘pizero.local’ from my desktop machine. I don’t run a DNS server per se but maybe look into that kind of dhcp / dns option?