this post was submitted on 19 Oct 2023
2 points (100.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
2
Can't access NPM when assigning a macvlan IP to it (alien.top)
submitted 1 year ago by Illuminated_Humanoid@alien.top to c/main@selfhosted.forum
23 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] sk1nT7@alien.top 1 points 1 year ago (4 children)
  • conflicting ports? Do you already use the mapped ports?
  • Macvlan prevents communication from the docker host to the macvlan IP and vice versa. Depending on how and from where you access the macvlan IP, it might not work natively.
  • Is NPM starting correctly? No errors in the container logs?
[–] Illuminated_Humanoid@alien.top 1 points 1 year 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.

[–] sk1nT7@alien.top 1 points 1 year ago (1 children)

Usually, when using macvlan, the ports should not conflict as the container obtains a new, separate IP address. 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?

[–] Illuminated_Humanoid@alien.top 1 points 1 year ago

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.

load more comments (1 replies)