Charmed Quark Systems, Ltd. - Support Forums and Community
New Amazon Echo Support - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: CQC Support (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=9)
+--- Thread: New Amazon Echo Support (/showthread.php?tid=9423)



New Amazon Echo Support - Dean Roddey - 09-12-2016

zra Wrote:No, HTTP works both internally and externally, HTTPS does not work either way.

OK, so that makes some sense I guess. It's pretty much got to be the certificate setup. Just to be sure, go back through the certificate document I wrote up and make sure every i is crossed and every t dotted. Make sure you put the right files in the right place in the certificate store.

And, just to be sure, you did check the 'enable' button on the HTTPS support in the web browser, right? If you forgot to check that, then the other info is ignored.

Also, you don't happen to have another web server running there that might be using 443, do you? You can open a command prompt and admin and do:

netstat -n -a -b > ns.txt


Open that ns.txt file in notepad and search for 443. It should show you the program that has 443 open. That should be CQCWebSrv.exe.


New Amazon Echo Support - Dean Roddey - 09-12-2016

Oops, Jason beat me to it.


New Amazon Echo Support - zra - 09-12-2016

Dean Roddey Wrote:10.x.x.x is a local address, so if you got that address when you used your public DNS name, then something wierd is going on.

I didn't. That was from inside.

From outside, I used my public DNS.


New Amazon Echo Support - zra - 09-12-2016

jkmonroe Wrote:what do you have running on 443?

netstat -ano and see what PID is running 443, then tasklist and find the PID to see the process.

CQCWebSrv.exe


New Amazon Echo Support - Dean Roddey - 09-12-2016

OK, so it's pretty much down to gotta be a certificate setup issue.


New Amazon Echo Support - jkmonroe - 09-12-2016

whats the proper behavior of the CQC web server if there is no cert installed?


New Amazon Echo Support - zra - 09-12-2016

jkmonroe Wrote:whats the proper behavior of the CQC web server if there is no cert installed?

I don't really use it.

I put a test image in the root directory and that displays as expected.

Also, Alexa works with port 80 configured.


New Amazon Echo Support - zra - 09-12-2016

Dean Roddey Wrote:OK, so it's pretty much down to gotta be a certificate setup issue.

Definitely.

Just to be certain. You said the server should be configured with

MStore,My:<certificate name>

Correct?


New Amazon Echo Support - Dean Roddey - 09-12-2016

Quote:whats the proper behavior of the CQC web server if there is no cert installed?

Pretty much I guess what he saw:

Quote:09/12 16:07:32-CQCMaster, CQCWebSrv, CQCWebSrvWorkerThread0
{
CIDSChan, CIDSChan_SChan.cpp.759, Failed/Cannot Do, Error: 5003/0/0
Could not acquire credentials. Name=Secure Server Data Source, Code=2148074254
<CQCWebSrv> CIDSChan_SChan.cpp - 790

}

I was thinking about it in terms of credentials from the other side, but probably it's saying it couldn't load the certificate info.


New Amazon Echo Support - Dean Roddey - 09-12-2016

zra Wrote:Definitely.

Just to be certain. You said the server should be configured with

MStore,My:<certificate name>

Correct?

That should be correct. However, it could be that you have the wrong files in the right places. What type of file did you drop into Personal/Certificates? In my examples it's a pfx file, which is more than a certificate. It's both the private key and public certificate in one file. I'm not sure how you deal with it if you have separate files only for those.