#Outside Access
6 messages · Page 1 of 1 (latest)
You portforward the ports 80, 443 and the ports you set for wings
Great! most inexperienced people go straight to a script (which we're glad you didn't).
If you set it up so it only works inside your local network, and this has been tested, we're going to need to do a few things:
-
Port forward ports 80 and 443 (for the panel) and 8080 and 2022 (for wings), assuming you didn't change them.
-
Check if you used your Local (private) IP or Public IP for the 'FQDN' setting in the node.
i. If it's your local (private) IP, change it to your public IP. ii. If it's already public, you're all good to go! -
Once ports have been forwarded and FQDN has been checked, tell your friends outside of your local network to test it, by connecting to your public IP. If it doesn't work, 9 times out of 10 (or more) its a port forwarding issue.
-
Try connecting yourself. You can connect to the panel yourself the same way, but if you're unlucky then you will get a red heart to the node, that is only there on your local network, but it works everywhere else. In this can, type
.natfor the fix.
Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.
bad bot
So typically instead of port forwarding I tunnel my ports and create a bridge connection from external and internal that way. I'm guessing I can't apply that here and have to go directly through my firewall and open it up? Thanks also