ColdFusion 2023 IIS 10 tomcat loses vhost on remote requests but loads okay on loopback

[thomas_1319]

I had multiple sites serving OK from IIS as part of a platform migration from CF 2018 to CF2023.

After applying my agency's wildcard cert in the IIS Bindings panel for each site

, both would load correctly browsing from the IIS Management context (I have a hosts file to resolve for loopback)

, but one of them respondes with a 404 from the servlet container when request is from a remote host and another loades normally when remote request.

I pretty familiar with wsconfig and the webserver connector implementation but have never seen this happen before. I've deleted the connector configurations and rebuilt them both individually and a a single 'all websites' wsconfig configuration. Restart IIS and the CF Application service, and clearing cfclasses as well.

I've also deleted the websites in IIS and wsconfig files, starting over (rinse/repeat).

Again, this misbehavior only happened after applying SSL binding. I don't have the AJP communication SSL'd, only the HTTPS protocol..

BTW, I registered on Adobe Account but creating a ticket there is obfuscated by the chatbot so badly I gave up there (it seems to think there are no ColdFusion Server Editions beyond 2018). Is there an alternate URL which will allow me to request starting a support request bypassing the bot?
Really annoying!!!

Thanks,

Tom

[sdsinc_pmascari]

This does sound bizarre.  Try a direct email to Adobe CF support.  I've found them to be remarkably responsive.

cfsup@adobe.com

[thomas_1319]

Will do.

Thanks!

[thomas_1319]

No reply from them.

The email looked familiar. I looked back searching in my client for previous threads.

I tried last year to get help that way, without any reply.

I contacted Charlie and eventually was able to work through that issue reading his blog.

But never heard anything from Adobe directly..

Actually now that I think about it, as long as I've used CF I've never been able to raise a response from Adobe staff.

(Since cfmx days - Sean Corfield answered an email once but he was no longer with Macromedia)

I 'll try going through the sales/vendor and see if my agency can get an 'official' account set up.

[Charlie Arehart]

Thomas, a few things:

• I don't see an email from you. Can you confirm the subject (or from address)? In any case, glad you feel ou found an answer in my blog. You might want to let folks know what it was (the answer you came up with, and/or the specific blog post)
• As for reaching Adobe directly, the email address BKBK gave you will get you to them, 100%. And it's NOT one that you will find offered if you go to Adobe.com and try to seek support.
• Indeed, in your saying you could not find the right place to report a bug, I lament also that that can happen with that normal adobe.com support chat, etc. Honeslty, don't use that for CF. CF is the red0headed step child in Adobe. 98% of folks at Adobe can't even spell it. Seriously. And the support mechanisms for Adobe.com are for the majority of OTHER Adobe products, not CF.
• Fortunately, the CF *TEAM* in Adobe is VERY committed to CF and are responsive. My comment above is about that vast majority of Adobeans (several tens of thousands) who are NOT on the CF team.
• To file bug reports or feature requests for CF, use tracker.adobe.com. There you absoltely will be able to select CF2023 or 2021, and fare more CF-specific characteristics
• That said, it's not a place to request "support". This is better for that, and the cfsup address is for when someone feels that a problem requires only Adobe's help, rather than something that we here in the community might help with (though often, we can help more than some would expect).

Hope all that's helpful.

[thomas_1319]

Hi Charlie,

We had a back and forth July 2023 amid the final patching of CF2018. Recall looking into the State of Florida vendor list?

I guess I misspoke to some extent - I did receive assistance from Adobe this May, but it was only because online license registration wasn't working for us. We did get that resolved.

With the current issue I suspect it's due to my unfamiliarity with new binding options available in IIS 10.

Do these choices look reasonable?
(I see a warning about not having a Default SSL site configured, but not on all sites)

Tom

[Charlie Arehart · Accepted solution]

For the sake of others following along, when I got back to him that day (Aug 29) Tom let me know he'd been in touch with Adobe and had solved the problem. See below where he started another thread reporting that, and that he may have more to share in time.

[thomas_1319]

I've been contacted by support, will try to summarize whatever the resulting fix might be.

Thanks to all,

Tom