On Thu, 7 Apr 2022 at 16:02, Dave Jones <[email protected]> wrote:
> > FPLTCQ1015E ERRNO 10410: 10410 > FPLMSG004I ... Issued from stage 3 of pipeline 3 name "WEENYWEB.REXX:7" > FPLMSG001I ... Running "tcpdata TLSLABEL SMBSSI" > > Turns out that the SSL error number 410 means "SSL message format is > incorrect.". > > How can I troubleshoot this so I can get weenyweb to work? Any ideas on > what's wrong here? > No idea :-) I suspect the browser isn't trying an SSL connection. I trust you made it listen to port 443 before you got here... Since the magic is all happening outside your virtual machine, you'd have to enable the trace in the SSL server. There's nothing in CMS Pipelines to see. An easier trick that might help is to remove the TLSLABEL option and capture the data coming out of TCPDATA. I've done that before to find that the browser was stubborn and "fixed" URL that I provided. It's possible that the browser doesn't like the certificate or ciphers that you offer, and decides to try something else. The 'developer options' in the browser may also show some info. Alternatively, set up a TCP/IP proxy with CMS Pipelines and prepare to get complaints about the person-in-the-middle attack. Sir Rob the Plumber
