Posts: 7,970
Threads: 554
Joined: Mar 2005
kblagron: Yes, I get the public IP address.
Dean: Yes, DDNS is correct, I even logged in to noip to confirm.
Do you know of some way to ping the CQC server so I can see if this is a port forward issue or CQC issue? I looked up ping syntax, no way to specify a port. I have 2 different ISPs, one is WiFi only and not connected to my network, so I can easily jump on it and actually be "outside" my network.
Posts: 40,483
Threads: 491
Joined: Aug 2002
You can't ping it per se. But if the web server is running and the port forward is working, you should be able to use a telnet client type program to connect to that port at your DDNS address. It won't work since it's not talking to a telnet type interface, but it should be able to connect to the port. If you get an error that it can't open the port, then it wasn't able to get to the web server.
If you try to access your test image it in a web browser, what error do you get?
Dean Roddey
Explorans limites defectum
Posts: 7,970
Threads: 554
Joined: Mar 2005
ok well some progress here, still trying to understand what it means.
I realized I have my old DynDns still setup, just tried that. It pulls up the test image and my years old text-based html CQC page with the values of given fields just fine. That's the insecure port and forward.
I then went back to trying the https way, the test image does NOT pull up.
So either i've gotten the SSL cert installed wrong or I've not forwarded that correctly.
Should I be forwarding port 443 to the CQC web server? Or something else?
Posts: 7,970
Threads: 554
Joined: Mar 2005
12-16-2018, 01:14 PM
(This post was last modified: 12-16-2018, 01:15 PM by IVB.)
btw the error when I use https and don't specify a port is "site can't be reached". Or if I put 443
Posts: 40,483
Threads: 491
Joined: Aug 2002
You should forward whatever port you indicated for secure comms in the installer, which would default to 443 I think, so that unless you changed it.
You sure you set up the certificate for exactly the right spelling of your DDNS name? It has to be exact since that is checked as part of the certificate validation.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
So, from your other post:
Code: 12/16 13:02:02-DESKTOP-DELL, CQCWebSrv, CQCWebSrvWorkerThread3
{
CIDSChan, CIDSChan_SChan_Win32.cpp.359, Failed/Cannot Do, Error: 5003/0/0
Could not acquire credentials. Name=Secure Server Data Source, Code=2148074254
<CQCWebSrv> Win32\CIDSChan_SChan_Win32.cpp - 390
}
The web server said it couldn't acquire credentials for a secure connection. So that would imply that there's an issue with the certificate. Either it's not for the right domain name, or it's not installed in the right place, or the wrong file is installed in the right place.
The text of the actual Windows error that occured is:
"No credentials are available in the security package"
Dean Roddey
Explorans limites defectum
Posts: 7,970
Threads: 554
Joined: Mar 2005
(12-16-2018, 01:42 PM)Dean Roddey Wrote: So, from your other post:
Code: 12/16 13:02:02-DESKTOP-DELL, CQCWebSrv, CQCWebSrvWorkerThread3
{
   CIDSChan, CIDSChan_SChan_Win32.cpp.359, Failed/Cannot Do, Error: 5003/0/0
   Could not acquire credentials. Name=Secure Server Data Source, Code=2148074254
     <CQCWebSrv> Win32\CIDSChan_SChan_Win32.cpp - 390
}
The web server said it couldn't acquire credentials for a secure connection. So that would imply that there's an issue with the certificate. Either it's not for the right domain name, or it's not installed in the right place, or the wrong file is installed in the right place.
The text of the actual Windows error that occured is:
"No credentials are available in the security package"
Ugh, damnit. Okay thanks.
|
