Getting HTTPS cert to work
Posted: Wed Dec 19, 2012 9:46 pmHoping someone can make this a tad simpler for me
I had documentation saved somewhere (of course I can't find it again) about how to install my own cert files for subsonic secure service.
I currently run my own domain, dedicated server with various web services - one of which is subsonic on its own port....
I have the following files already: "xxx.pem" - CLASS1 ; "certificat.crt" ; "key.key" (generic filenames)
The primary goal here is to be able to access my subsonic service via HTTPS without certificate error. Currently in use is the Subsonic self-signed cert which produces a security warning in standard browsers.
** Separate, less important issue** (note: links are dummy links - I am not associated with Domain.com)
Not sure if this is fixable, but I have a 301 set up in a rather odd manner I'd like working better.
pertinent info: This server is hosted behind residential ISP = port 80 blocked
Currently the way it works:
naked domain forwards to HTTPS://www.domain.com via the domain registrar - this specified URL is addressed to my dynamic IP that is updated automatically to the registrar via their dynamic DNS client
Subdomain "subsonic.domain.com" forwards via 301 URL REDIRECT to https://www.domain.com:[HTTPS Port]
What I want:
be able to type in "subsonic.domain.com" and have it forward to "https://www.subsonic.domain.com" without port number showing... just to make it look cleaner... I feel like that's impossible thanks to my ISP blocking port 80, and I can't do the forwarding server-side...rather has to be done all at the domain registrar since all traffic from them has to come over non-standard ports..... my personal website "domain.com" forwards to the HTTPS version at the registrar, and the clean HTTPS URL comes in just the way I like. aslo with no cert errors.... I hope I explained this well enough
I had documentation saved somewhere (of course I can't find it again) about how to install my own cert files for subsonic secure service.
I currently run my own domain, dedicated server with various web services - one of which is subsonic on its own port....
I have the following files already: "xxx.pem" - CLASS1 ; "certificat.crt" ; "key.key" (generic filenames)
The primary goal here is to be able to access my subsonic service via HTTPS without certificate error. Currently in use is the Subsonic self-signed cert which produces a security warning in standard browsers.
** Separate, less important issue** (note: links are dummy links - I am not associated with Domain.com)
Not sure if this is fixable, but I have a 301 set up in a rather odd manner I'd like working better.
pertinent info: This server is hosted behind residential ISP = port 80 blocked
Currently the way it works:
naked domain forwards to HTTPS://www.domain.com via the domain registrar - this specified URL is addressed to my dynamic IP that is updated automatically to the registrar via their dynamic DNS client
Subdomain "subsonic.domain.com" forwards via 301 URL REDIRECT to https://www.domain.com:[HTTPS Port]
What I want:
be able to type in "subsonic.domain.com" and have it forward to "https://www.subsonic.domain.com" without port number showing... just to make it look cleaner... I feel like that's impossible thanks to my ISP blocking port 80, and I can't do the forwarding server-side...rather has to be done all at the domain registrar since all traffic from them has to come over non-standard ports..... my personal website "domain.com" forwards to the HTTPS version at the registrar, and the clean HTTPS URL comes in just the way I like. aslo with no cert errors.... I hope I explained this well enough