This is the stagnation am getting on web client when I access from a public IP. When I use the servername or IP for the server I log in to GP successfully. This public IP that has a port is pointed to the server IP. Within the site I can access the GP web client using this public IP but away from the site I get the stagnation. What have I not done??.
RomRyan
*This post is locked for comments
Because the certificate is only for *inside* the network and probably uses the machine name where it was created. If the URL to access the server is different on the outside then your certificate will not work, hence the certificate error. Self-signed certificates are not recommended for full blown intra/extra net implementations of web client. You are better off with an Active Directory Certificate Store certificate or a certificate issued by a Third-party Certification Authority such as Comodo, Symantec, GoDaddy, GlobalSign, DigiCert, Verizon or the likes. A Third-party Certification Authority will only issue a certificate for the public facing URL, i.e., somecompany.com, so you will need to setup your routing tables to map internal server names to, let's say, gp.somecompany.com
This a self signed certificate. I can launch web client flawlessly when am clients network but when am outside clients network the stagnation returns.
Your certificate is incorrect according to the picture you posted. In many cases, when the certificate is invalid for the URL you are specifying, you will not be able to log into the application.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,113 Super User 2024 Season 2
Martin Dráb 229,918 Most Valuable Professional
nmaenpaa 101,156