#tymm_webhooks

1 messages · Page 1 of 1 (latest)

tranquil slateBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1230068893737947148

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

wide umbraBOT
manic horizon
#

hi! why do you have :444 in your URL?

#

why aren't you implementing SSL normally, on port 443 , and just using the normal URL without a port number?

lavish geode
#

because we have few testing environment and only can be segregated by port numbers

manic horizon
#

ack, I'd suggest finding a different approach, like subdomains or URL query parameters instead

#

if it helps the raw error was error: certificate verify failed (Hostname mismatch)

lavish geode
#

well we were using ports previously and it was working fine. we had a 9443 and 9444 previously for our development and qa server respectively and have never had any issues. just wondering what went wrong in our new setup

lavish geode
manic horizon
#

I think you're returning a cert with centagate.com as the hostname, you can try debug with openssl s_client -connect demo.signingcloud.com:444 etc

lavish geode
manic horizon
#

if you run that command it's in the first certificate in the chain : 0 s:CN=*.centagate.com, O=Signing Cloud Sdn. Bhd., L=Kuala Lumpur, ST=Kuala Lumpur, C=MY but I'm honestly not sure what that represents/means

lavish geode
manic horizon
#

maybe you do something special with returning different certs for different client IPs/locations

tranquil slateBOT