This is well and good, except the website and certificate aren't being managed
by IIS, but some other open source app that I can find even less information on
than openssl. The common thread between them is they both have the same
instructions on how to create/install/renew the certificate
Just to let everyone know, this project is on hold for the forseeable future.
We are looking at an alternative way to setup the reverse proxy and certificate
that falls more into the realm of what we as Microsoft guys are familiar with.
I.E. IIS based sites and certs. Thanks for the input
Hey everyone. I'm still not so into this so here I go again.
I am trying to rewenew an expeired certificate on a windows server 2003
machine. None of the steps in the RenewCert.txt document seem to apply. I did
not set this server up originally and I need lots of help trying to figure this
The problem is with installing it on the server. It is a windows 2003 server
with II6, however the certificate isn't being handled by IIS. I have no real
clue how this thing was set up so I'm grasping at straws. Gotta love clients
that hire college kids to do work, then are stuck when the kid
I have the renewed cert, I just can't figure out how to get it on the server.
If IIS was managing the certificate and the websites on this server I'd be
fine, but that isn't the case. I'm grasping at straws trying to follow up
undocumented work by a college kid for this client. Yay for me!
First off I'm a complet noob here. I don't do open source and I'm not a
programmer.
I have been handed a job that goes something like this.
A webserver has a certificate that has expired. Openssl was used to create the
cert, and is used as a proxy of some sort to handle redirects. I have
