🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Login PubSub+ Broker Manager Failed

cjhuaxin
cjhuaxin Member Posts: 9 ✭
in PubSub+ Event Portal #1

I don't know why, but the two brokers I deployed (one single node and one HA) suddenly can't log in, they have been fine before, before that I did an operation to create a DMR cluster (external link) for these two brokers.
Both nodes are prompted with the same error message


Best Answer

  • ChristianHoltfurth
    ChristianHoltfurth Member, Employee Posts: 75 Solace Employee
    #2 Answer ✓

    Hi @cjhuaxin ,
    What's the URL in your browser your are pointing to?
    The screenshots in the console seem to indicate that you are pointing the browser to the private monitoring API of the broker and I'm wondering, if that might be the issue.
    Can you point your browser to your broker's admin interface directly, something like http://34.150.121.188 and see, if you can log in there?

Answers

  • ChristianHoltfurth
    ChristianHoltfurth Member, Employee Posts: 75 Solace Employee
    #3 Answer ✓

    Hi @cjhuaxin ,
    What's the URL in your browser your are pointing to?
    The screenshots in the console seem to indicate that you are pointing the browser to the private monitoring API of the broker and I'm wondering, if that might be the issue.
    Can you point your browser to your broker's admin interface directly, something like http://34.150.121.188 and see, if you can log in there?

  • cjhuaxin
    cjhuaxin Member Posts: 9 ✭
    #4

    @ChristianHoltfurth
    Thank you very much, I'm pretty sure the browser URL is http://34.150.121.188:8080, but I'm back to normal now.
    I'm watching to see if this problem will occur again, thanks again.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #5

    Are these Docker containers, or machine images? Can you still log into CLI? Either via SSH'ing to port 2222, or doing docker exec -it <solaceContainerName> cli if using Docker, or via solacectl cli if using a machine image? We might be able to extract some diagnostics if you can get into CLI.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #6

    @cjhuaxin glad to see it is working, just a misunderstanding!

    How did you manage to find that weird URL anyhow?

    Also, I made you a queue. ;-)

  • cjhuaxin
    cjhuaxin Member Posts: 9 ✭
    #7

    @Aaron
    When this problem occurs, can I log into the CLI normally, do I need to provide any log information?
    Also, this URL in the screenshot above is what appears when I click on the login on the interface

  • ChristianHoltfurth
    ChristianHoltfurth Member, Employee Posts: 75 Solace Employee
    #8

    @cjhuaxin Glad to hear it's working! :)

Categories

This Month's Leaders

This Week's Leaders