04-13-2023 07:45 AM
I have installed the SSM On-Prem 8 202212 ISO. I chose the DISA STIG profile instead of the default one.
After booting up, i can SSH into the machine. However, the Web GUI isn't accessible. The firewall is allowing the traffic.
I am using the https://ip-address:8443/admin/ url to reach it.
Any ideas? In the CLI i can't seem to find a way to turn it on.
04-13-2023 07:57 AM
from command level i will check is the port listing on 8443 :
$ netstat -nlptu
04-13-2023 08:15 AM
Tried this. I don't see any mention of 8443, only 22.
04-13-2023 08:27 AM
Try reload the SSM Server and give some time and test it.
or may be something wrong your installation.
check installation guide.
04-15-2025 08:51 PM
I ran into the same issue thinking that it was issue with the installer/ISO itself but all you gotta do is give it some time and run the following command once in a while till its being shown
netstat -nlptu | grep 8443
after starting the machine
[admin@SSM-On-Prem ~]$ netstat -nlptu
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN -
tcp6 0 0 ::1:6379 :::* LISTEN -
tcp6 0 0 :::111 :::* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
udp 0 0 0.0.0.0:50337 0.0.0.0:* -
udp 0 0 0.0.0.0:5353 0.0.0.0:* -
udp 0 0 0.0.0.0:111 0.0.0.0:* -
udp 0 0 127.0.0.1:323 0.0.0.0:* -
udp6 0 0 :::5353 :::* -
udp6 0 0 :::48863 :::* -
udp6 0 0 :::111 :::* -
udp6 0 0 ::1:323 :::* -
after a while
[admin@SSM-On-Prem ~]$ netstat -nlptu
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN -
tcp6 0 0 ::1:6379 :::* LISTEN -
tcp6 0 0 :::8443 :::* LISTEN -
tcp6 0 0 :::80 :::* LISTEN -
tcp6 0 0 :::111 :::* LISTEN -
tcp6 0 0 :::22 :::* LISTEN -
tcp6 0 0 :::443 :::* LISTEN -
udp 0 0 0.0.0.0:50337 0.0.0.0:* -
udp 0 0 0.0.0.0:5353 0.0.0.0:* -
udp 0 0 0.0.0.0:111 0.0.0.0:* -
udp 0 0 127.0.0.1:323 0.0.0.0:* -
udp6 0 0 :::5353 :::* -
udp6 0 0 :::48863 :::* -
udp6 0 0 :::111 :::* -
udp6 0 0 ::1:323 :::* -
[admin@SSM-On-Prem ~]$ netstat -nlptu | grep 8443
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN -
tcp6 0 0 :::8443 :::* LISTEN -
04-16-2025 01:39 AM
Hi,
Thanks for the suggestion, but this didn't work back then.
I logged a call with Cisco and the outcome of it was "we don't support your hypervisor platform, only VmWare, as is stated in the install guide. We can not help you further."
The thing is, the install guide does provide a setup based on VMWare, but nowhere does it explicitly state "this only works on VMWare". It assumes that the reader will get this information by reading the document.
Oh well, couple weeks wasted having to prove to Cisco that no firewall was blocking, whilst i have sent along screenshots that my firewall indeed isn't blocking traffic (multiple times), but they will not read it. Had to create a VM in the same subnet just to prove that that without a firewall i still can't reach the port.
Support nowadays....
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide