Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: New Amazon Echo Support
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
jkmonroe Wrote:this isn't a thing, but you should really consider changing your domain to a TLD per best practices. it makes dealing with issues like this a lot easier, particularly in regards to things like split DNS.

What part are referring to? The internal DNS server?

I set this domain up years ago and using .local for internal was the best practice at the time. Perhaps that has changed. Ill look into it.
Dean Roddey Wrote:That was a typo on my part.

So it should be Store not MStore?
jkmonroe Wrote:do you have both certs installed? you should have your home.zrasdomain.com and the root cert chain for your provider.

The root is in Trusted Root Certification Authorities and in Intermediate Certification Authorities.

home.zrasdomain.com is only in personal and other people.

BTW, thanks for your help.
Dean Roddey Wrote:This is separate from that. If you use https, then the connection will be on 443 (unless you tell the browser to do otherwise) so it will do a secure connection. The secure folders are a separate thing altogether and make the web server do a simple digest challenge to the browser.



Actually it should. If you have a publicly visible DNS name, then using it from inside your network should resolve to your public IP address and should cause you to go out and back in again, or at least to your router and through any port forwarding and such, and it should look like an external access for testing purposes.

Local connections using 443 are not working either.

They do work using port 80.

Definitely a 443 issue.
zra Wrote:Local connections using 443 are not working either.

what does this mean, exactly?

if you're getting nothing at all (page not displayed type of stuff) are you sure CQC is port 443?

you should at least be getting a cert mismatch where it asks you if you'd like to continue.
So using HTTPS using your local computer name works, but but HTTPS using your public DNS name fails, right?
jkmonroe Wrote:what does this mean, exactly?

if you're getting nothing at all (page not displayed type of stuff) are you sure CQC is port 443?

Positive.

jkmonroe Wrote:you should at least be getting a cert mismatch where it asks you if you'd like to continue.

The error is:

This site can’t be reached

10.x.x.x unexpectedly closed the connection.
Dean Roddey Wrote:So using HTTPS using your local computer name works, but but HTTPS using your public DNS name fails, right?

No, HTTP works both internally and externally, HTTPS does not work either way.
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.
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.