Hello all, I am having issue with accessing our SCG web dashboard and have been troubleshooting. I used AI to summarize what I've tried before and the context of the issue. Any leads would be appreciated, thank you!

Environment:

Secure Connect Gateway Virtual Edition, Hyper-V deployment, SUSE Linux Enterprise Server 15 SP6
Docker-based (confirmed via docker ps; Podman not installed)
Support ID: 03879033, Enterprise/Perpetual license, support valid through 2/18/2027

Background: Web dashboard was already inaccessible before any upgrade was attempted. Performed a CLI upgrade (SCG-5.36.00.16.bin --upgrade) hoping it would resolve the access issue. Console output reported: "patch update has been successfully completed with the version: 5.36.00.16."

Current symptoms post-upgrade:

Login banner still displays 5.34.00.16 (uncertain if this is expected/cosmetic for CLI patches, or a sign the upgrade didn't fully apply — trying to confirm actual version via /opt/esrsve/version now)
docker ps shows all 3 containers (saede-app, esrsde-app, esrsalert-app) with "Up" status, no restart loops
Port 5700: ss -tlnp shows dockerd listening, but curl (both locally and remotely) returns "Failed to connect... Could not connect to server"
Port 9443: curl gets a response (HTTP-level success), but returns <h1>Page Not Found</h1> at the root path
Full appliance reboot performed — same results persist afterward

Diagnostics run per your VE Troubleshooting Guide:

Inside esrsde-app: wd status connectivityRegistration → RUNNING
Inside saede-app: wd status secureconnectgateway → RUNNING
wd status secureconnectgatewaydb → "Unknown services" (name doesn't appear to exist in this version)
wd health (inside saede-app) → secureconnectgatewayalertservice shows state: FAILED, exitValue: 1, description "Listens for alerts, then publishes them to other plugins"
Attempted to pull logs for the failed service via journalctl -u secureconnectgatewayalertservice, both as the container's default user (sudo password unknown/not provided at deployment) and via docker exec -u root — journal access denied either way ("Failed to search journal ACL: Permission denied... No journal files were opened due to insufficient permissions"), suggesting journald may not be fully functional inside this container.

Question: Is the FAILED secureconnectgatewayalertservice likely the root cause of the dashboard returning 404/refusing connections on both 5700 and 9443? What's the correct way to pull this service's actual error logs given journalctl isn't accessible inside the container — is there a direct log file path we should be checking instead? Also looking for confirmation on which port (5700 vs 9443) is actually correct for VE dashboard access, since your own documentation references both depending on the page.

Browse By Board

Dell Client PowerShell Provider

PowerEdge Wiki

Modular Infrastructure

PowerEdge Servers

Systems Management

Servers

PowerEdge XE7745 - Power Consumption (6x vs 2x RTX PRO 6000 BSE)

Dell Repository Manager 3.5.2 unexpected browser Basic Authentication

R940 PCIe Power

Login to OME ends up in circling line

R6715 hourly latency spikes after iDRAC upgrade to 1.30.20.10

Do we know when Dell is planning on updating SSH in the iDRAC?

Warranty

Dell R520 3 disks in RAID 5, cannot rebuild new disk after replace

48GB RAM

End of life of Dell PowerEdge R360

XR5610 - Part number for onboard SATA cable (SL7_PCH_SA1 to backplane), removing PERC H355

Cannot Access SecureConnectGateway web dashboard.

PowerEdge XR5610

miscellaneous trap

Dell R640 won't POST, no VIDEO

Dell Support Resources

Latest Solutions

PowerEdge XE7745 - Power Consumption (6x vs 2x RTX PRO 6000 BSE)

R940 PCIe Power

48GB RAM

XR5610 - Part number for onboard SATA cable (SL7_PCH_SA1 to backplane), removing PERC H355

Cannot Access SecureConnectGateway web dashboard.