sk1nT7@alien.topBtoSelf-Hosted Main@selfhosted.forum•Can't access NPM when assigning a macvlan IP to itEnglish
1·
1 year ago- 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?
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?