• 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

Resolved Extensions: Internal server error

alegsa

New Pleskian
Hi. When I go to Extensions, I get this error:
Internal server error Retry

error.jpg
I don't know what is wrong...

Thank you
 
Try to run on Plesk server following command:

Code:
# wget https://ext.plesk.com

Do you see any certificate related errors?
 
wget Plesk Extensions

Result:

--2020-04-10 05:06:09-- Plesk Extensions
Resolving ext.plesk.com (ext.plesk.com)... 185.180.13.19
Connecting to ext.plesk.com (ext.plesk.com)|185.180.13.19|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

[ <=> ] 19,121 --.-K/s in 0s

2020-04-10 05:06:10 (338 MB/s) - ‘index.html’ saved [19121]
 
Are you sure that command was correct? It should be

Code:
# wget https://ext.plesk.com
 
wget Plesk Extensions

Result:

--2020-04-10 05:06:09-- Plesk Extensions
Resolving ext.plesk.com (ext.plesk.com)... 185.180.13.19
Connecting to ext.plesk.com (ext.plesk.com)|185.180.13.19|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’

[ <=> ] 19,121 --.-K/s in 0s

2020-04-10 05:06:10 (338 MB/s) - ‘index.html’ saved [19121]
 
Try to remove extension catalog cache with following commands:

# rm -rf /usr/local/psa/var/cache/https*
# plesk db "delete from PersistentCache where events like '%catalog%'"
# service sw-engine restart
 
Are you sure that command was correct? It should be

Code:
# wget https://ext.plesk.com
mr igor, I don't have extesions, why is it returning the following error when I run the command?

[root@*****~]# wget Plesk Extensions
--2021-10-06 14:44:22-- Plesk Extensions
Resolving ext.plesk.com (ext.plesk.com)... failed: Name or service not known.
wget: unable to resolve host address ‘ext.plesk.com’
 
FYI Guys, if you already tried all these things and the issue persist, Check:
Code:
Date
On the server. I was fighting with this and the issue was solved by updating the date and time on the server. In this case, to apply an easy fix I ran the following:
Code:
ntpdate 0.us.pool.ntp.org

I hope helps someone. :)
 
Are you sure that command was correct? It should be

Code:
# wget https://ext.plesk.com
ssh display:
ERROR: cannot verify ext.plesk.com's certificate, issued by ‘/C=US/O=Let's Encrypt/CN=R3’:

Issued certificate has expired.
 
Try to run on Plesk server following command:

Code:
# wget https://ext.plesk.com

Do you see any certificate related errors?
I have the same problem and YES I see certificate error.
What can I do to solve the problem? :(

[root@plesk ~]# wget Plesk Extensions
--2022-04-28 20:25:09-- Plesk Extensions
Resolving ext.plesk.com... 212.102.55.131, 212.102.55.139, 2a02:6ea0:d500::5, ...
Connecting to ext.plesk.com|212.102.55.131|:443... connected.
ERROR: cannot verify ext.plesk.com’s certificate, issued by “/C=US/O=Let's Encrypt/CN=R3”:
Issued certificate has expired.
To connect to ext.plesk.com insecurely, use ‘--no-check-certificate’.
 
Try to run on Plesk server following command:

Code:
# wget https://ext.plesk.com

Do you see any certificate related errors?
I have the same problem and YES I see certificate error.
What can I do to solve the problem?


[root@plesk ~]# wget Plesk Extensions
--2022-04-28 20:25:09-- Plesk Extensions
Resolving ext.plesk.com... 212.102.55.131, 212.102.55.139, 2a02:6ea0:d500::5, ...
Connecting to ext.plesk.com|212.102.55.131|:443... connected.
ERROR: cannot verify ext.plesk.com’s certificate, issued by “/C=US/O=Let's Encrypt/CN=R3”:
Issued certificate has expired.
To connect to ext.plesk.com insecurely, use ‘--no-check-certificate’.


[root@plesk ~]# host ext.plesk.com
ext.plesk.com is an alias for 1648825949.rsc.cdn77.org.
1648825949.rsc.cdn77.org has address 212.102.55.130
1648825949.rsc.cdn77.org has address 212.102.55.139
1648825949.rsc.cdn77.org has IPv6 address 2a02:6ea0:d500::6
1648825949.rsc.cdn77.org has IPv6 address 2a02:6ea0:d500::5


[root@plesk ~]# ping -c4 ext.plesk.com
PING 1648825949.rsc.cdn77.org (212.102.55.130) 56(84) bytes of data.
64 bytes from unn-212-102-55-130.cdn77.com (212.102.55.130): icmp_seq=1 ttl=55 time=8.44 ms
64 bytes from unn-212-102-55-130.cdn77.com (212.102.55.130): icmp_seq=2 ttl=55 time=8.51 ms
64 bytes from unn-212-102-55-130.cdn77.com (212.102.55.130): icmp_seq=3 ttl=55 time=8.46 ms
64 bytes from unn-212-102-55-130.cdn77.com (212.102.55.130): icmp_seq=4 ttl=55 time=8.46 ms

--- 1648825949.rsc.cdn77.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3013ms
rtt min/avg/max/mdev = 8.447/8.473/8.516/0.115 ms
[root@plesk ~]#


Plesk details:
OS: ‪CentOS 6.6 (Final)‬
Plesk Onyx V. 17.8.11
 
Try to remove extension catalog cache with following commands:

# rm -rf /usr/local/psa/var/cache/https*
# plesk db "delete from PersistentCache where events like '%catalog%'"
# service sw-engine restart
unfortunately it was not enough to solve the problem
 
Try to remove extension catalog cache with following commands:

# rm -rf /usr/local/psa/var/cache/https*
# plesk db "delete from PersistentCache where events like '%catalog%'"
# service sw-engine restart
Worked for me. I got into the issue after installing Plesk Obsidian 18.0.59 (from Plesk Obsidian 18.0.55) today.

Then i removed "Plesk Email Security" and after realizing was not the cause of Resolved - Arc errors in maillog i tried to reinstall.

I clicked on "Plesk Email Security" (from catalog) but the browser returned back (nothing happen)

Going directly to the extension link DOMAINNAME:8443/modules/catalog/index.php/catalog/package/email-security i notice the "Internal Server Error" message.

PS: wget https://ext.plesk.com was working fine .. but didn't solve the issue.

I think this is normally a bug into Plesk and should be fixed ..

Thank you!
 
Back
Top