Skip to main content
Solved

Command Center unavailable from new Web Server

  • December 13, 2022
  • 4 replies
  • 682 views

LukeBrett
Byte
Forum|alt.badge.img+5

After a hardware refresh of the CommServe, we deployed a new Web Server to use it as our main web console/Command Center. We are able to use the new server’s URL for the web console, but it does’nt work for the AdminConsole/Command Center, we get a 404 error Not Found. The Command Center actually works if we enter the CommServe URL manually, but not with the new Web Server’s URL.

We tried to force the new Web Server’s URL on the CommServe object using the additional setting WebConsoleURL/CommServeDB.GxGlobalParam, but the Command Center is still unavailable. TomCat and IIS were restarted, on the CommServe and the new Web Server, but the Command Center will only work with the CommServe URL.

Anyone had a similar problem or have suggestions? 

 

 

Best answer by LukeBrett

Something must have gone wrong during the installation. I reverted the snapshot and reinstalled the packages and it works fine. Thanks @Mike Struening for your time!

View original
Did this answer your question?

4 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@LukeBrett , can you confirm that nothing else is bound to port 80?


LukeBrett
Byte
Forum|alt.badge.img+5
  • Author
  • Byte
  • 10 replies
  • December 13, 2022

Hello @Mike Struening , thanks for answering. No, nothing else is bound to port 80.


LukeBrett
Byte
Forum|alt.badge.img+5
  • Author
  • Byte
  • 10 replies
  • Answer
  • December 13, 2022

Something must have gone wrong during the installation. I reverted the snapshot and reinstalled the packages and it works fine. Thanks @Mike Struening for your time!


Mike Struening
Vaulter
Forum|alt.badge.img+23

Funny thing is, that was the other go to fix 🤣


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings