TechMed Posted February 9, 2020 Share Posted February 9, 2020 Hi All, I have been trying to find an answer as to why I cannot access a specific Docker from different vlans/subnets. I have multiple vlans and subnets that are working perfectly, but I cannot get any of them past Letsencrypt to the Docker it is protecting. Basically, any vlan/subnet that is not on the Letsencrypt/Nextcloud subnet cannot connect to Nextcloud; anything on the NC subnet connects as expected, including externally. I really have researched this and cannot find a solution. Obviously I am still new to complex networking, but I do have a decent foundational understanding. Does anyone have any thought as where I can research the solution to understand this dilemma? Thanks!!! Quote Link to comment
Roxedus Posted February 10, 2020 Share Posted February 10, 2020 I think this is macvlans doing. 1 Quote Link to comment
TechMed Posted February 10, 2020 Author Share Posted February 10, 2020 Gotcha. So because Letsencrypt is probably creating a private macvlan, it is dropping/refusing anything outside of the vlan/subnet it is on. I am going to try the folks over on the LE thread and see if they can verify. Thanks for the pointer! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.