1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Plesk Update redirect error 11444/relay

Discussion in 'Plesk 10.x for Linux Issues, Fixes, How-To' started by Andrelt, May 2, 2011.

  1. Andrelt

    Andrelt Guest

    0
     
    I recently did an update on my Plesk 10.0.1, and i added the business managment and plugin update. The update installed flawlessly, but when i went to go back to my control panel, i am redirected to

    https://edifier.b1fam.com:11444/relay

    How do i fix this issue, i went to the parallels knowledgebase, and found a solution, but i am not sure how to go throught the process, i am not very proficient with linux, so i need some one to walk me through the process. like how to change from old hostname to new one to correct this issue.. please help
     
  2. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,242
    Location:
    Novosibirsk, Russia
    What KB article do you mean and what is the problem with applying solution?
     
  3. Andrelt

    Andrelt Guest

    0
     
    http://kb.odin.com/en/9412

    I know this sounds stupid, but i don't know what values goes in for the old host name and new host name.
     
  4. Paul Martin

    Paul Martin Guest

    0
     
    My situation is similar, but the hostname is correct. I get redirected to "https://<my-correct-domain-name>:11444/relay" but that port is not listening on the server (verified with netstat). Recently upgraded to 10.2, running CentOS 5 x64. Please advise?
     
  5. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,242
    Location:
    Novosibirsk, Russia
    It is sso port. Make sure that sso is on with:

     
  6. EugeneL

    EugeneL Regular Pleskian

    20
    57%
    Joined:
    Feb 18, 2011
    Messages:
    461
    Likes Received:
    0
    Hi, Paul

    If you upgraded to Panel 10.2, port 11444 shouldn't be used any more.
    Try to execute /usr/share/plesk-billing/repair-integration --command=repair-all --idp-url=https://<your-correct-domain-name>:8443
     
  7. Paul Martin

    Paul Martin Guest

    0
     
    Igor, sorry I should have mentioned that - yes, SSO is on.

    EugeneL: are you sure about that? All the documentation I've found indicates that 11444 is still used. It's the 11443 that was replaced with 8443.
     
  8. Paul Martin

    Paul Martin Guest

    0
     
    EugeneL: incidentally, I did that command, and it didn't change anything. It's still trying to go to 11444/relay. Here's the output of "/usr/local/psa/bin/sso -g":


    my plesk-billing # /usr/local/psa/bin/sso -g
    SSO on
    sso server url: https://my.geekniche.com:8443
    sso relay url: https://my.geekniche.com:11444
    my plesk-billing #
     
  9. EugeneL

    EugeneL Regular Pleskian

    20
    57%
    Joined:
    Feb 18, 2011
    Messages:
    461
    Likes Received:
    0
    Yes, for Panel 10.2 SSO has been completely moved to port 8443.

    Try to check file /etc/sso/sso_config.ini if variable "relay_port" has correct value 8443. Try to change it if it's wrong.
    Then try to set SSO properties manually:
    # /usr/local/psa/bin/sso -s -server https://<your-domain-name>:8443 -url https://<your-domain-name>:8443
    # /usr/local/psa/bin/sso -e
     
  10. Paul Martin

    Paul Martin Guest

    0
     
    Checked the file and it was set to 11444. Edited it to 8443, then ran the command you said. No go. For good measure, I ran the repair-all that you mentioned above. Still no go. I bounced the psa service as well as the sw-cp-server service. Nothing. Still redirected to the 11444. Any other ideas?

    Thanks for the help, btw. Where'd you find the information about SSO moving to 8443?
     
  11. EugeneL

    EugeneL Regular Pleskian

    20
    57%
    Joined:
    Feb 18, 2011
    Messages:
    461
    Likes Received:
    0
    I'm a Parallels staff and as far as I know, in 10.2 version ports 11443 and 11444 have been completely substituted by port 8443.

    What is the output of command /usr/local/psa/bin/sso -g now?

    It seems that wrong port is also stored in Panel database.
    Can you log in into Business manager directly using URL https://<your-domain-name>:8443/plesk-billing/admin?
    If so, try to find local Plesk Panel there in System configuration > Server Groups and use tool "Reconnect"

    Or you can send me a credentials to your server and panel via private message and I'll try to troubleshoot your issue
     
  12. Paul Martin

    Paul Martin Guest

    0
     
    my ~ # /usr/local/psa/bin/sso -g
    SSO on
    sso server url: https://my.geekniche.com:8443
    sso relay url: https://my.geekniche.com:8443
    my ~ #

    Ok, NOW I can log into Plesk Billing via the direct URL. Trying to go to 8443 still redirects to 11444, but I couldn't even get into Billing before, so...progress.

    Unfortunately, I'm now stuck at a screen that tells me to change my password, but when I try to, it tells me that the username is already taken (admin). It's acting...special.

    Thoughts?
     
  13. Paul Martin

    Paul Martin Guest

    0
     
    Using a separate admin account let me log in properly. I did the System Config > Server Groups > Reconnect. But browsing to https://my.geekniche.com:8443 still redirects to 11444/relay. Once again...thanks for the help so far.
     
  14. EugeneL

    EugeneL Regular Pleskian

    20
    57%
    Joined:
    Feb 18, 2011
    Messages:
    461
    Likes Received:
    0
    I can suggest almost the last way to try to fix the issue remotely:
    1. Open the Panel database:
    #shell> mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa
    2. Check table misc there
    #mysql> select * from misc where param in ('sso_relay', 'sso_server', 'sso_server_user_url');

    If somewhere there will be incorrect port, fix it:
    #mysql> update misc set val = 'https://<your-domain-name>:8443' where param in ('sso_relay', 'sso_server', 'sso_server_user_url');

    If this doesn't help that only way will be to log in into your server via SSH and try to troubleshoot the issue there.
    You can send me your credentials via PM or e-mail or to open Support Ticket for such purpose.
     
  15. Paul Martin

    Paul Martin Guest

    0
     
    Well, those entries were fine, but the offending entry was the sole entry in the SSOBranding table. Swapped out the 11444 for 8443, and everything works now.

    Thanks for all your help, I was losing my mind over here.
     
  16. EugeneL

    EugeneL Regular Pleskian

    20
    57%
    Joined:
    Feb 18, 2011
    Messages:
    461
    Likes Received:
    0
    Happy to hear that the issue has been resolved.
    Let me know if you have any other issues/comments/suggestions while using Business Manager.
     
  17. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,242
    Location:
    Novosibirsk, Russia
  18. Andrelt

    Andrelt Guest

    0
     
    Igor, i found the Kb article you posted is the exact problem that i am having, but i some baby steps on how to address the problem. I would you like to know could you get me a step by step approach to using this article to fix my issue. such as do i us the vi editor to look into files,etc please help!!
    Andret
     
  19. IgorG

    IgorG Forums Analyst Staff Member

    49
    24%
    Joined:
    Oct 27, 2009
    Messages:
    24,557
    Likes Received:
    1,242
    Location:
    Novosibirsk, Russia
    All information and instructions are described in KB article.
    Sorry, but if you are not familiar with unix command line interface and sql commands - please contact Parallels Support Team.
     
  20. brialyn

    brialyn New Pleskian

    6
     
    Joined:
    Mar 12, 2014
    Messages:
    2
    Likes Received:
    0
    Hi, I'm having similar problems but I cannot say what the cause was. When I try to login to the Plesk panel which I have done many times over many years I get a redirect now. Here's what happens.
    https://173.201.183.63:8443 redirects to https://brialynwebhosting.com.au:8443/relay
    I have tried the command line as expressed in this thread but I cannot get it changed back to what works.
    Should I go and try to change the database somehow?
    Thanks
     
Loading...