-
-
Notifications
You must be signed in to change notification settings - Fork 158
Solr cloud working internally but admin interface unreachable #222
Comments
Please provide your docker-compose.solr.yaml, that will heop loads. Are you using exactly the one here? You'll also want to take a look at If you'd do a If you just use the ddev-drupal9-solr add-on in a dummy project (like a Drupal 9 quickstart) does it work properly? (Do a D9 quickstart and |
Thanks for the quick response! I'm using the standard docker-compose.solr.yaml with the three node SOLR Cloud. I have now done a completely fresh D9 quickstart site and installed the addon and I can't reach the solr admin for that either. This is the ddev debug test output for that: Is it possibly a WSL2 thing? Although I've not noticed this problem with other services running on exposed ports like MailHog or Kibana. I've been using DDEV for a while but I'm not that knowledgeable of docker so I'm not sure how to go about troubleshooting this. |
This is the output from
|
Hmm, the 8983 port is not https by default; IIRC solr doesn't work right on https. If you do a But somebody had a problem like this in https://discord.com/channels/664580571770388500/1069909810134397009/1069909810134397009 and their result was that chrome was automatically redirecting to https without their permission. Make sure you use Try using |
BTW, using Chrome I'm getting the same redirect problem; have to force the url to |
I had tried that earlier and had no luck but I was trying it again with the quickstart / addon site and I can confirm it's working on the quickstart addon site now with http but I get this error on the SolrCloud site:
|
Please provide the docker-compose.solr.yaml that you're using, thanks, and when you show an error message like that please show the URL you're using to get it (and try it with |
Ha. Silly me. That 503 was because my original site was shutdown during the debug process. Also silly me as it would seem that Chrome is indeed the culprit. Even when I typed http:// Chrome was changing it to https://. I launched FireFox and now it's working. Looks like it was user error all along, with a little bit of help from Chrome. ;-) On the plus side, I can confirm that the SolrCloud contrib works. :-) Also, thanks for the assistance and for DDEV. It's an excellent tool! :-) |
Yay! |
Hi. I wonder if anyone can give me any clues on this. I've managed to get Solr Cloud working with 3 nodes. It is all set up as a search_api server / index and it would appear to be working as intended. Yay!
However I can't seem to get to the admin ui and I just get a 404 when I go to https://[sitename].ddev.site:8983/
If I SSH to the web container I can reach it fine from the command line with the SOLR Server URI I specified for Drupal.
Would anyone be able to shed any light on this? It seems like it should be a simple thing to sort out but I am having no luck with it. I wondered if it was something to do with solr running on http and ddev on https.
The text was updated successfully, but these errors were encountered: