OK, I found the problem, due to Rob's suggestion. If I point Firefox to this URL:
https://192.168.128.118:2080/ it works as designed. I was just using 192.168.128.118:2080 before. Many thanks. DJ --- BEST REGARDS DAVE JONES IBM CHAMPION [1] Managing Director for zSystems Support, zLinux, and Cloud ++1 281.578.7544 (Cell) Web: www.itconline.com [2] 18502 Purdy Ct. Houston, TX 77084 USA On 04.07.2022 7:14 AM, Rob van der Heij wrote: > 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 Links: ------ [1] https://www.credly.com/badges/7c92e732-8ab1-4470-98c6-251c33506d69/public_url [2] http://www.itconline.com/
