Closed EricFROL closed 9 months ago
@EricFROL I saw this come up on the Discord, and had a thought. If the ingress node is behind a firewall, are you able to forward TCP & UDP 51821-51831 to it? Or if it's something like a home connection, are you able to designate the ingress as a DMZ target?
@EricFROL we don't block ingress creation even if host is behind NAT, on the UI we just show a warning, so I am not sure from where exactly are you getting this response can you confirm your server version again?
@unquietwiki I currently have firewall disabled, so that can't be... how can I designate the ingress as a dmz target??
@abhishek9686 yes, v0.20.2
@unquietwiki I currently have firewall disabled, so that can't be... how can I designate the ingress as a dmz target??
@abhishek9686 yes, v0.20.2
okay that's an old version, this check has been removed in newer versions
Well that's the version stated in https://docs.netmaker.io/quick-start.html. Should I put latest?
Well that's the version that is stated in https://docs.netmaker.io/quick-start.html. Should I put latest?
we are updating the docs, use v0.21.2
Closing as working on v0.21.2. Thank you.
Contact Details
No response
What happened?
Just decided to set up netmaker. I have followed all previous steps fine, until I need to set up Ingress + External Clients. Adding any of my three connected hosts as a client returns me this alert as a popup (they all are on the same local network):
Am I doing something wrong?
Version
v0.20.2
What OS are you using?
Linux, Windows
Relevant log output
No response
Contributing guidelines