Search results

Sound not very good. I'm disapointed.

Is it possible to use the migation tool in order to migrate the content of a Centos7 system to a server that uses alma8?

What will happen with my existing license when I change my Server and os?

Sounds like a soution but not a real solution. Watchdog should be able to login.

maillog contains the following entry every hour: Dec 30 13:24:44 h2675909 dovecot: pop3-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<ovPXO7kNwrF/AAAB> Dec 30 13:24:44 h2675909 dovecot: pop3-login...

And what's about config.aum?

OK - grafana update has been installed now. But I wonder why this long way of user activities was needed.

Doesn't change the situation.

I followed the Plesk docu and runed into trouble. So I think it's not a good idea to change the version of a software and not to change the related part of the documentation

Update failed. Update utility stdout: Loading mirror speeds from cached hostfile * epel: mirrors.hostiserver.com Retrieving key from https://autoinstall.plesk.com/grafana/rpm/gpg.key Update utility stderr: 2023-10-28 12:46:27 INFO: pum is called with arguments...

https://docs.plesk.com/en-US/obsidian/administrator-guide/plesk-administration/plesk-for-linux-the-plesk-firewall.72046/

Sorry, but there is nothingto post. It's simply the link Rules Management that is not there. I de- and reinstalled the Firewall but it had no effect.

Nobody can help?

Tools & Settings > Firewall > Enable Firewall but not the link: Rules Management

Tools & Settings > Firewall > Enable Firewall Rules Management > is not displayed. What's going wrong?

plesk bin license --retrieve result: Updating Plesk license key: [2023-10-14 22:25:53.580] 24850:652af9141a320 ERR [panel] KeyUpdate Result code: 2 Network failure [2023-10-14 22:25:53.580] 24850:652af9141a320 ERR [panel] KeyUpdate Result desc: cURL cannot communicate with license server...

report failed: Failed to send report: Failed connect to ka.plesk.com:443; Operation now in progress How to repair that?

But the Plesk dokumentation say: Caution: Both the Plesk firewall and firewalld are tools for managing the iptables firewall. Using both tools simultaneously can result in conflicts and in ports required for Plesk to operate being closed. We recommend only using one tool at a time. Please help.

It's a never ending circel ... - logi to 60 onitorng is possible - the live chat there is just a bot - the cat link leads to the sign-in of the support page - login there needs a validation but doesn't accept the gmail account I'm on a good way to get crazy