Unable to setup OpenSolr with new account

Created on 11 November 2024, about 1 month ago

Versions

Drupal Core: 10.3
Search API Opensolr: 2.2.3

Problem/Motivation

I evaluated OpenSolr with a trial account and was very happy with the search results.
Now I have registered another OpenSolr account under the client's name and email address, so future billings can be done via the client's credit card.

However, after going to OpenSolr's module configuration page, selecting the 'Settings' tab at at '/admin/config/search/search-api/opensolr' I always get the 'Authentication failed' message when clicking the 'Test connection' button.
Also, under the 'Autoconfigure' tab there are no regions/versions to select and no 'Start' button either.

Any suggestions on how to trigger the automatic configuration again or get passed the 'Authentication failed' message?

Thank you very much,
Alex

πŸ’¬ Support request
Status

Active

Version

2.2

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States alexi721

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @alexi721
  • πŸ‡·πŸ‡΄Romania bbu23

    Hi Alex,

    Thank you for reporting this issue.

    I think we're missing a "Start over" or "Reset Credentials" option for this particular case. Do you have access to command line to execute a command or are you restricted to using the UI?

  • πŸ‡·πŸ‡΄Romania bbu23

    Actually, do you confirm that you introduced the email and password and saved the configuration here "/admin/config/search/search-api/opensolr"? And after that you triggered the Test connection?

  • πŸ‡ΊπŸ‡ΈUnited States alexi721

    The REST API key changed as I might have clicked on the 'Generate' button inadvertently.
    Anyway, with new key everything is working now and you can mark this ticket as resolved.

    Thank you very much for your prompt response, which I really appreciated.

  • πŸ‡·πŸ‡΄Romania bbu23

    That's great!
    I'm glad that everything is working as expected, and the issue has been resolved!

    Thank you!

Production build 0.71.5 2024