Recent content by Bitpalast

The pages are not exactly identical. In the first one, your YT script insertion is in line 360, in the second one it is in line 350. This indicates that the issue is coming from your page's scripts. Moreover, your YT is played from Youtube, not from your website. In your website you are only...

Honestly, remembering how much effort was put into the CentOS -> Alma upgrade script and how many caveats had to be fixed, Q2/2026 is completely unrealistic for that script. Let's first have a very stable and very reliable Alma 8 -> 9 upgrade script, then maybe consider another to -> 10 maybe by...

status=226/NAMESPACE is a systemd failure at the “namespace setup” step, i.e. systemd tried to apply one of its sandboxing/isolation features (mount/user/tmp/dev namespaces, etc.) for httpd.service and the kernel/container runtime didn’t allow it. In LXC containers (especially unprivileged ones...

So mail.mydomain1.com was hosted elsewhere, not on the same server where the website is? That of course explains why so many iterations where needed to solve the case. I was certainly assuming that mail.mydomain1.com is hosted on the same server where the website is hosted.

How does an MX record come into play in this scenario, specificially when you use "localhost" to address the SMTP server?

Is the SMTP server actually listening? Is the service active?

It's either the host name or a ban on localhost IP connecting to the SMTP server. First try "localhost" instead of the public domain name.

You can try "localhost" instead of the real hostname.

Port 587 requires STARTSSL/STARTTLS, won't work on SSL/TLS. Options: change port to 465 or 25 (without SSL/TLS, you don't need that anyway if the connection stays on your own server).

Yes it is. If you have tried the delisting service Sign in to your account be aware, that the first email you get from them always states, that there is no error non MS side. However, you need to respond to that email and bring your case forward again, e.g. send them their return mail, then a...

Username: TITLE Auto-scrolling to bottom of paginated pages PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE 18.0.74 #2 PROBLEM DESCRIPTION Since the latest Plesk updates, paginated pages auto-scroll to the bottom when opened. This makes the pagination settings >10 useless...

I suggest to rather find /var/www/vhosts/domain.tld/httpdocs/ -type d -exec chmod 0750 {} \;

Shortening log rotation intervals on that one big client installation is a good idea. Removing AWStats might be too much. It's an issue in that software, but sooner or later that will be solved. Instead, develop a short script that monitors the process list for long running AWStats processes and...

A reboot of that instance might solve it.

I think there is not true technical issue in Plesk with it. Rather check whether the domain is consistently routed to the desired IP or whether it might have several A- or AAAA-records that are pointing to another server, too.