Search results

I have no idea what your expertise is. It is possible you don't know how DNS works together with the fact that no-one dares to publish their real domains and ip addresses it becomes very hard to tell what may be wrong

You're writing that Bind is running. Is it running as a service within Plesk's control or did you install Bind on the Linux server? If you haven't installed Bind through Plesk, it will not have control over the service. Is the server the authoratative DNS-server for that specific domain? If...

you may or may not be aware that you can login with [email protected] with https://webmail.mycompanyname.com that's secured with your wildcard certificate *.mycompanyname.com as long as those 2 domains remain on the same server.

There was another thing I bumped into in Ubuntu 20. I have a local perl installation that I use for my Anti-Spam-Proxy. Again this is not directly related to Plesk, but you may find this useful. In a very distant past I used to update Perl on the server. This is NOT a good idea as Plesk uses...

apt install curl

Like I said, one of my servers is running production in 20.04 I had only a few difficulties, but none had anything to do with Plesk. For my own WordFence harvesting script I had some difficulties to get the MySQL extensions to work in MariaDB because watchmouse killed his project in bitbucket...

I would use the migration extension. I have many subscriptions with an installation date of 2007 whilst my oldest Plesk server is 3 years old. You can bulk migrate them even, but I would start with 1 or 2 domains. A back-up is not that wise and I know of a few "restore bugs" that Plesk refuses...

To get pre-Ubuntu 20.x behaviour, you need to run the command: https://askubuntu.com/questions/1250974/user-root-cant-write-to-file-in-tmp-owned-by-someone-else-in-20-04-but-can-in

The issues regarding with LetsEncrypt are limited to the wildcard certificates only. You have that issue too, but apparently you're not using wildcard certificates. The Plesk servers running the website depend on the Plesk DNS extension for those certificates. Whenever the certificate starts...

I don't think dist-upgrade is worth it. Your hardware needs to be replaced anyhow You will have down-time You risk having a buggy or even non-working system afterward,

I'm running 1 Plesk server on Ubuntu 20 for a month now. The only very strange thing I ran into was Ubuntu 20's security feature on one of my bash scripts. The script runs as root and was unable to handle files that belonged to another owner and had no security attributes set for others. On all...

My solution to your initial problem was to have a seperate Plesk server for DNS. Have Plesk DNS disabled on all the hosting servers. Install Bind9 on 1 of the other Plesk servers and configure it as a slave server. I have this setup for years and it has many advantages. Only recently I ran into...

Username: mr-wolf TITLE WordPress Scan stumbles on files in folder ./private PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Ubuntu 16.04 & Ubuntu 20 Plesk 18.0.30 PROBLEM DESCRIPTION When I do a scan for WordPress instances with the new WP toolkit the scan stops after it stumbles on...

Username: mr-wolf TITLE plesk repair web removes a PHP configuration file of mine without asking which it thinks is orphaned PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Ubuntu 18.04 Plesk 18.03 PROBLEM DESCRIPTION I have the file...

In that case even more reasons to NOT do an OS upgrade at all with the probable risk of opening up a can of worms and stay with a system that's at least working.

Never do an upgrade of a production machine. It's better to make a clean install and migrate. Currently I'm setting up an Ubuntu 20.04 LTS machine with Plesk that's replacing an Ubuntu 16 LTS that was in service for more than 5 years

Are you running version 18.0.30 as that -php-fpm-configuration is a fairly new option? Did you use the option -php-fpm-configuration ? I ran a "plesk repair web" without options this week and noticed it also runs the php-fpm configuration check by default, but I don't know for sure if it did...

You probably have a missing or orphaned php-file in /etc/php/7.0/fpm/pool.d/ or some other folder. As of version 18.0.30 you can issue plesk repair web -php-fpm-configuration to fix that. Before I had to use my own scripts to find out what was happening. I do have a problem with that command...

You could even have incoming data reverted to another service on the same port. The least intrusive way is to work with an added config file in the folder /etc/nginx/conf.d The config files in that folder are parsed by Nginx in alphabetical order. The file zz010_psa_nginx.conf is responsible...

I would flog him 5 times and promise him another 10 if it happens again :)