Change listening port on management interface #13529
Replies: 1 comment 5 replies
-
You're trying to access the SOC web interface from the Internet? Is that the ultimate goal here? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.80
Installation Method
Security Onion ISO image
Description
configuration
Installation Type
Distributed
Location
on-prem with Internet access
Hardware Specs
Meets minimum requirements
CPU
4
RAM
16
Storage for /
200
Storage for /nsm
200
Network Traffic Collection
span port
Network Traffic Speeds
Less than 1Gbps
Status
Yes, all services on all nodes are running OK
Salt Status
No, there are no failures
Logs
No, there are no additional clues
Detail
Hi all,
I have done port forwarding on router from my public IP port 7823 to Manager LAN IP 192.168.10.100. changed URL base to match public IP of router and does not work. Manager redirect back to Public IP and changes port to 443.
I have tested port forward 443 to 443 it is working, but 7823 does not. I started dig in one of possible solutions is to forward 7823 to 7823 on manager, but also docker needs to listen on port 7823 and forward to container on 443, this at least does not touch nginx configuration.
Please advice easiest way to achieve this, I have other services which already use 443 and I am not in situation to use 443 for Manager.
Thanks in Advance
Surba
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions