• 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

Issue file 'plesk.list.ai_back' invalid filename extension

M

MiSuisse

New Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
Plesk Obsidian - Version 18.0.51 Update #1
New Thread

Code: 
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Skipping acquire of configured file 'all/binary-amd64/Packages' as repository 'http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease' doesn't support architecture 'amd64'

Code: 
OS : Ubuntu 22.04.2 LTS
Product : Plesk Obsidian - Version 18.0.51 Update #1

Code: 
$ dpkg -l psa plesk-release
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version                                          Architecture Description
+++-==============-================================================-============-===========================================
ii  plesk-release  18.0.51.1-v.ubuntu.22.04+p18.0.51.1+t230404.1037 amd64        Plesk Obsidian v18.0 release marker package
ii  psa            18.0.51-v.ubuntu.22.04+p18.0.51.1+t230404.1037   amd64        Plesk release key package

Upgrade system :
Code: 
$ apt update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://autoinstall.plesk.com/pool/PSA_18.0.51_11495 jammy InRelease
Hit:3 http://autoinstall.plesk.com/PHP74_17 jammy InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:5 http://autoinstall.plesk.com/PHP80_17 jammy InRelease
Hit:6 http://autoinstall.plesk.com/PHP81_17 jammy InRelease
Hit:7 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:8 http://autoinstall.plesk.com/PHP82_17 jammy InRelease
Hit:9 http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease
Hit:10 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Skipping acquire of configured file 'all/binary-amd64/Packages' as repository 'http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease' doesn't support architecture 'amd64'

$ grep -r "WPB_" /etc/apt*
/etc/apt/sources.list.d/plesk.list:deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/WPB_18.0.51_64/  all all

$ grep -r "PSA_" /etc/apt*
/etc/apt/sources.list.d/50sw_autoinstaller.list:deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.51_11495/  jammy all
/etc/apt/sources.list.d/plesk.list:deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.51_11495/  jammy extras
/etc/apt/sources.list.d/plesk.list.ai_back:#deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.51_11495/  jammy extras
 
Arf no time for edit my post lol.
So, i installed new server, but only core plesk is installed, impossible install extension or other dependencies.

but all dependencies is installed ?! no wet, lol !?

Repair :
Code: 
# plesk repair all -y

Reconfiguring the Plesk installation
    Reconfiguring the Plesk installation ............................ [FAILED]
    - Started bootstrapper repair procedure (fast mode). This may
      take a while.
    - Certain actions may be skipped if not applicable.
    -
    -  Finishing up upgrade procedures and rerunning previously
      failed upgrade actions...
    - ===> Cumulative Plesk database upgrade and repair (revertable
      stage) has been started.
    - ===> Preparing Plesk database upgrade (revertable stage).
    - ===> Cumulative upgrade and repair of Plesk database
      (revertable stage) has been completed.
    - ===> Plesk database scheme upgrade has been started.
    - Applying migrations from:
      /opt/psa/bootstrapper/pp18.0.51-bootstrapper/migrations/
    - ===> Plesk database scheme upgrade has been completed.
    -
    - **** Product repair started.
    - Started bootstrapper repair procedure (fast mode). This may
      take a while.
    - Certain actions may be skipped if not applicable.
    -
    -  Trying to start service mariadb... active
    - done
    -  Trying to establish test connection... connected
    - done
    -  Trying to find Plesk database psa... version is 018000000
    -  Trying to backup MySQL database... done
    -  MySQL databases are dumped to
      /var/lib/psa/dumps/mysql.preupgrade.18.0.51-18.0.51.20230406-102746.dump.gz
    -  Finishing up upgrade procedures and rerunning previously
      failed upgrade actions...
    -  Trying to add supplementary group 'lock-manager' for user
      'psaadm'...  already there
    - ===> Cumulative APS controller database (apsc) upgrade and
      repair has been started.
    - Upgrade or repair for 'apsc' (stage 'prep') is not required
    -  Trying to backup MySQL database... done
    -  MySQL databases are dumped to
      /var/lib/psa/dumps/mysql.preupgrade.apsc.18.0.51-18.0.51.20230406-102747.dump.gz
    - ===> Cumulative upgrade and repair of APS controller database
      has been completed.
    - Connection to APSC DB is possible
    - ===> Cumulative APS controller upgrade and repair (final stage)
      has been started.
    - Upgrade or repair for 'apsc' (stage 'post') is not required
    - ===> Cumulative upgrade and repair of APS controller (final
      stage) has been completed.
    - ===> Cumulative Plesk database upgrade and repair (revertable
      stage) has been started.
    - Upgrade or repair for 'core' (stage 'prep') is not required
    - ===> Preparing Plesk database upgrade (revertable stage).
    -  Trying to set psa database version to 018000000... done
    - ===> Cumulative upgrade and repair of Plesk database
      (revertable stage) has been completed.
    - ===> Plesk database scheme upgrade has been started.
    - Applying migrations from:
      /opt/psa/bootstrapper/pp18.0.51-bootstrapper/migrations/
    - ===> Plesk database scheme upgrade has been completed.
    - INFO: Clean install: no
    - INFO: Last executed task: 2022-10-24-19-01-15
    - INFO: All found tasks:
    - 2012-01-13-18-56-00
    - 2012-04-10-14-39-48
...
...
...
    - 2020-03-19-17-13-39
    - ERROR: Upgrade step 2015-06-23-17-35-48_InstallComposer.php
      failed with code 1 and output:
    - INFO: Executing upgrade task: 2015-06-23-17-35-48 (clean)
    - [2023-04-06 10:27:49.074] 174245:642e828511938 ERR [panel]
      Error in cURL request: SSL certificate problem: unable to get
      local issuer certificate:
    - 0: /opt/psa/admin/plib/Upgrade/upgrade.php:46
    - ERROR: Plesk\Upgrade\Exception: Error in cURL request: SSL
      certificate problem: unable to get local issuer certificate
      (upgrade.php:46)
    - 0: /opt/psa/admin/plib/Upgrade/upgrade.php:46
    -
    - INFO: Executing upgrade task: 2019-02-18-14-09-55 (forced)
    - [2023-04-06 10:27:50.000] 174253:642e82855de71 ERR [panel]
      Essential extensions could not be installed (reason: SSL
      certificate problem: unable to get local issuer certificate
    - SSL certificate problem: unable to get local issuer certificate
    - SSL certificate problem: unable to get local issuer certificate
    - SSL certificate problem: unable to get local issuer certificate
    - SSL certificate problem: unable to get local issuer
      certificate). Plesk will automatically attempt to install it at
      a later time.
    - SUCCESS: Upgrade step
      2019-02-18-14-09-55_InstallEssentialExtensions.php was
      successfully done.
    - INFO: Executing upgrade task: 2019-04-25-14-46-58 (forced)
    - SUCCESS: Upgrade step 2019-04-25-14-46-58_ReportUsage.php was
      successfully done.
    - INFO: Executing upgrade task: 2020-03-19-17-13-39 (forced)
    - SUCCESS: Upgrade step 2020-03-19-17-13-39_UpgradeExtensions.php
      was successfully done.
    - Some steps of upgrade failed. Run upgrade with option --repair
      to rerun failed steps.
    -
    -
    - Warning: execute post install/upgrade actions
    -
    - ===> Cumulative Plesk upgrade and repair (final stage) has been
      started.
    - ===> Preparing Plesk upgrade (final stage).
    - ===> Cumulative upgrade and repair of Plesk (final stage) has
      been completed.
    -  Reconfiguring Apache web server...
    -  Reconfiguring ProFTPD FTP server...
    - ===> Configuring ProFTPD server
    -  Reconfiguring AWStats web statistics...
    -  Reconfiguring WatchDog...
    -  Restoring SELinux contexts...
    -  Reconfiguring SSL ciphers and protocols...
    -  Cleaning active Panel sessions...
    -  Fixing permissions on Panel packages files
    -
    - Bootstrapper repair finished.
    - Errors occurred while performing the following actions: upgrade
      Plesk business logic.
    - Check '/var/log/plesk/install/plesk_18.0.51_repair.log' and
      '/var/log/plesk/install/plesk_18.0.51_repair_problems.log' for
      details.
    - If you can't resolve the issue on your own, please address
      Plesk support.
    - *****  problem report *****
    - Warning: execute post install/upgrade actions

Checking the Plesk database using the native database server tools .. [OK]

Checking the structure of the Plesk database ........................ [OK]

Checking the consistency of the Plesk database ...................... [OK]

Checking system users ............................................... [OK]

Checking Linux system files ......................................... [OK]

Checking virtual hosts' file system ................................. [OK]

Checking Plesk version .............................................. [OK]

Checking Apache configuration ....................................... [OK]

Checking for custom configuration templates ......................... [OK]

Checking associations between domains and IP addresses .............. [OK]

Checking for corrupted reference between IP collections and
IPaddresses ......................................................... [OK]

Checking for links between APS applications and subscriptions ....... [OK]

Checking for nginx ULIMIT value ..................................... [OK]

Checking for extra configurations in database not owned by any object
................................................................... [OK]

Checking the status of the required Apache modules .................. [OK]

Checking the configuration of Apache modules ........................ [OK]

Checking web server configuration. Please wait
    Reinstalling SSL/TLS certificates ............................... [OK]
    Applying the default SSL/TLS certificate to all IP addresses .... [OK]
    Repairing web server configuration for all domains. This aspect
    can be used with individual domains ("plesk repair web
    example.com"), and on the server level ("plesk repair web") ..... [OK]
    Repairing server-wide configuration parameters for web servers .. [OK]

Checking the usage of PHP handlers .................................. [OK]

Checking for obsolete PHP-FPM configuration files ................... [OK]

Repairing the mail server configuration
    Reconfiguring all domains and mailboxes .........................   [OK]

Checking the DNS configuration file ................................. [OK]

Restoring DNS server configuration
    Synchronizing DNS zones with the DNS server ..................... [OK]

Checking MySQL database servers ..................................... [OK]

Repair databases on available servers ............................... [OK]

Repair database users on available servers .......................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0
exit status 1


GUI Error
Nouveau projet(3).png
 
As this is a newly installed server, did you check the date and time of the server, as that can lead to SSL-related issues when not correctly set.
 
I would suggest you contact Plesk Support Team:

support.plesk.com

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...
support.plesk.com support.plesk.com

You can still get Plesk Support if your license does not include Plesk support. It's free for the first month.
 
I am still investigating the SSL issue since the Let's Encrypt update, and it appears that the problem stems from the ZScaler certification. Since the update, it requires domains to be whitelisted. Could you please provide me with the list of domains used for the update and maintenance of Plesk Core + extensions?


*.plesk.com
*.api.letsencrypt.org
... ?
 
You must log in or register to reply here.

Similar threads

brother4
Issue Plesk Update: as repository 'http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease' doesn't support architecture 'amd64'
Replies
4
Views
914
Martin Dias
Martin Dias
brainforge
Resolved System updates have started failing.
Replies
2
Views
341
brainforge
brainforge
N
Issue Failed to update Plesk. To solve this problem, you can send the update log to Plesk support.
Replies
4
Views
320
scsa20
scsa20
G
Issue apt-update has errors [Web Presenence Builder, WPB, amd64 unsupported]
Replies
19
Views
3K
brother4
brother4
Luiz_Gustavo
Resolved Update Error - Release does not have a Release file
2
Replies
21
Views
5K
Peter Debik
P
Back
Top