CF 2023 SOLR installed but cant access coldfusion collections

Ah OK, Michael. I see now where I got confused. More on that in a moment.

As for your challenge, I think I see what may be the problem and a solution. Now that you've shared the screenshot of the CF Solr Server page, I see you have an ip address there of 10.81.7.39. The default would be "localhost", but I guess you had your reason for changing it. (Is it that you tried that as a possible fix?)

If you set it back to localhost, does it work? If you felt you needed to change it, see my point 3a below that may be relevant.

Otherwise, I have some refinements/corrections to what I'd offered, and in reply to what else you have now offered.

1) First, let me share that I was thrown off by what you reported in the your original post here, where you shared output from the install log, which you said showed:

Check Disk Space:         C:\ColdFusionAdd-onServices
                          Status: SUCCESSFUL

THAT path reference is why I thought you had installed a separate service. To be clear, there IS support for doing such a separate service with its own installer, but most don't need it. And even in your last reply here you say "I am not trying to run a separate instance of SOLR or anything .. it's completely as it is out of the box. Both installs reported successful installations." By "both installs", I would have thought, "what is this other installer, then?"

But I realize now that you have been referring to the install log you find IN the cfusion/jetty folder. And I am noticing now (for the first time ever) that that log DOES in fact refer to C:\ColdFusionAdd-onServices, even there there is no such directory! I just confirmed, and in fact what I pasted above here is out of my own install log in that cfusion/jetty folder. Wow on that, and a lesson learned. So you can ignore my 3rd bullet. 

2) As for the "solr admin" I referred to in the second bullet, I misread that you meant simply the "solr server" page in the CF Admin (though I did make reference to that as well).  To be clear, there IS an available Solr Admin, which IS available at a different URL than the CF Admin. More on that in a moment

3) As for finding what port Solr DOES listen on, I was mistaken in saying it was in the jetty.lax. (And it's definitely NOT that 8077 which you tried. That's indicated on that line you quoted as being the "stop" port. This has nothing to do with what you'd put in either the CF Admin or in to get to that Solr Admin.)

Instead, the port that the solr service would listen on is defined in the start.ini file| (in that cfusion/jetty folder). And I find for a CF2023 install that it does indeed default to 8995. The line is this:\

jetty.http.port=8995

And indeed THAT is the port you should be putting into that "solr server" page of the CF admin.

3a) Note that right above that is a line that's (by default) commented out as # jetty.http.host=0.0.0.0. That's for indicating the IP address from which Solr is willing to accept connections. And I believe that the default (if it's commented out like that) is to only accept requests from localhost--which makes sense when CF and Solr are on the same box, as here.

But again you had changed your CF Solr Server page to name that other IP Address. If you really feel you MUST do that for some reason, then uncomment this and put in that IP address. (Or you could leave it as 0.0.0.0, which means any IPv4 ip address. And since Solr listens on that non-standard port of 8995 by default, that port would be blocked from access into this machine by any normal firewall.)  Does that help the CF Admin collections page to work?

4) If not, and assuming your port was that 8995 value, what do you see at http://localhost:8995/solr ?  This should show the solr admin I was referring to in my second bullet, and others.

If it comes up, that confirms that indeed Solr is running and on that port. (But since you now confirm you have no collections defined, there's not going to be any "cores" shown via the drop-down on the left of its UI, as I asked about in my last reply.)

5) If instead somehow the UI does NOT come up, for that port found in that start.ini, then that's a problem. And that could also explain why CF was not succeeding in showing collections--when you had the Solr Server page pointing to that "correct" port.

And if that may be what's happening for you (once you correct that port), your next step would be the logs in the cfusion/jetty/logs folder. There's one with the current date pepended to the words ".stderrout.log", so today's would be 2023_09_01.stderrout.log. I realize you may not know how to make sense of all that's there, but give it a look.

(BTW, you can ignore if you see an error like "Address already in use: bind" referring to that very 8070 "stop port". That may be in use by something else, like even CFBuilder running within VSCode. That port is not anything important if Solr is running via that CF Addon service. The stopping of that does not rely on that "stop port". )

6) I will add finally that I have CF2023 running, and the add on service, and it's running on that 8995 port, and I have no problem viewing the "coldfusion collections" page in the CF2023 Admin. I have no collections currently. 

So you should indeed expect that this would be so in your "standard install". There has to be an answer to what's amiss. Hope something above helps. Sorry it's been so many words to help get there.

If the above doesn't help, and others don't offer a better solution, I have still more I could propose for diagnosing things.