|
Hi Greg,
I'm reasonably certain this error is caused by the "Host or IP Address" you
specified in the Code for I connection profile of tbfpwr9 not matching the
certificate name of tbfpwr9.totalbiz.local.
Even though based on the names I'm sure they point to the same IBM i host,
they are not identical. If possible, change the "Host or IP Address" in
you
code for I profile to tbfpwr9.totalbiz.local. Basically, it has to match
your certificate.
Rob W.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Greg
Wilburn
Sent: Monday, May 18, 2026 11:32 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: VS Code debugger
I'm forcing myself to learn VS Code - it is painful to say the least (not
that RDi wasn't).
I'm pretty sure that I'm up to date on Code for IBM i as well as IBM i
debug. However, I'm getting an error when attempting to debug as a batch
job or service entry point.
EQAVS1007E tbfpwr9 on port 8005 could not be connected.
Message received: Hostname/IP does not match certificate's altnames: Host:
tbfpwr9. is not in the cert's altnames: DNS:tbfpwr9.totalbiz.local
I had to set this up manually in Navigator using the same certificate we
use
for internal connections.
I tried creating the launch.json as well.
We use this same certificate for all other Apache connections for our
internal PC's.
Any ideas?
TIA,
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.