• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk Update redirect error 11444/relay

A

Andrelt

Guest
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
 
What KB article do you mean and what is the problem with applying solution?
 
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?
 
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
 
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.
 
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
 
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?
 
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
 
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?
 
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.
 
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.
 
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.
 
Happy to hear that the issue has been resolved.
Let me know if you have any other issues/comments/suggestions while using Business Manager.
 
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
 
Andrelt said:
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
Click to expand...

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.
 
You must log in or register to reply here.

Similar threads

E
Question Analyzing Maillog: User unable to Send Emails
Replies
2
Views
398
AYamshanov
AYamshanov
P
Resolved Plesk update: ERROR while trying to backup MySQL database
2
Replies
21
Views
558
Dave W
Dave W
A
Issue WP Staging issue
Replies
0
Views
288
Alpha
A
B
Issue Can't redirect to the updates
Replies
2
Views
400
Brian Young
B
IAR
Question Update OpenSSL on CentOS 6.4 (due to ERR_SSL_PROTOCOL_ERROR message)
Replies
1
Views
1K
ChristophRo
ChristophRo
Back
Top