• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Internal Web Presence Builder error

Monty

Silver Pleskian
Plesk Guru
Username:

TITLE

Internal Web Presence Builder error

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Product version: Plesk Obsidian 18.0.53.1
OS version: CentOS 7.9.2009 x86_64
Build date: 2023/06/13 09:00
Revision: 3988a02704d3a3a48ed93ab21c8de546d1a69d77

PROBLEM DESCRIPTION

When trying to edit a website with Presence Builder the following error is displayed:

Code:
Internal Web Presence Builder error.
File: /usr/local/psa/admin/plib/vendor/plesk/zf1/library/Zend/Log.php; Line: 348
Message: PHP Warning : date(): We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead; Code: 2

STEPS TO REPRODUCE

  • Login to Plesk
  • Select a website that was created with Presence Builder
  • Click on "Presence Builder"

ACTUAL RESULT

Error mentioned above is displayed instead of Presence Builder

EXPECTED RESULT

Presence Builder should open without error

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
In our test environment we found this solution:

Code:
# ll /etc/localtime 
lrwxrwxrwx. 1 root root 25 Nov 14  2021 /etc/localtime -> ../usr/share/zoneinfo/UTC
# unlink /etc/localtime
# ln -s /usr/share/zoneinfo/UTC /etc/localtime
(Notice the difference in the symlinks: parent "../" prefix vs. the absolute "/" path.)

Could you please check on your system whether changing the symlink solves the issue for you?
 
@Peter Debik Indeed, this worked, thanks a lot for this!

Is this considered a "permanent workaround" or are there any plans to provide a "proper" fix in an updated version of Presence Builder?
 
I don't know yet what the priority level will be. Developers asked for the confirmation first that the solution works. I think now they'll escalate it into a ticket where a permanent fix will be developed.
 
Back
Top