Hello YaskoT,
Could you please share which version of SCG Virtual Edition is installed? I've made a research and found follow troubleshooting guide:
Could you please check it?
Please ask me if you have any questions.
Hi Maria,
Thanks for the quick reply, here are the details:
$ cat /etc/os-release
Name= "SLES"
VERSION= "12-SP5"
VERSION_ID="12E Linux Enterprise Server 12SP5"
ANSI_COLOR=0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp5
Hello YaskoT,
Thank you for your reply.
Could you please also share version of SCG?
Did you check troubleshooting steps from documentation, I've sent previously?
Please ask me if you have any questions.
Hi Maria,
The version the Secure Connect Gateway Virtual is Edition 5.00.07.10 for Microsoft Hyper-V Systems.
and , yes i followed this instruction prior to the install.
Hello YaskoT,
Thank you for your reply.
What browser do you use? You can access the secure connect gateway user interface using the following web browsers:
Mozilla Firefox 88
Google Chrome 91
Microsoft Edge 91
Also it is recommended to perform follow steps:
-Ensure that the required ports are configured on the local system.
Network reqiurements you can check here on page 10:
-Log in to the local system through Secure Shell (SSH) using the root credentials.
-Run docker exec -it esrsde-app bash to access the SRS container.
-Run systemctl status connectivityRegistration to verify if the connectivityRegistration service is
running.
-Run docker exec -it saede-app bash to access the SAE container
-Run systemctl status secureconnectgateway and systemctl status secureconnectgatewaydb to
verify if the secureconnectgateway and secureconnectgatewaydb services are running
-If the services are not running, perform the following steps:
1)Run docker restart esrsde-app to restart the SRS container.
2)Run docker restart saede-app to restart the SAE container.
-Retry accessing the user interface.
Retry accessing the user interface.
-Log in to the local system through Secure Shell (SSH) using the root credentials.
-Run docker exec -it saede-app bash to access the SAE container.
-Go to /var/lib/docker/volumes/saede_logs/_data
-Check the application.log file to identify the component that failed to load.
If the issue still persists, reboot the local system.
Thank you.
Hi Maria,
After running the following, here is what i get:
systemctl status connectivityRegistration
? connectivityregistration.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
systemctl status secureconnectgateway
? secureconnectgateway.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
systemctl status secureconnectgatewaydb
? secureconnectgatewaydb
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
PS. I have rebooted the system multiple times, also reinstalled/reconfigured the .vhd on Hyper-V.
Hello YaskoT,
Thank you for your reply. May I please also ask you, what browser do you use?
Hi Maria,
I have tried with Chrome and Edge.
Thanks,
Hello YaskoT,
Thank you for your reply. I make a research and write you as soon I find a solution for you. Did you contact Technical Support?