Resolved https://mydomain.com:8447 not resolving

[javierllinas]

Hello,

I just want to know if its possible to reach updates via domain (https://mydomain.com:8447).
I've secured Plesk with Let's Encrypt and have no issues accessing port 8443, but 8447 has never worked via domain URL, and I have to use the IP.

Not a big deal but maybe someone has run into the same.

Best,
J

 

[javierllinas]

Hello,

Just to clarify:

• https://<myIPAdress>:8443 -> Ok
  
• https://<myIPAdress>:8447 -> Ok
• https://<myDomainName.tld>:8443 -> Ok
  
• https://<myDomainName.tld>:8447 -> NOT resolving

I'm trying to make this work with no success, appreciate any guidance.

Best,
J

 

[UFHH01]

Hi javierllinas,

pls. note that

https://<myDomainName.tld>:8447

is not a constant URL, it depends on the autoinstaller session, if you are able to reach it.

After opening => HOME > Tools & Settings > Updates and Upgrades , the opened link "https://<myDomainName.tld>:8443/admin/update/product/" will redirect you to "https://<myDomainName.tld>:8447/summary.html", which will close the session after 30 minutes of inactivity.

I just want to know if its possible to reach updates via domain (https://mydomain.com:8447).

Could you pls. explain in detail, what your desire is? Do you want to check this URL with a crontab? As mentioned above, the possible session depend on an active autoinstaller session and is not a constant URL.

 

[javierllinas]

Thanks for the feedback, UFHH01

After opening => HOME > Tools & Settings > Updates and Upgrades , the opened link "https://<myDomainName.tld>:8443/admin/update/product/" will redirect you to "https://<myDomainName.tld>:8447/summary.html", which will close the session after 30 minutes of inactivity.

Then, what's happening is that "https://<myDomainName.tld>:8443/admin/update/product/" isn't working: HOME > Tools & Settings > Updates and Upgrades has never worked if logged via domain, does that make any sense?

Best,
Javier

 

[UFHH01]

Hi javierllinas,

"https://<myDomainName.tld>:8443/admin/update/product/" isn't working: HOME > Tools & Settings > Updates and Upgrades has never worked

Pls. check with ( logged in as user "root" over SSH ):

ps aux | grep installer

... for ( possible ) orphaned autoinstaller - instances, as only ONE instance is allowed and possible. If you get some outputs with the "grep" - command, pls. kill these processes with the example command:

kill -9 XXXXX

... where "XXXXX" has to be replaced with the unique PID-number from your "grep" - command.
Afterwards, pls. move again to => HOME > Tools & Settings > Updates and Upgrades and an additional tab should be opened at your browser.



If you experience further issues/errors/problems as described, pls. consider to investigate ( possible ) issues/errors/problems with the help of your "panel.log" or/and additional logs at "/var/log/plesk".

=> Plesk for Linux services logs and configuration files ( KB - article: 213403509 )​

Sometimes, it is as well a good idea to change the log - level ( TEMPORARILY! ), to get more informations in Plesk - log - files:

=> How to enable/disable debug logging in Plesk 11.5 and up? ( KB - article: 213408889 )​

 

[javierllinas]

Hi again, @UFHH01

It seems there are some processes going on:

root     1392X  X.X  X.X XXXXXX XXXXX ?        S    16:07   0:00 /var/cache/parallels_installer/parallels_installer_CentOS_7_x86_64_3.21.2 --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
root     1392X  X.X  X.X XXXXXX  XXXX ?        S    16:07   0:00 /var/cache/parallels_installer/parallels_installer_CentOS_7_x86_64_3.21.2 --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser
root     1573X  X.X  X.X XXXXXX   XXX pts/0    S+   16:18   0:00 grep --color=auto installer

Is it safe to kill those? How is this done?

Also, keep in mind that HOME > Tools & Settings > Updates and Upgrades does work if I log in using the IP ("https://<myIP>:8443/admin/update/product/")

Thanks for your attention.
Best,
J

 

[UFHH01]

Hi javierllinas,

Is it safe to kill those?

Yes, it is.

How is this done?

I already mentioned the "kill" - command with my previous post at: => #5 ... Have you got problems using the "kill" - command? Pls. explain with more details where you are stuck and experience ( possible ) issues/errors/problems.

 

[javierllinas]

I already mentioned the "kill" - command with my previous post at: => #5 ... Have you got problems using the "kill" - command? Pls. explain with more details where you are stuck and experience ( possible ) issues/errors/problems.

You did, but I'm afraid I'm not used to the syntax: is it

kill 13924 0.1 1.8 153328 34392

?
How long is the ID? Is it like this (bold/red characters) -> root 13925 0.0 0.1 109716 2748 ? S 16:07 0:00 /var/[...]

Please, excuse my ignorance.

 

[UFHH01]

Hi javierllinas,

kill -9 XXXXX

As you can see the command - string is devided into three parts:

• kill
• -9
• XXXXX

When you use the "ps" - command, the SECOND output is the desired "PID-NUMBER" ( ... which is the "XXXXX" within my previous example )

Example ( from YOUR provided ps-command - output )

kill -9 13924

 

[javierllinas]

Thanks for the clarification, UFHH01.

Unfortunately, killing the processes did not have effect on the issue: still can't load Updates and Upgrades URL using domain.

Also, it seems that Plesk is running processes constantly, so they keep appearing. This process, in particular, keeps and keeps appearing within the same session and different IDs:

root     XXXXX  0.0  0.0 112668   944 pts/0    S+   18:37   0:00 grep --color=au  to installer

I'll check the logs as you've suggested.

Thank you for your time.
Best,
J

 

[UFHH01]

Hi javierllinas,

and did you try to use:

plesk installer --select-product-id plesk --select-release-current --reinstall-patch --install-component base

and the Plesk Repair Utility ( => Plesk Repair Utility ) with the example command:

plesk repair all -y -v

In addition, pls. make sure, that you opened all necessary ports at your firewall and IF you use Fail2Ban on your server, pls. don't forget to add localhost and your server IP(s) onto your whitelist, to avoid issues/errors/problems.

 

[javierllinas]

In addition, pls. make sure, that you opened all necessary ports at your firewall and IF you use Fail2Ban on your server, pls. don't forget to add localhost and your server IP(s) onto your whitelist, to avoid issues/errors/problems.

Yes, all Plesk ports are open. I also use Fail2ban, and have my IP whitelisted, and I guess localhost is added correctly

127.0.0.1/8

I'll try what you've just suggested, thank you very much

 

[javierllinas]

Hello,

Just an update on this: the only way I could make this work was using the hostname, in my case https://mail[dot]mydomain[dot]com:8447

Thanks @UFHH01 for your willing to help.

Best,
Javier

 

[Alex Movergan]

It must be Cloudflare. It doesn't proxy 8447 port