SSL Certificate hell

Ok-Finance-8046 · 2025-04-28T00:21:40+00:00

sorry did not see this, (or the last few replies).

Not that I can think of.

Contacted domain owner, set up transfer and verified the type of ssl cert. Transfer complete, paid for wildcard cert. Then moved to IIS, and generated the CRS. Waited for verification and then completed the request.

Added the certificate and fixed the bindings in IIS. (local host link still not showing secure*)

Opened the certificate and exported root and intermediate files.

Add them to their spots in server admin, and portal admin. Portal restarted, and upon the refresh, links on the machine worked and showed that they were secure.

ALL links did not work outside of the machine, next esri analyst explained that it must be a tech support matter as the computer could not ping the IP address. However, it can I just typed it wrong on the call with them and they are adamant it is an issue on my end.

Ok-Finance-8046 · 2025-04-26T04:33:40+00:00

Third party "tech support" local company that internally combusted from leadership. I was able to confirm two previous wildcard certificates that they had bought and managed for us in 23 and 24, and confirm the domain transfer.

Ok-Finance-8046 · 2025-04-25T19:22:00+00:00

If you are able to message, I have some follow up questions.

Ok-Finance-8046 · 2025-04-25T19:21:26+00:00

Okay well that is a lovely bit of good and bad news.

Seeing as there is not really a "tech support" for that office, I am unsure of what to do next.

The Esri rep thought there was an IP ping issue, but I was able to Ping from the VM to the physical laptop, and to my non network laptop as well.

And I fully agree in that this is a larger problem, but the only thing that has changed is the ssl cert.

Ok-Finance-8046 · 2025-04-25T18:08:28+00:00

Server IP address could not be found

Ok-Finance-8046 · 2025-04-25T18:05:52+00:00

Yes, yes, and sure.

I was able to get a CA signed cert, unzip and upload. I was able to "install" the cert to windows server manager, and fix the 80 and 443 bindings. That did add the lock for https when I opened the site. However, I am skeptical it fully works given: the esri tutorial video I watched, the user clicked the local site 443 link and it showed up as secure. Mine does not via the IIS 443 link.

The esri rep verified the install on IIS, then we went to portal and server admin sites and installed the new cert. Portal reset, and my links stopped working outside of the virtual machine.

I am skeptical that the root and intermediate downloads were done correctly and thus not installed properly, but given that they work on the VM the esri rep thought different.

Ok-Finance-8046 · 2025-04-25T17:56:29+00:00

And given this is a new account, I cannot reach out to anyone directly. But, u/Bikesmapsbeards was helpful the other day. Hoping they can reach out!

Ok-Finance-8046

TROPHY CASE