Illuminated_Humanoid

joined 2 years ago
 

Hi,

Has anyone managed to install NPM on their NAS with a macvlan IP that works? I have been trying to set this up for a few days now and I can't seem to figure out what I am doing wrong.

I know that Synology NAS has port 443,80 always in use so my understanding is that since I am using a macvlan IP, it doesn't conflict with the NAS. Because of that, I think the issue and where I am screwing up is setting up the container so that a bridge can connect my macvlan and my host network.

Again, has anyone managed to get this to work?

[–] Illuminated_Humanoid@alien.top 1 points 2 years ago (1 children)

What's the main kicker here? Reading this over, it sounds like you're saying to create two macvlans, but I only see an execution of one? I am confused brother

What happens if you use bridge networt and manually map the port 80 and 443 port to a random one on your synology like 8888 and 9999? Can you then access these ports?

Not exactly sure how to do that. Yes, you're right, I created a whole new container and for some reason it doesn't load. Without macvlan IP it loads fine, with the macvlan it just refuses to load.

I appreciate the heck out of you for trying, but my god this confuses the crap out of me even more lol. I've read it over several times, and I am just not connecting the dots ☹️

[–] Illuminated_Humanoid@alien.top 1 points 2 years ago (2 children)

I'm not sure, but there certainly must be a conflict with the built-in DSM Nginx.

There are zero error logs.

 

Hi

Stock nginx built into Synology DSM won't cut it, so I decided to install Nginx Proxy Manager. Before doing so, I created a macvlan and assigned the NPM container to use the assigned IP. Once install is finished, and I try to launch NPM, it fails to load. I tried the same install without macvlan, and it works and loads just fine. I have installed many other containers on macvlan, so I know what I am doing and have the knowledge and experience, but I have never run into this before where there seems to be a conflict I am not aware of.

Help? Anyone?

 

Hi,

I am wondering if anyone knows of a self-hostable container that specifically only manages and issues SSL certs via lets encrypt? I know NPM does this, but I am hoping to find a container that doesn't have all the extra stuff I don't need.

 

Hi friends,

I have been trying to sort this out for many days now, and I am stuck on what is most likely a small issue I am overlooking. I have read many guides and previous posts on this, but I still haven't figured it out. I will explain what I have done and hopefully someone can spot the error. Scroll all the way down to read all details.

  • I have my FQDN on Cloudflare. I set its DNS entries, as you can see below, to point to my PUBLIC IP where my stuff is hosted.

https://preview.redd.it/8484seuxw1vb1.png?width=1308&format=png&auto=webp&s=ae30061796e3cc296116e344283d1fc918757a67

  • Next, I went into Nginx Proxy Manager and clicked add certificate. I got the API token from Cloudflare site and filled it in as you can see below. The certificates are successfully granted.

https://preview.redd.it/czhf5g3ux1vb1.png?width=495&format=png&auto=webp&s=47f48fea68eb315565617da4c9108cc86befde53

  • Next, I added a reverse proxy entry in Nginx. I want this entry to point to my NAS homepage, so I set it, as you can see below. I also applied and forced SSL that was issued.

https://preview.redd.it/46pcp0h8y1vb1.png?width=496&format=png&auto=webp&s=5fbba6cc0cc8d1e424ec49e733fea51952e8eaf9

https://preview.redd.it/um8wtfbiy1vb1.png?width=498&format=png&auto=webp&s=16d77305e91dbf98c22f87b99df2f46ffe39fe82

Now, I would expect after this step that I could just go into my browser and type the FQDN, and it will route me to the LAN IP I set the proxy entry to, but it's not working. Keeps taking me to a "this page cannot be found" .

What am I missing here?
Are any of the steps above unncessary?
The guide I originally followed is this one right here

Important notes:
- I have port 443 forwarded in my router to my NAS IP.
- I have adguard home with Unbound setup in my network on a separate Raspberry Pi.
- I use tailscale on all my devices.
- My home router and my NAS are both firewalled.
- My self-hosted containers are all in docker on my Synology NAS (minus adguard)

 

Hi,

I am planning to switch from Plex to Jellyfin all in the name of supporting FOSS. I am wondering if anyone knows whether Jellyfin has a built-in proxy just like Plex? I am not talking about the Plex relay that limits your streaming speed when port forwarding is not setup correctly. I am talking about a normally functioning Plex server that still by default hides the IP of the server. Does Jellyfin do this too, or will it expose my IP externally to those who connect to my server?

Edit: If you are unsure what I am talking about, open a desktop browser and connect through the browser to a Plex server. If you have any extensions in your browser that show the IP of the website you're connected to, like I do (flagfox), then you'll see what I mean about Plex hiding the server IP. I honestly would've never known Plex did this had it not been for my browser extension.

 

Hi,

I just recently setup tailscale for accessing all my self-hosted fun stuff while I am away from home as securely and conveniently as possible. It dawned on me today that it's entirely possible that tailscale can have an outage one day, and at that time I would need a backup. So I searched around and the best open source alternative with the same concept I could find was zerotier. So, I have a few questions for you.

#1. Can I use zerotier alongside Tailscale for backup connections in the scenario I described? If so, should I?

#2. What is your backup method you currently have set up?